agentsclimarketplace

Conventional commit

Skill vaibhavsaxena022/skills/conventional-commit

AI-agent skills for software engineering — works with Claude Code, Codex, Cursor

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.

2 things to look at

  • 23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 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.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.7 KB, 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

  1. Run git diff --staged. If nothing is staged, run git status and ask the user to stage changes first.
  2. 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
  3. Infer a short scope from the touched module/package (optional).
  4. 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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.