commit-helper

Generate clear conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or after completing TDD cycles.

⭐3stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026⬇️1downloads

When & Why to Use This Skill

The Commit Helper skill automates the generation of professional, standardized git commit messages by analyzing staged code changes. By leveraging AI to interpret diffs and apply Conventional Commit standards, it enhances repository readability, streamlines the development workflow, and ensures consistent documentation across team projects without manual effort.

Use Cases

  • Workflow Automation: Automatically generate precise commit messages after completing TDD cycles or refactoring sessions to maintain a clean and searchable project history.
  • Team Standardization: Enforce the Conventional Commits specification (feat, fix, refactor) across a distributed team to facilitate automated changelog generation and semantic versioning.
  • Efficiency Boost: Reduce the cognitive load of summarizing complex code changes by allowing the AI to analyze git diffs and suggest concise, imperative-style summaries that follow best practices.
  • Code Review Readiness: Create descriptive and structured commit messages that help reviewers quickly understand the intent and scope of changes before a Pull Request is submitted.
namecommit-helper
descriptionGenerate conventional commit messages from staged changes. Runs autonomously using Haiku model. Use after completing TDD cycles, after refactoring sessions, or when ready to commit.
contextagent

Commit Helper

Autonomous commit message generation that analyses staged changes and generates conventional commit messages.

When to Use

  • After completing a TDD cycle (tests pass)
  • After a refactoring session
  • After completing a task in the XP workflow
  • Whenever you have staged changes ready to commit

What It Does

  1. Checks git status for staged changes
  2. Reads the staged diff
  3. Checks recent commits for style consistency
  4. Analyses change type and scope
  5. Generates a conventional commit message

Conventional Commit Format

<type>: <summary>

[optional body]

[optional footer]

Types

Type Use For
feat New feature
fix Bug fix
refactor Code restructuring (no behaviour change)
test Adding/updating tests
docs Documentation only
chore Build, tooling, dependencies

Summary Rules

  • Under 50 characters
  • Imperative mood ("add" not "added")
  • No period at end
  • Capitalise first letter

Safety Rules

  • NEVER add contributors unless explicitly requested
  • NEVER commit files containing secrets
  • NEVER use --amend unless explicitly requested