Conventional commit

Skill vaibhavsaxena022/skills/conventional-commit

Write a Conventional Commits message from the staged git diff. Use when the user asks to commit, write a commit message, or has just staged changes. Produces a properly formatted "type(scope): subject" with an optional body and footer.From its SKILL.md

Install

npx -y skills add vaibhavsaxena022/skills --skill conventional-commit

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

0 stars0 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.7 KB, 314 tokens by cl100k_base, as published. Nobody here has run it

Conventional Commit

Generate a commit message that follows the Conventional Commits spec from the currently staged changes.

Steps

Run git diff --staged. If nothing is staged, run git status and ask the user to stage changes first.
Pick the primary type:
- feat — a new feature
- fix — a bug fix
- refactor — code change that neither fixes a bug nor adds a feature
- perf — performance improvement
- test — adding or fixing tests
- docs — documentation only
- build / ci — build system or CI changes
- chore — tooling, deps, housekeeping
Infer a short scope from the touched module/package (optional).

Compose the message:

type(scope): imperative subject, <=72 chars, no trailing period

- what changed and why (wrap at 72 chars)

BREAKING CHANGE: ... / Refs #123   (only if applicable)

Rules

Subject in the imperative mood ("add", not "added" or "adds").
One logical change per commit — if the diff mixes unrelated changes, suggest splitting them.
Don't invent issue numbers or breaking-change notes.
Output only the message. Run git commit only if the user asks.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.