write-commits

Generate Git commit messages following the Conventional Commits specification.

4|1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/lushly-dev/afd --skill write-commits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-commits
Source: https://github.com/lushly-dev/afd/tree/main/.claude/skills/write-commits
Command: npx skills add https://github.com/lushly-dev/afd --skill write-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures your Git commit messages are consistent, informative, and follow the Conventional Commits standard, making your project history clear and changelogs easy to generate.

Core Features & Use Cases

  • Conventional Commits Generation: Automatically formats commit messages with type, scope, subject, body, and footer.
  • Scope Identification: Suggests appropriate scopes based on project structure (packages, modules, features).
  • Breaking Change Handling: Correctly formats BREAKING CHANGE: footers and uses the ! marker.
  • Use Case: When you've just finished a new feature, use this Skill to help you write a commit message like feat(auth): implement two-factor authentication with a detailed body explaining the implementation.

Quick Start

Use the write-commits skill to generate a commit message for your staged changes.

Frequently Asked Questions about write-commits

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

FAQPage Schema
How do I write a Git commit message that follows the Conventional Commits standard?

A conventional Git commit message is formatted with a type, optional scope, subject, body, and footer. This Skill generates that structure automatically by classifying commit types, selecting scopes, and formatting breaking changes to ensure your project history stays consistent.

What is the correct format for indicating a breaking change in a commit message?

Breaking changes in commit messages use the `BREAKING CHANGE:` footer or the `!` marker after the type and scope. This Skill automatically detects breaking changes in your staged code and correctly formats the commit footer to adhere to the specification.

How do I choose the right scope for a conventional commit based on my project structure?

Scopes in conventional commits represent specific packages, modules, or features. This Skill identifies appropriate scopes by analyzing your project structure and suggesting the most relevant module context for your staged changes.

Can I automatically generate a changelog from conventional commit messages?

Yes, consistent conventional commit messages enable automated changelog generation. This Skill ensures your Git history uses the correct type prefixes, scopes, and formatting required by changelog generation tools to parse version updates accurately.

What's the best way to write detailed Git commit messages for staged changes?

Reviewing staged changes to write detailed commit messages involves formatting the type, scope, subject, and body. This Skill analyzes your staged Git changes and generates a fully structured commit message, including a detailed body explaining the implementation.

Why should I enforce conventional commits for my code review and version control process?

Enforcing conventional commits during code review ensures version control history is clear, informative, and machine-readable. This Skill standardizes your commit conventions, making it easier to track features and fixes across the project lifecycle.