菜单
Stage all changes, generate a Conventional Commit message from the diff, and commit. Use when the user says "commit", "commit this", "commit my changes", "commit for me", or wants a clean git commit without manual staging or message writing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use ONLY when the user explicitly asks for it — e.g. "explain this code," "walk me through this module/feature/API," "review this for me," "/explain-code," or points at a file/function/snippet and asks what it does. Produces a short, high-level report on existing (already-committed, no-diff) code: what it does, how it's structured, non-obvious behavior, edge cases, risk flags, open questions, and where to look next. Do NOT trigger automatically just because code is present in context or was recently discussed — wait for the user to ask.
Use ONLY when the user explicitly asks for it — e.g. "practice IELTS speaking", "IELTS speaking practice", "help me with IELTS", "IELTS part 1/2/3", or similar direct requests. Do NOT trigger on general mentions of IELTS or English speaking unless the user explicitly invokes this skill by name.
Use ONLY when the user explicitly asks for it — e.g. "mock interview me", "do a mock interview", "practice interview questions", "interview me", "drill technical Q&A", or similar direct requests. Do NOT trigger on general interview-related discussion unless the user explicitly invokes this skill by name.
Use ONLY when the user explicitly asks for it — e.g. "create a product brief", "flesh this out", "turn this idea into a product brief", or similar direct requests. Do NOT trigger on general product discussions or idea sharing unless the user explicitly invokes this skill by name.
Use ONLY when the user explicitly asks for it — e.g. "document this API", "hand off this endpoint", "prepare FE integration notes", or similar direct requests. Do NOT trigger automatically when documenting or summarizing code — wait for the user to ask.
Use ONLY when the user explicitly asks to enter brainstorming mode by name (e.g. "brainstorm first", "let's brainstorm", "start a brainstorming session"). Do NOT trigger on general discussion, questions, requests for suggestions, or solution exploration unless the user explicitly invokes this skill by name.
基于 SOC 职业分类
| name | bdv-smart-commit |
| description | Stage all changes, generate a Conventional Commit message from the diff, and commit. Use when the user says "commit", "commit this", "commit my changes", "commit for me", or wants a clean git commit without manual staging or message writing. |
Automates the git commit workflow: stage, generate message, commit.
Check for changes
git status --short to detect staged and unstaged changes.Stage all changes
git add -A to stage everything.Analyze the diff
git diff --cached to review staged changes.Generate commit message
Use Conventional Commits format:
<type>[optional scope]: <short summary>
[optional body]
Rules:
type must be one of: feat, fix, refactor, chore, docs, test, style, perf, ci, buildscope is optional — use only when the change is scoped to a clear module/areasummary is imperative, lowercase, no period, max 72 charsbody is optional — add only when the change is non-obvious or multi-partConfirm before committing
git commitCommit
git commit -m "<message>" with the approved message.git add -A: This means the working tree is clean. Report and stop.MERGE_HEAD and include the merge context in the message body.git diff --cached contains patterns like API keys, passwords, tokens, or .env content, STOP and warn the user. Do not commit.