Conventional commits

Skill minagayid/Agents/skills/library/conventional-commits

Write clear git commit messages following the Conventional Commits spec. Use when the user asks to commit changes, write a commit message, or clean up commit history.From its SKILL.md

Install

npx -y skills add minagayid/Agents --skill conventional-commits

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, as published. Nobody here has run it

Conventional Commits

Produce commit messages that follow Conventional Commits.

Format

<type>(<optional scope>): <description>

<optional body>

<optional footer(s)>

Types

feat — a new feature
fix — a bug fix
docs — documentation only
style — formatting, no code change
refactor — code change that neither fixes a bug nor adds a feature
perf — performance improvement
test — adding or fixing tests
build / ci — build system or CI changes
chore — tooling, deps, housekeeping

Rules

Subject line ≤ 72 chars, imperative mood ("add", not "added"/"adds"), no trailing period.
Use a scope when it clarifies the area, e.g. feat(auth): ....
Explain what and why in the body (wrap at ~72 cols), not how — the diff shows how.
Breaking changes: add ! after type/scope and a BREAKING CHANGE: footer.
Reference issues in the footer: Closes #123.
Before writing, inspect the actual diff (git diff --staged) so the message matches reality.

Examples

feat(api): add pagination to the /users endpoint

Return 25 users per page with `page` and `per_page` query params.
Keeps large tenants from timing out on the list call.

Closes #482

fix: prevent crash when config file is missing

Fall back to defaults instead of throwing on first run.