commit

Analyze git changes and draft a What/Why/Details commit message.

25|5|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Hedgehogues/awesome-claude --skill commit-hedgehogues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Hedgehogues/awesome-claude/tree/main/skills/commit
Command: npx skills add https://github.com/Hedgehogues/awesome-claude --skill commit-hedgehogues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a well-structured git commit following project conventions. Analyzes staged and unstaged changes, drafts a detailed commit message with What/Why/Details sections, and commits. Auto-detects task ID format from git history.

Core Features & Use Cases

  • Analyzes changes in the working directory and staging area to propose coherent commits.
  • Groups edits into logical blocks and generates What/Why/Details sections for each commit.
  • Auto-detects TASK-ID from git history or uses an explicit argument to tag commits.
  • Enforces project conventions and prompts for confirmation before committing.

Quick Start

Invoke the commit skill to create a structured commit for your current changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate a structured git commit message for project conventions?

Automating a structured git commit involves analyzing staged and unstaged changes, grouping related edits into logical blocks, and drafting a What/Why/Details message. The skill enforces project conventions and prompts for approval before committing.

How does auto-detecting a TASK-ID from git history work for commits?

Auto-detecting a TASK-ID from git history works by scanning previous commit messages to identify and extract the existing task ID format. Alternatively, it can use an explicit argument provided by the user to tag the new commit accurately.

Can I group related code changes into logical blocks before committing?

You can group related code changes into logical blocks by analyzing your working directory and staging area. The skill identifies coherent edits and organizes them into separate blocks to propose logically structured commits.

Does this workflow guard against committing sensitive files in version control?

Yes, the workflow guards against committing sensitive files in version control. It enforces best practices by scanning changes and preventing sensitive files from being included, prompting for confirmation before performing the final commit.

What is the best way to enforce commit conventions across a software engineering team?

The best way to enforce commit conventions is to automate the drafting process with What/Why/Details sections. The skill analyzes changes, auto-detects task IDs, and prompts for confirmation to ensure every commit adheres to established project standards.