GitHub
change-mapper
Strategically groups code changes and maps them to documentation references for atomic commits.
☆ 1View skill
tools git workflows AI Skills
Discover tools git workflows skills, compare source repositories and read the instructions for each workflow.
Categories: tools git workflows
tools git workflows Clear filters
Browse skills
GitHub
commit-policy
Enforces commit guardrails ensuring traceability and security.
☆ 1View skill
GitHub
commit
Use when creating any git commit, when user asks to commit work, or after completing a task. Always invoke before running git commit.
☆ 1View skill
GitHub
git-doc-updater
Auto-check and update key documentation before Git commits to keep docs in sync with code. Triggers: docs, 文檔, 更新文檔, sync docs, release, 發布.
☆ 1View skill
GitHub
readme-updater
Intelligently update README.md to sync with code changes. Triggers: readme, 說明, 更新說明, update readme, 文檔同步.
☆ 1View skill
GitHub
readme-i18n
Maintain multilingual README versions (English primary, Chinese translation). Triggers: i18n, 翻譯, translate, 多語言, sync readme, 中英文, bilingual.
☆ 1View skill
GitHub
git-precommit
Orchestrate pre-commit workflow including Memory Bank sync, README/CHANGELOG/ROADMAP updates. Triggers: GIT, gc, push, commit, 提交, 準備 commit, 要提交了, git commit, pre-commit, 推送.
☆ 1View skill
GitHub
git-ops
Get information about the state of a git repo, get diffs, make commits, make PRs, etc.. Use this skill when the user needs to accomplish git tasks.
☆ 1View skill
GitHub
git-commit-message
读取暂存区变更（git diff --cached）并参考 git log 的最近提交风格生成提交消息。适用于用户让你读取暂存区、总结暂存变更或建议提交消息的场景。
☆ 1View skill
GitHub
commit-helper
Generate clear commit messages from repository changes. Use when creating commits, writing commit messages, or reviewing staged/current changes. Works with both git and jj.
☆ 1View skill
GitHub
commit-msg
Generate commit message from git diff with security check
☆ 1View skill
GitHub
branch-completion
Use when implementation is complete and tests pass. Guides completion by presenting structured options for merge, PR, or cleanup.
☆ 1View skill
GitHub
code-review-reception
Use when receiving code review feedback, before implementing suggestions. Requires technical verification, not performative agreement or blind implementation.
☆ 1View skill
GitHub
git-worktrees
Use when starting feature work that needs isolation from current workspace. Creates isolated git worktrees with directory selection, safety verification, and baseline testing.
☆ 1View skill
GitHub
mr-review
Review and approve GitLab merge requests using glab CLI
☆ 1View skill
GitHub
github-search
Search GitHub code, repositories, issues, and PRs via gh CLI
☆ 1View skill
GitHub
ci-fixer
Automated CI/CD pipeline fixer - watches CI, fixes errors locally, commits, and loops until green. Use when CI is failing and you want to automatically fix and verify changes.
☆ 1View skill
GitHub
review-code
This skill should be used when the user asks to "review code", "review this PR", "code review", "audit this code", or mentions reviewing pull requests, security checks, or code quality. Covers security (OWASP),...
☆ 1View skill
GitHub
github-action-sha-resolver
Resolves GitHub Action tags/versions (e.g., @v4) to their full 40-character commit SHAs for security pinning.
☆ 1View skill
GitHub
github-issues
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or mana...
☆ 1View skill
GitHub
workflow-security-review
Guide for reviewing GitHub Actions for security vulnerabilities.
☆ 1View skill
GitHub
ci-github-actions
Apply when setting up CI/CD pipelines: automated testing, linting, building, and deployment with GitHub Actions.
☆ 1View skill
GitHub
git-conventional-commits
Apply when writing commit messages to maintain consistent, readable git history that enables automated changelog generation.
☆ 1View skill
GitHub
git-workflow
Apply when establishing team branching strategy, PR workflows, and release management.
☆ 1View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.