conventional-commits

Generate conventional commit messages with the Claude Code footer.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/francisfuzz/emoji_gen --skill conventional-commits-francisfuzz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/francisfuzz/emoji_gen/tree/main/.claude/skills/conventional-commits
Command: npx skills add https://github.com/francisfuzz/emoji_gen --skill conventional-commits-francisfuzz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps create commit messages that adhere to the Conventional Commits specification and automatically include the Claude Code footer for traceability.

Core Features & Use Cases

  • Enforces type/scope patterns (feat, fix, docs, etc.)
  • Supports breaking-change indicators
  • Provides templates, examples, and guidance for consistent history

Quick Start

Generate a commit using the provided template, for example:

git commit -m "$(cat <<'EOF' feat: add emoji category support

Adds categorization system for emojis (animals, food, symbols). Use --category to filter... EOF )"

Frequently Asked Questions about conventional-commits

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

FAQPage Schema
How do I write commit messages that follow the Conventional Commits specification?

Conventional Commits uses a structured format: type[optional scope][optional !]: description. Common types include feat (new feature), fix (bug fix), docs (documentation), and others. This standardizes your git history and enables automated changelog generation and version bumping.

Can I use conventional commit templates with Claude Code?

Yes. This Skill generates conventional commit messages automatically within Claude Code workflows. It enforces the type/scope/description format, supports breaking-change indicators with !, and includes the Claude Code footer for traceability on every commit.

What's the best way to enforce consistent commit message format across a git repository?

Conventional Commits standardizes message structure across your team. By applying templates and validation rules during commit creation, you ensure type and scope consistency, making your git log machine-readable for automation and easier for developers to scan.

Do I need to manually format each commit message, or can it be generated?

This Skill generates commit messages automatically during git commit workflows. You provide the change context, and it produces a properly formatted conventional commit with the required footer, removing manual formatting effort and reducing human error.

How does the Claude Code footer improve commit traceability?

The Claude Code footer appended to every commit creates an audit trail linking each commit to Claude Code generation. This improves traceability for code review, debugging, and compliance workflows where you need to know how and when changes were created.

What happens if I need to mark a breaking change in a conventional commit?

Conventional Commits supports breaking-change indicators. Add an exclamation mark before the colon (e.g., feat!: or feat(scope)!:) to signal a breaking change, and optionally include a BREAKING CHANGE footer for detailed explanation. This prevents consumers from missing critical API changes.