format-commit

Generate structured commit messages with Why and How sections from git changes.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/daodaoedu/daodao --skill format-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: format-commit
Source: https://github.com/daodaoedu/daodao/tree/main/.claude/skills/format-commit
Command: npx skills add https://github.com/daodaoedu/daodao --skill format-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often write terse or inconsistent commit messages that lack context, making code review, changelogs, and future debugging harder. This Skill guides the author to capture the purpose (Why) and the concrete changes (How) so each commit is informative and standardized.

Core Features & Use Cases

  • Guided prompts to capture commit type, scope, short description, and the reasons for the change.
  • Automated analysis of git diffs to synthesize concrete How points from staged changes without asking the user to restate low-level details.
  • Confirmation workflow that shows the generated message formatted with Why and How sections and optionally executes the commit, useful for maintainers and teams enforcing descriptive commit policies.

Quick Start

Use the skill to generate a Why/How formatted commit message from the current repository changes and confirm to run the commit.

Frequently Asked Questions about format-commit

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

FAQPage Schema
How do I generate structured git commit messages with Why and How sections?

Generate structured commit messages by prompting for commit type, scope, and reasons, then synthesizing the How section from staged git diffs. This produces standardized, descriptive commits for code review and changelogs.

What is the best way to standardize commit messages for code review and changelogs?

Standardize commit messages by using a guided workflow that captures the change purpose and concrete modifications separately. This ensures each commit contains informative Why and How sections for maintainers and teams.

Can I automatically analyze git diffs to write descriptive commit messages?

Yes, the tool automatically analyzes git diffs to synthesize concrete How points from staged changes. This prevents developers from manually restating low-level details while maintaining descriptive commit policies.

Does the commit message generator execute git commit after confirmation?

Yes, after confirming the generated Why and How formatted message, the workflow optionally executes the git commit directly. This streamlines the process for developers committing code in repositories.

What do I need to generate structured commit messages from local git changes?

You need access to repository git status and diffs. The workflow prompts for commit type, scope, and reasons for the change, then synthesizes the concrete modifications from the staged changes.

When should I use a guided commit message format instead of writing commits manually?

Use a guided format when terse or inconsistent commit messages lack context for code review, changelogs, or future debugging. It captures the purpose and concrete changes so each commit is informative and standardized.