Conventional Commit
- 14.3k installs
- 37.1k repo stars
- Updated July 28, 2026
- github/awesome-copilot
Conventional Commits is a skill for writing standardized commit messages following the Conventional Commits specification.
About
Conventional Commits is a skill for standardized commit message formatting following a structured specification. Developers use it to ensure consistent git history that enables automated versioning and changelog generation. Core practice for teams using semantic versioning.
- Conventional Commits specification and patterns
- Enforces consistent commit message format
- Enables automated changelog and versioning
Conventional Commit by the numbers
- 14,293 all-time installs (skills.sh)
- +303 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #10 of 739 Git & Pull Requests skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
conventional-commit capabilities & compatibility
- Works with
- github · gitlab · bitbucket
- Use cases
- code review
- Pricing
- Free
npx skills add https://github.com/github/awesome-copilot --skill conventional-commitAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 14.3k |
|---|---|
| repo stars | ★ 37.1k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | github/awesome-copilot ↗ |
How do you write Conventional Commits messages with an AI agent?
Conventional Commits is a skill for standardized commit message formatting following a structured specification. Developers use it to ensure consistent git history that enables automated versioning a
Who is it for?
Teams implementing semantic versioning and automated changelogs
Skip if: Teams that do not follow Conventional Commits or rely solely on squash-merge titles with no per-commit message discipline.
When should I use this skill?
The user asks for a commit message, conventional commit format, or help summarizing staged git changes before commit.
What you get
Validated Conventional Commits message with type, scope, subject, body, and optional breaking-change footer ready to paste into `git commit`.
- Conventional Commits-formatted message string
By the numbers
- Structured XML prompt template with examples and validation steps
- Workflow begins with `git status` before message generation
Files
Instructions
<description>This file contains a prompt template for generating conventional commit messages. It provides instructions, examples, and formatting guidelines to help users write standardized, descriptive commit messages in accordance with the Conventional Commits specification.</description>Workflow
Follow these steps:
1. Run git status to review changed files. 2. Run git diff or git diff --cached to inspect changes. 3. Stage your changes with git add <file>. 4. Construct your commit message using the following XML structure. 5. After generating your commit message, Copilot will automatically run the following command in your integrated terminal (no confirmation needed):
git commit -m "type(scope): description"6. Just execute this prompt and Copilot will handle the commit for you in the terminal.
Commit Message Structure
<commit-message>
<type>feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert</type>
<scope>()</scope>
<description>A short, imperative summary of the change</description>
<body>(optional: more detailed explanation)</body>
<footer>(optional: e.g. BREAKING CHANGE: details, or issue references)</footer>
</commit-message>Examples
<examples>
<example>feat(parser): add ability to parse arrays</example>
<example>fix(ui): correct button alignment</example>
<example>docs: update README with usage instructions</example>
<example>refactor: improve performance of data processing</example>
<example>chore: update dependencies</example>
<example>feat!: send email on registration (BREAKING CHANGE: email service required)</example>
</examples>Validation
<validation>
<type>Must be one of the allowed types. See <reference>https://www.conventionalcommits.org/en/v1.0.0/#specification</reference></type>
<scope>Optional, but recommended for clarity.</scope>
<description>Required. Use the imperative mood (e.g., "add", not "added").</description>
<body>Optional. Use for additional context.</body>
<footer>Use for breaking changes or issue references.</footer>
</validation>Final Step
<final-step>
<cmd>git commit -m "type(scope): description"</cmd>
<note>Replace with your constructed message. Include body and footer if needed.</note>
</final-step>Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.264k92.8k
Git Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.164k187kResolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.160k187k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.145k261kGit CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.2k37k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.15.6k147Forks & variants (1)
Conventional Commit has 1 known copy in the catalog totaling 218 installs. They canonicalize to this original listing.
- ilteoood - 218 installs
How it compares
Use conventional-commit for spec-structured messages; use freeform commit prompts when the team does not enforce Conventional Commits.
FAQ
What commit format does conventional-commit produce?
conventional-commit produces messages following the Conventional Commits specification: a type (feat, fix, chore, etc.), optional scope, subject line, optional multi-line body, and optional breaking-change or issue-reference footers.
Does conventional-commit inspect git changes first?
Yes. The conventional-commit workflow instructs agents to run `git status` and review diffs before drafting, so the generated subject and body reflect actual staged changes rather than guesses.
Is Conventional Commit safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.