conventional-commit

Generates standardized commit messages following the Conventional Commits specification.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/devsajad/next.js-starter-kit --skill conventional-commit-devsajad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventional-commit
Source: https://github.com/devsajad/next.js-starter-kit/tree/main/.claude/skills/conventional-commit
Command: npx skills add https://github.com/devsajad/next.js-starter-kit --skill conventional-commit-devsajad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing inconsistent or vague git commit messages makes project history hard to read, breaks automated changelog generation, and slows down code review. This Skill enforces the Conventional Commits specification so every commit message follows a structured, machine-parseable format. ## Core Features & Use Cases - Structured Message Generation: Builds commit messages with type, scope, description, body, and footer fields using a defined XML template. - Guided Git Workflow: Walks through git status, git diff, staging, and committing so changes are reviewed before the message is written. - Validation Rules: Enforces allowed types (feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert), imperative mood descriptions, and BREAKING CHANGE footers. - Use Case: After modifying several files in a feature branch, run the workflow to inspect the diff, then produce a message like "feat(parser): add ability to parse arrays" and commit it directly in the terminal. ## Quick Start Ask the assistant to review your staged git changes and generate a conventional commit message, then commit them.

Frequently Asked Questions about conventional-commit

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

FAQPage Schema
How do I write a conventional commit message?

Use the format type(scope): description, where type is one of feat, fix, docs, style, refactor, perf, test, build, ci, chore, or revert. Write the description in imperative mood, and optionally add a body and footer for breaking changes or issue references.

How to generate commit messages from git diff automatically?

Run git status and git diff to review your changes, then stage files with git add. The workflow constructs a conventional commit message from the inspected changes and executes git commit -m with the generated message in the terminal.

What commit types are allowed in Conventional Commits?

The allowed types are feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert. The scope is optional but recommended for clarity, and a breaking change can be marked with an exclamation mark or a BREAKING CHANGE footer.

Does this workflow work with any git repository?

Yes, it works with any standard git repository since it relies only on common git commands like status, diff, add, and commit. No additional tooling, hooks, or dependencies are required.

Why is my conventional commit message rejected as invalid?

Validation fails when the type is not one of the allowed values or the description is missing or not in imperative mood. Check that the message follows the type(scope): description structure and uses verbs like add instead of added.