generate-commit-message
Generate Commit Message Only
Inspect staged changes and produce a commit message.
Run each command as a separate Bash tool call.
Do not combine commands with &&, ;, pipes, redirection, wrapper echo lines, or other shell glue unless a shell feature is truly required.
git diff --cached --name-status
git diff --cached
If no files are staged, stop and report that no commit message can be generated.
Write the message in English using this structure:
- Subject line: One plain sentence, first letter capitalized.
- Do not use conventional prefixes such as
fix:,feat:,chore:,docs:, or similar tags. - Body: Detailed bullet points describing key file-level and behavior-level changes.
Output only the commit message content in a copy-ready format.
Do not run git commit.
Do not modify staging state unless the user explicitly asks.
More from patrick-fu/awesome-skills
brainstorm
>-
9explore-and-plan
>-
8cursor-coding-agent
>-
4log-driven-debugging
>
2codex-coding-agent
Delegate coding tasks specifically to Codex CLI (`codex`) from another host agent or automation harness. Use this only when the user explicitly wants Codex or `codex` to do the work, such as building features, reviewing diffs, refactoring a codebase, continuing a prior Codex session, or running a longer coding task through Codex. Do not use for simple one-line edits you can do directly, for ordinary read-only code inspection that the current agent can answer itself, or when the user did not ask to use Codex.
2claude-code-coding-agent
Delegate coding tasks specifically to Claude Code CLI (`claude`) via background process or headless print mode. Use this only when the user explicitly wants Claude Code or `claude`, such as building features, reviewing diffs, refactoring a codebase, or running a longer coding task in the background with Claude Code. Do not use for simple one-line edits you can do directly, for read-only code inspection without delegation, or when the user did not ask to use Claude Code.
2