commit

Generate Conventional Commits messages with scopes and breaking-change footers.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/eriknovak/ErikNovak --skill commit-eriknovak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/eriknovak/ErikNovak/tree/main/.dotfiles/.claude/skills/commit
Command: npx skills add https://github.com/eriknovak/ErikNovak --skill commit-eriknovak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create clear, standardized git commit messages that follow the Conventional Commits specification, reducing ambiguity and improving changelog quality.

Core Features & Use Cases

  • Generate conventional commit messages for the most common change types (feat, fix, docs, style, refactor, perf, test, build, ci).
  • Validate syntax, enforce optional scopes, and support breaking-change footers to communicate impact.
  • Provide a guided workflow for staging, composing, and applying commits within a Git repository.

Quick Start

Create a conventional commit message for the latest changes in the working tree.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages for git changes?

You create conventional commit messages by using this Skill to analyze your working tree changes, validate syntax, and guide you through staging and applying commits with standardized prefixes like feat, fix, or docs.

What is the conventional commits specification and when do I need it for version control?

The conventional commits specification standardizes git commit messages using structured types, optional scopes, and breaking-change footers. You need it for version control to reduce ambiguity and automate changelog generation across any Git repository.

Can I include breaking change footers and scopes in my git commit workflow?

Yes, you can include breaking change footers and optional scopes in your git commit workflow. The Skill enforces these conventional commit elements to clearly communicate impact and structure your repository history.

What's the best way to automate standard commit types like feat and fix in a Git repository?

The best way to automate standard commit types is using a guided workflow that validates your changes and applies conventional commit types like feat, fix, refactor, and perf, ensuring consistent version-control history across your Git repository.

Does this conventional commit workflow work with any Git repository?

Yes, this conventional commit workflow applies to any Git repository. It handles feature additions, fixes, docs updates, and refactors by guiding you through staging, diffing, and committing steps without requiring specific platform dependencies.