conventional-commit

What it does and when to use it

Write a Conventional Commits v1.0.0 message for the current changes. Use when writing or checking a commit message or PR title.

How it works

SKILL.md has no level-two headings · 26 lines, 151 words

---
name: conventional-commit
description: Write a Conventional Commits v1.0.0 message for the current changes. Use when writing or checking a commit message or PR title.
---

# Conventional Commit

Format:

```text
<type>(<scope>): <description>

[body: why, not what]

[footer: BREAKING CHANGE: ..., Closes #123]
```

Types: `feat` new behavior · `fix` bug fix · `refactor` no behavior change · `perf` speed ·
`docs` docs only · `test` tests only · `build` deps/build · `ci` pipelines · `chore` other upkeep · `style` formatting.

Rules:
- Base it on `git diff --cached` (or `git diff` if nothing is staged), not on the conversation.
- Imperative, present tense: "add", not "added"/"adds". Lowercase header, no trailing period, ≤ 72 chars.
- Scope = module, package or app touched. Omit if none fits.
- Breaking change: `!` after type/scope and a `BREAKING CHANGE:` footer.
- One logical change per commit. If the diff mixes two, say so and propose a split.
- No AI attribution (`Co-Authored-By`, "Generated with") unless the repo's own rules require it.

Example: `fix(auth): refresh expired token before retrying request`

Versions

Database snapshot: 13.11.2026 · package version afd1f7615f39 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100commit
  Create a conventional commit from current workspace changes. Use when the user asks to run $commit, asks to commit changes, or asks for a commit message from the current diff.
• 96commit-message-generator
  Generate a clear, concise conventional commit message from staged code changes. Use when writing a commit message.
• 100commit
  Write a commit message and create a git commit. Use when the user wants to commit changes, asks for a commit message, or says "commit this" or "make a commit".
• 100at-commit
  Generate a Conventional Commits message from staged changes and wait for confirmation before committing. Use when the user asks to commit or generate a commit message.
• 100commit
  Analyze staged changes and write a conventional commit message. Use when staged changes are ready to commit or a message needs wording.
• 100caveman-commit
  Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.