committing-staged-with-message
Generate commit message for staged changes, pause for approval, then commit. Stage files first with `git add`, then run this skill.
Best use case
committing-staged-with-message is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate commit message for staged changes, pause for approval, then commit. Stage files first with `git add`, then run this skill.
Teams using committing-staged-with-message should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/committing-staged-with-message/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How committing-staged-with-message Compares
| Feature / Agent | committing-staged-with-message | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generate commit message for staged changes, pause for approval, then commit. Stage files first with `git add`, then run this skill.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Commit staged with Generated Message ## Step 1: Analyze Staged Changes Run these commands using the Bash tool to gather context: - `git diff --staged --name-only` - List staged files - `git diff --staged --stat` - Diff stats summary - `git log --oneline -5` - Recent commit style - `git 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. ## Step 2: Generate Commit 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):** 1. **What changed**: bullet points per file or logical group 2. **Symbols added/removed** (when applicable): functions, classes, tests 3. **Diff stats**: lines added/removed (from `--stat` summary line) — MUST be the last line of the body - Format: `+ symbol_name`, `- symbol_name` - Omit for config/docs/formatting-only changes Keep the message laser-focused. Do not repeat the subject line in the body. ## Step 3: Pause for Approval **Please review the commit message.** - **Approve**: "yes", "y", "commit", "go ahead" - **Edit**: Provide your preferred message - **Cancel**: "no", "cancel", "stop" ## Step 4: Commit Once approved: - `git commit --gpg-sign -m "[message]"` - Commit staged changes with approved message (GPG signature mandatory) - `git status` - Verify success
Related Skills
message-authentication-code-pattern
Security pattern for implementing Message Authentication Codes (MACs) to ensure data integrity and origin authentication. Use when implementing HMAC, CMAC, or other MAC algorithms, verifying message integrity, authenticating message origin with shared secrets, or when non-repudiation is NOT required. Specialization of Cryptographic action pattern.
acc-create-psr7-http-message
Generates PSR-7 HTTP Message implementations for PHP 8.5. Creates Request, Response, Stream, Uri, and ServerRequest classes with immutability. Includes unit tests.
denylist-stuck-messages
Add message IDs to the relayer denylist. Use after investigating stuck messages with /investigate-stuck-messages, or when you have specific message IDs to denylist.
staged-changes-review
Checklist-driven review of staged Git changes with deterministic rule scanning and semantic analysis. Use when the user wants to review staged changes, check for errors before commit, or validate code quality before committing.
searching-message-history
Search Telegram conversation history and stored links. Use when finding past messages, what someone said, or links shared in chats.
bgo
Automated Blender build-go workflow. Automatically builds, removes old version, installs, enables, and launches Blender with your extension/add-on. Use when you want to quickly test changes, execute complete build-to-launch cycle, or run custom packaging scripts with automatic Blender launch.
fireflies-automation
Automate Fireflies tasks via Rube MCP (Composio). Always search tools first for current schemas.
fireberry-automation
Automate Fireberry tasks via Rube MCP (Composio). Always search tools first for current schemas.
finmei-automation
Automate Finmei tasks via Rube MCP (Composio). Always search tools first for current schemas.
fingertip-automation
Automate Fingertip tasks via Rube MCP (Composio). Always search tools first for current schemas.
finerworks-automation
Automate Finerworks tasks via Rube MCP (Composio). Always search tools first for current schemas.
find-skill
Search for Agent Skills in local folders and on GitHub. Use when you need a capability you don't have—search before building.