Back to the catalog
Agent skills · Code versions (Git)
50 tools
- commitCreates and executes one coherent git commit from staged or selected working-tree changes. Use when the user asks to commit changes, stage a2 stars
- prCreates or updates a GitHub pull request for the current branch. Use when the user asks to publish committed branch changes as a PR or refre2 stars
- git-workflow[AUTO-INVOKE] MUST be invoked BEFORE creating git commits, PRs, or code reviews. Covers Conventional Commits, PR templates, review requireme4 stars
- development-brain知行合一：主动识别正在开始、进行中或刚完成的真实开发工作，在首次代码、Git 或外部系统写入前做证据化预检，执行中只引用已确认约束，完成并取得 Git/测试/MR 证据后自动复盘和安全进化。自然语言中的实现、修改、调试、重构、修复、构建、开发验证、提交代码以及 Skill 功能变
- chinese-commit-conventions中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-co
- chinese-git-workflow国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用，不要根据上下文自动触发。
- using-git-worktrees当需要开始与当前工作区隔离的功能开发，或在执行实现计划之前使用——通过原生工具或 git worktree 回退机制确保隔离工作区存在
- write-prDraft a pull request title and body from the current branch's diff and commit history, following the project's PR template and title convent19 stars
- git-workflow-managerGit workflow and branching strategy expert. Use when establishing team collaboration patterns, optimizing commit practices, or designing sca
- spec-driven-developmentSpec-Driven Development (SDD) methodology based on GitHub's SpecKit.4 stars
- add-git-tagCreate annotated Git milestone tags. Use when completing a phase, releasing a version, marking a research checkpoint, or generating a milest
- release-codePrepare research code repositories for public release. Use for open-source cleanup, README/LICENSE/CITATION, GitHub releases, tags, and repr
- safe-git-opsPerform Git operations safely with sandbox-aware failure handling. Use for commit, push, merge, rebase, stash, worktree, conflicts, lock fil
- update-docsRefresh project documentation after code changes. Use after implementing features, changing behavior, or preparing a milestone commit.
- work-timeline-plannerBuild retrospective or forward-looking work timelines from git history, docs, notes, or chat records. Use for progress summaries, mentor rep
- github-automation自动化 GitHub 操作。当用户需要推送代码到 GitHub、管理仓库、创建 PR、处理 Issue、git push 失败时使用此技能。优先使用 mcporter call github.push_files 而不是 git push。119 stars
- mcp-deepwikiSkills for accessing and searching docs in DeepWiki/GitHub’s public code repositories can help users understand open-source project source c166 stars
- gitnexus-pr-reviewUse when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. 48,544 stars
- gitnexus-pr-swarm-reviewRun a GitNexus production-readiness pull request review using a coordinated reviewer swarm.48,544 stars
- gitnexus-reviewReview code changes with GitNexus from a GitHub PR URL or number, a branch/ref or commit range, or local staged, unstaged, and untracked cha48,544 stars
- gitnexus-workUse when executing an engineering plan produced by gitnexus-plan (or a small bounded task directly) — implements step by step with GitNexus 48,544 stars
- githubGitHub issues, pull requests, repos, code search, releases, gists, stars, watching, forks, and Actions via the gh CLI. Use when the user men17 stars
- gitlabGitLab issues, merge requests, repositories, CI pipelines, and code search via the glab CLI. Use when the user mentions GitLab, an MR/issue 17 stars
- git-workflow-and-versioningStructures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitt117,497 stars
- epic-trackerRoadmap and delivery artifact management in Linear or GitHub. Use when creating, editing, decomposing, moving, or updating roadmaps, epics, 8 stars
- git-helpersGit workflow for conventional commits, pull request creation, and pull request merging. Use when committing, opening or pushing a pull reque8 stars
- good-readmeCreate, improve, or audit README.md documents for GitHub projects. Use only when the user explicitly asks for a README, README quality/reada13 stars
- codex-review-cycleUse when the user explicitly asks to run an iterative Codex review cycle on a non-empty git diff, including working-tree changes, current br1 star
- vibe-commitUse when the user asks to commit, stage, or "save" agent-assisted coding changes — including vague requests like "commit this", "commit plea1 star
- vibe-goal-alignmentUse when the user asks to align, confirm, or correct the agent's understanding before action; when prior misinterpretation, risky ambiguity,1 star
- vibe-reviewUse when the user asks for agent-assisted code review of a git diff, working tree, branch, base ref, git-backed plan or document change, or 1 star
- vibe-writingUse when the primary task is writing, revising, reviewing, or critiquing agent-assisted coding development text, source-code comments or doc1 star
- writing-style-guideUse when generating or editing user-facing prose, including docs, comments, READMEs, changelogs, commit messages, PR descriptions, and chat 1 star
- melech-cr-clone-trainerBuild or resync a private reviewer that learns your GitHub code-review style.46 stars
- melech-plan-reviewReview a solution before approving it, like a GitHub changes tab: a file tree of red and green pseudo-code the user can comment on inline, t46 stars
- melech-pr-gardenerTend one explicit GitHub author's open PRs and keep them green — one stateless pass per scheduled run.46 stars
- code-reviewUse this when reviewing AEM Edge Delivery Services (EDS, Franklin, Helix) code, either self-review at the end of development before opening 326 stars
- create-siteUse this when a user wants to create a brand-new AEM Edge Delivery site from scratch and no GitHub repository or DA content exists yet — tri326 stars
- slicc-handoffUse this when the user asks to continue work in the SLICC browser agent or to install a skill into SLICC, for example "handoff to slicc", "m326 stars
- cc-pr-review-ciComprehensive TypeScript/React PR review. Outputs structured review.json consumed by a posting script that creates a GitHub Review with inli
- conventional-commit-reviewReviews staged changes and drafts a Conventional Commits-compliant commit message with the right type, scope, and length. Use before committ
- cpp-coding-standardsC++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce mo
- ecc-conventionsDevelopment conventions and patterns for ECC. JavaScript project with conventional commits.
- everything-claude-codeDevelopment conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
- everything-claude-code-conventionsDevelopment conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
- git-workflowGit workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative developmen
- github-opsGitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security mo
- orch-add-featureOrchestrate building a brand-new feature end to end — research, plan, TDD implementation, review, and gated commit — by delegating each phas
- orch-change-featureOrchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to m
- orch-fix-defectOrchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to t
Looking for something else?QuestionsContact
