Menu
Generate commit message for staged changes, pause for approval, then commit. Stage files first with `git add`, then run this skill.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | committing-staged-with-message |
| description | Generate commit message for staged changes, pause for approval, then commit. Stage files first with `git add`, then run this skill. |
| compatibility | Designed for Claude Code |
| metadata | {"model":"haiku","argument-hint":"(no arguments needed)","disable-model-invocation":true,"allowed-tools":"Bash, Read, Glob, Grep"} |
Run these commands using the Bash tool to gather context:
git diff --staged --name-only - List staged filesgit diff --staged --stat - Diff stats summarygit log --oneline -5 - Recent commit stylegit diff --staged - Review detailed staged changes. Size guard: if --stat shows >10 files or >500 lines changed, skip the full diff and rely on --stat + --name-only to generate the message.Use the Read tool to check .gitmessage for commit message format and syntax.
The commit message body MUST include (concisely — no padding, no redundancy):
--stat summary line) — MUST be the last line of the body
+ symbol_name, - symbol_nameKeep the message laser-focused. Do not repeat the subject line in the body.
Please review the commit message.
Once approved:
git commit --gpg-sign -m "[message]" - Commit staged changes with approved message (GPG signature mandatory)git status - Verify successInteractive Q&A to build UserStory.md from user input. Use when the user wants to create a user story document or start the assisted workflow.
Generates prd.json task tracking file from PRD.md requirements document. Use when initializing Ralph loop or when the user asks to convert PRD to JSON format for autonomous execution.
Transforms UserStory.md into PRD.md by extracting features and converting user stories into functional requirements.
Investigates codebase before planning. Use before any non-trivial implementation task to gather context in isolation.
Provides concise, focused code reviews matching exact task complexity requirements. Use when reviewing code quality, security, or when the user asks for code review.
Writes tests following TDD (using pytest and Hypothesis) and BDD best practices. Use when writing unit tests, integration tests, or BDD scenarios.