菜单
Group and stage related changes for git commit. Use when staging files for commit, grouping related changes, or deciding what to include in each commit. Implements how to group changes and when to split commits.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill when writing code, implementing features, refactoring, planning architecture, designing systems, reviewing code, or debugging. This skill transforms junior-level code into senior-engineer quality software through SOLID principles, TDD, clean code practices, and professional software design.
Resolve git rebase conflicts: when to accept main's version vs branch, how to remove conflict markers, and how to avoid duplicate sections. Use when resolving conflicts during git rebase (e.g. rebase onto main) or when continuing a rebase after fixing conflicts.
When adding new API or server routes: document manual validation, add an automated check (smoke or test) that hits the route, wire it into the suite, and run that verification before marking the task complete. Use when adding new Nuxt/API routes, server endpoints, or similar.
Finish and ship work: sync task systems (taskmaster/beads if in use), ensure quality gates pass, run deslop, then shipit. Use when wrapping up a branch—closing tasks, cleaning AI slop, and opening or updating a PR.
Create or update a pull request with a terse semantic title and appropriate description. Use when creating a PR, opening a pull request, updating PR description, or when a PR already exists and the description should be checked and updated.
Write semantic commit messages in Conventional Commits format. Use when committing, writing commit messages, or when a terse semantic commit is required. Covers format, types, scope, imperative mood, and length.
| name | stage-related-files |
| description | Group and stage related changes for git commit. Use when staging files for commit, grouping related changes, or deciding what to include in each commit. Implements how to group changes and when to split commits. |
Group changes logically for git add and decide when to split into one or more commits.
Group by logical change: one feature/fix/docs refactor per commit when possible.
git status to see modified, added, and deleted files*research*.md (e.g. docs/cloud-build-cache-research.md)plan*.txt or *.plan.mdgit add <paths>. Avoid staging everything in one blob unless it truly is one logical changegit status again to verify what is staged (confirm research/plan files are not included)git add for the full setgit add + commit cycles (group 1 → add → commit, then group 2 → add → commit)