skills.rest
specks-dev
specks-devOFFICIAL
Explore all skills by this author →
GitHub

prepare-git-commit-message

Generate review-ready git commit messages from uncommitted changes and diffs.

Updated Aug 23, 2026
Search Tags:#git#review#generate#commit-message#code-changes#status-diff
One-click install
npx skills add https://github.com/specks-dev/specks --skill prepare-git-commit-message
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-git-commit-message
Source: https://github.com/specks-dev/specks/tree/main/.claude/skills/prepare-git-commit-message
Command: npx skills add https://github.com/specks-dev/specks --skill prepare-git-commit-message

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers convert uncertain or vague work into clear, actionable commit messages, increasing traceability and review efficiency.

Core Features & Use Cases

  • Generate concise, descriptive commit messages from the current working tree by analyzing git status, diff, and recent history.
  • Write the suggested message to git-commit-message.txt for user review before committing.
  • Supports reference to plan elements or steps if available, and includes a concise summary of changed files.

Quick Start

Use the prepare-git-commit-message skill to generate a commit message for your current working directory. The tool analyzes uncommitted changes and outputs a file named git-commit-message.txt containing the suggested message for review and manual commit.

Frequently Asked Questions about prepare-git-commit-message

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a git commit message from uncommitted changes?▼

You can generate a git commit message by analyzing uncommitted changes, diffs, and recent history to produce a concise message. The suggested message is written to git-commit-message.txt for your review before you manually commit.

What is the best way to write clear commit messages for multi-file changes?▼

Writing clear commit messages for multi-file changes involves analyzing the overall diff and recent history to create a precise summary. This approach produces a single review-ready message covering all changed files without performing the actual git commit.

Can I generate a commit message without automatically committing to git?▼

Yes, you can generate a commit message without automatically committing to git. The process analyzes uncommitted changes and outputs the suggested message to a text file, ensuring you retain full manual control over the actual git commit.

How does analyzing git status and diff improve commit message generation?▼

Analyzing git status and diff improves commit message generation by identifying specific code changes and recent history. This ensures the generated message accurately reflects the actual working tree state and supports traceability for single or multi-file commits.

Do I need to reference plan elements to generate a commit message from code changes?▼

You do not need to reference plan elements to generate a commit message, but the tool supports them if available. It primarily relies on analyzing uncommitted changes and recent history to produce the suggested message.

Related Skills

Explore More Software Engineering Skills→
agentclashagentclash
25

git-rules

Validate git commit hygiene and working tree status post-commit.

Official
Basic
mattg101mattg101
1

gcp-copy

Stage all changes, commit with a message, and push to a remote Git repository.

Community
Basic
HomericIntelligenceHomericIntelligence
18

run-precommit

Execute pre-commit hooks on staged or all repository files.

Official
Intermediate
jk278jk278

git-analyzer

Analyze git repositories to summarize commit history and file changes.

Community
Intermediate