commit-conventions

Generate Conventional Commits messages from staged git changes.

2|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/anton-dovnar/cursor --skill commit-conventions-anton-dovnar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-conventions
Source: https://github.com/anton-dovnar/cursor/tree/main/skills/commit
Command: npx skills add https://github.com/anton-dovnar/cursor --skill commit-conventions-anton-dovnar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures commit messages follow the Conventional Commits standard by analyzing staged changes and producing uniformly formatted messages.

Core Features & Use Cases

  • Analyze staged changes with git diff --staged to determine type, scope, and impact
  • Generate commit messages that conform to the Conventional Commits structure (type, optional scope, short description, and optional body)
  • Use in git pre-commit or commit-time workflows to improve changelog automation and readability

Quick Start

Generate a Conventional Commit message for the current staged changes.

Frequently Asked Questions about commit-conventions

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

FAQPage Schema
How do I automatically generate conventional commit messages from staged changes?

To generate conventional commit messages automatically, this Skill analyzes your git diff --staged output to determine the type, scope, subject, and optional body, producing a formatted message that conforms to the Conventional Commits specification.

What are conventional commits and how do they improve git commit workflows?

Conventional commits standardize git commit message formatting by structuring type, optional scope, short description, and body, which improves changelog automation and overall commit readability across codebases of various sizes.

Can I use this automated commit formatting tool with my existing pre-commit workflow?

Yes, this tool is applicable during git pre-commit or commit-time workflows, analyzing staged changes to output properly formatted messages without requiring additional dependencies or external components.

How does the tool determine the correct type and scope for a conventional commit?

The tool determines the type and scope by analyzing the git diff --staged output, assessing the nature and impact of your code changes to build a compliant Conventional Commits message.

Does this conventional commits generator require any specific git dependencies or components?

No, this conventional commits generator has zero dependencies and requires no additional components, operating directly on staged git changes to produce properly formatted messages.