commit-message

Generates commit messages. Use before any git operations involving a commit, or when writing, generating, or creating commit messages.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 8, 2026

When & Why to Use This Skill

This Claude skill automates the generation of professional, standardized Git commit messages following the Conventional Commits specification. It enhances repository maintainability and team collaboration by ensuring every change is documented with clear intent, proper scoping, and mandatory compliance markers like DCO sign-offs.

Use Cases

  • Standardizing commit history: Automatically generating 'type(scope): message' formatted commits to ensure a clean, readable, and searchable project history.
  • Enforcing Best Practices: Ensuring every commit explains the 'why' behind a change rather than just the 'what', improving the quality of future code audits.
  • Workflow Automation: Streamlining the git workflow by automatically adding DCO (Developer Certificate of Origin) sign-offs and preparing content for PR body updates.
  • Context-Aware Documentation: Analyzing code changes to suggest appropriate scopes and types (feat, fix, refactor, etc.), reducing the cognitive load on developers during the staging process.
namecommit-message
descriptionGenerates commit messages. Use before any git operations involving a commit, or when writing, generating, or creating commit messages.

Commits

  • Format: type(scope): message
  • Scope SHOULD indicate the area of change
  • Types: feat, fix, docs, refactor, test, chore, ci
  • SHOULD be one logical change per commit - suggest splitting unrelated changes
  • SHOULD explain why, not just what changed
  • MUST use git commit -s to add DCO sign-off (do not add sign-off manually)
  • MUST update PR body when adding follow-up commits to an open PR