Commit staged with generated message

VerifiedSafe

Analyzes staged changes via `git diff --staged`, generates a structured commit message (changes, symbols added/removed, stats), then pauses for approval before committing with GPG signature. Helps automate consistent commits without manually writing messages.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#git#commit-messages#staged-changes#approval-flow

Recommended for

Automated summary

Generates a commit message for staged changes, pauses for approval, then commits with GPG signing.

Strengths

  • Automatically analyzes changes to generate a structured commit message
  • Includes a pause for human approval or editing
  • Respects local conventions via .gitmessage
  • Automatically adds GPG signature

Limitations

  • Requires files to be staged beforehand with git add
  • Only works in Claude Code
  • May fail if GPG signing is not configured
When to use it

Use this skill when you have staged changes ready to commit and want a consistent commit message following project conventions.

When not to use it

Avoid this skill for very frequent commits or when you prefer writing each message manually without an approval step.

Security analysis

Safe
Quality score92/100

The skill runs standard git commands (diff, log, commit) on the local repository. It does not exfiltrate data, execute arbitrary code, or perform destructive actions. The commit is gated behind user approval. No obfuscated or risky operations are present.

No concerns found

How this analysis is made

Examples

Commit staged bug fix
Run the committing-staged-with-message skill
Commit staged refactoring
Use the commit skill on my staged changes
Commit with approval
Generate a commit message for the staged files and let me review it

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

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

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/commit-staged-with-generated-message-mm5t8a5w/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/commit-staged-with-generated-message-mm5t8a5w' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/commit-staged-with-generated-message-mm5t8a5w/download' --output '.skill-downloads/commit-staged-with-generated-message-mm5t8a5w/SKILL.md.part' && mv '.skill-downloads/commit-staged-with-generated-message-mm5t8a5w/SKILL.md.part' '.skill-downloads/commit-staged-with-generated-message-mm5t8a5w/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Environment declared by the author: Designed for Claude Code

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/commit-staged-with-generated-message-mm5t8a5w/SKILL.md' && test -s '.skill-downloads/commit-staged-with-generated-message-mm5t8a5w/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/committing-staged-with-message' && cp -R '.skill-downloads/commit-staged-with-generated-message-mm5t8a5w' '.claude/skills/committing-staged-with-message'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/commit-staged-with-generated-message-mm5t8a5w'

openskills read 'commit-staged-with-generated-message-mm5t8a5w'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/commit-staged-with-generated-message-mm5t8a5w/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills