duckyman-aiduckyman-ai/agent-skills/skills/git-convention/SKILL.md

git-convention

Skill1 starsChanged 6 months agoMITView on GitHub

Write conventional git commit messages following the Angular commit convention format. Use this skill whenever writing commit messages, creating commits, reviewing git history, generating changelogs, or any task involving git version control. Triggers when you see "commit", "git commit", "commit message", "changelog", "version control", "git history", "semantic commit", "conventional commit", or when the user asks to commit changes, create a PR, or review commit history. Also use when setting up commit linting or husky hooks for enforcing commit conventions.

1 other project uses a version of this.

Adopted by

Most recently taken up by

yanix2445/skillstheir own version, first seen Feb 9, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
yanix2445/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- capcut-editorSkill
- design-mdSkill
- flutter-clean-archSkill
- intellij-pluginSkill

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Write conventional commit messages that are machine-readable, enable automatic changelog generation, and drive semantic versioning (fix → …
line 8
Distinctive:
Use imperative mood throughout ("add", "move", "fix")
line 106
Distinctive:
Keep subject under 72 characters
line 107
Distinctive:
Write vague subjects like "update stuff"
line 116
Distinctive:
Add Co-Authored-By or AI attribution lines
line 118

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Git Convention Skill

Write conventional commit messages that are machine-readable, enable automatic changelog generation, and drive semantic versioning (fix → PATCH, feat → MINOR, BREAKING CHANGE → MAJOR).

Format

<type>[optional scope][!]: <subject>

[optional body]

[optional footer(s)]

Append ! after type/scope to flag a breaking change without a footer: feat!: or feat(api)!:.

Type

Type	Description
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation changes
`style`	Formatting, whitespace (no logic change)
`refactor`	Code change that neither fixes a bug nor adds a feature
`perf`	Performance improvement
`test`	Adding or correcting tests
`build`	Build system or dependency changes
`ci`	CI configuration changes
`chore`	Other changes not modifying src or test files
`revert`	Reverts a previous commit

Scope

The scope identifies the area of change — module, package, component, or feature name. Use lowercase, keep it short.

Examples: auth, api, ui, user, core, payment, config

Subject Rules

Imperative, present tense: "add" not "added" or "adds"
Lowercase first letter, no period at the end
Under 72 characters

Body

Explain what changed and why, not how. Separate from subject with a blank line. Use bullet points for multiple changes.

Footer

One or more footers in git trailer format (Token: value or Token #value). Common tokens:

Closes #123 — link to issues
BREAKING CHANGE: description — note breaking API changes
Refs: #456 — reference related commits/PRs
Reviewed-by: Name — credit reviewers

Examples

Feature:

feat(auth): add login with Google

- Add GoogleSignInButton component
- Update auth service to handle OAuth tokens
- Handle failed authentication with error boundary

Closes #123

Bug fix:

fix(api): handle null response from user endpoint

Null responses crashed the app. Return empty user object instead.

Breaking change (footer):

feat(core): change user model structure

BREAKING CHANGE: User.id is now String instead of int.
All database queries need updating.

Breaking change (! notation):

feat(api)!: send email when product ships

Refactoring:

refactor(user): extract validation to separate class

Move validation from UserService to UserValidator for testability.

Best Practices

DO:

Use imperative mood throughout ("add", "move", "fix")
Keep subject under 72 characters
Explain what and why in the body
Reference issues in the footer
One logical change per commit

DON'T:

Use past tense
Capitalize subject or end with period
Mix multiple types in one commit
Write vague subjects like "update stuff"
Explain how the code works in the message
Add Co-Authored-By or AI attribution lines

Tooling

These tools make conventional commits practical by automating enforcement and changelog generation. Search for the right tool based on your project's language:

Commit linting — reject commits that don't follow the format. Works as a git hook (often via husky, pre-commit, or lefthook).

Changelog generation — read commit history and produce a categorized CHANGELOG.md automatically:

feat → Features section
fix → Bug Fixes section
BREAKING CHANGE → Breaking Changes section

Popular options by ecosystem:

JS/TS: commitlint + conventional-changelog
Python: commitizen
Flutter/Dart: changelog_cli + conventional_commit
Android: jreleaser + conventional-commit-gradle-plugin
Go: goreleaser + git-chglog
Rust: cog (cocogitto)
Ruby: commitizen-rb
Java/Kotlin: jreleaser + conventional-commit-gradle-plugin
.NET/C#: GitVersion + MinVer
PHP: conventional-commits-php

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free