菜单
Generate a well-formatted Git commit message based on staged changes. Use when the user wants to commit code and needs a clear, conventional commit message written for them.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | git-commit |
| description | Generate a well-formatted Git commit message based on staged changes. Use when the user wants to commit code and needs a clear, conventional commit message written for them. |
Generate a commit message for the current staged changes.
git diff --cached to see what is staged.git status and tell the user to stage files first.<type>(<scope>): <short summary>
<optional body: what and why, not how>
Types: feat, fix, refactor, chore, docs, test, style, perf, ci
Rules:
git commit -m "<message>" (or with -m for body if needed).Review code changes for correctness, security, performance, and style. Use when the user wants a thorough review of a diff, PR, or specific files before merging or submitting.
Systematically debug an error, unexpected behavior, or failing test. Use when the user has a bug, crash, or test failure they need to diagnose and fix.
Generate or update documentation for an existing codebase. Use when the user needs a README, API reference, module-level docs, or inline code comments written or refreshed based on the actual code.
Break down a feature or project requirement into a structured development plan with tasks, milestones, and implementation order. Use when the user has a goal but needs to figure out what to build and in what sequence.
Refactor code to improve structure, readability, or performance without changing external behavior. Use when the user wants to clean up or restructure existing code safely.
Generate a new project skeleton from scratch based on the user's chosen tech stack. Use when starting a new project and needing the initial directory structure, config files, and boilerplate set up correctly.