菜单
Generate Git commit messages following project conventions. Use when the user wants to commit changes or asks for a commit message. Analyzes staged/unstaged changes and produces properly formatted commit messages with tags, Title Case summaries, and prose bodies.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Visualizes tasks as a Discovery Tree using Mermaid diagrams. Use when planning or tracking multi-step work with parent and child task relationships.
Full AppleScript development aid. Use when the user wants to create, edit, run, debug, compile, or test AppleScript scripts, including GUI automation via System Events. Scaffolds files with proper headers, follows AppleScript best practices, compiles and runs scripts, and assists with debugging.
Ensure source files include a consistent metadata header comment using the correct comment syntax for the language. Use when creating new source files or when the user asks to add, fix, or update file headers. Handles Created/Modified timestamps, copyright years, and language-appropriate comment syntax.
Full Bash development aid. Use when the user wants to create, edit, run, debug, or test Bash shell scripts. Scaffolds files with proper headers, follows Bash best practices, executes scripts, and assists with debugging.
Full C++ development aid with emphasis on memory safety and cross-platform programming. Use when the user wants to create, edit, build, run, debug, or test C++ source files, headers, or CMake projects. Scaffolds files with proper headers, enforces modern C++ best practices, memory-safe idioms, cross-platform CMake builds, and assists with debugging and testing.
Full Perl development aid. Use when the user wants to create, edit, run, debug, or test Perl scripts and modules. Scaffolds files with proper headers, follows Perl best practices, executes scripts, and assists with debugging.
| name | commit |
| description | Generate Git commit messages following project conventions. Use when the user wants to commit changes or asks for a commit message. Analyzes staged/unstaged changes and produces properly formatted commit messages with tags, Title Case summaries, and prose bodies. |
| allowed-tools | Read, Bash, Grep, Glob |
| argument-hint | ["description of changes"] |
Generate and create Git commit messages following the project's strict formatting rules.
[TAG] Title Cased Short Summary
Detailed description of the change, written in prose and wrapped at
72 characters.
[BUG FIX] = A bug fix[FEATURE] = New feature code[REFACTOR] = A code refactor[TEST CODE] = Added test code[TIDY] = A tidy up action such as reformatting or spelling fixesIf this is the very first commit of a project (no prior commits exist), the entire commit message must be exactly:
Initial commit
No tag, no body.
git status to see what has changedgit diff --cached to see staged changes; if nothing is staged, run git diff to see unstaged changesgit log --oneline -1 to determine if this is the first commit (if it errors, it is the first commit)README.markdown (preferred), README.md, README, README.rst, README.txt). If one exists, read it and determine whether the changes make any part of it stale or incomplete (features added/removed, usage changed, install steps, options, file layout, etc.). If so, update the README in the same commit. If the README is unaffected, proceed without changes.git add -A)git commit -m "$(cat <<'EOF'
[TAG] Title Cased Short Summary
Detailed description of the change.
EOF
)"
$ARGUMENTS is provided, treat it as a description of the changes to help craft the commit message