agentsclimarketplace

Conventional commits

Skill jnMetaCode/skillet/skills/conventional-commits

skillet — a package manager for AI agent skills (SKILL.md). Find, install, version & share skills from a Git-backed registry. Zero infra, MCP-native, reproducible.

Install
npx -y skills add jnMetaCode/skillet --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.

What its author says it does

Copied from the file, not written here

Write precise Conventional Commits messages from the actual staged diff. Use whenever committing code or asked to write/fix a commit message.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, as published. Nobody here has run it

conventional-commits

Write the message from the diff, not from the conversation. The reader is a stranger running git log in two years.

Procedure

  1. Read what is actually staged: git diff --cached --stat then the diff itself.
  2. Classify the change — pick ONE primary type:
    • feat new user-visible capability · fix corrects wrong behavior
    • refactor no behavior change · perf faster, same behavior
    • docs · test · build · ci · chore (only when nothing else fits)
  3. Scope = the subsystem a reader would filter by: feat(parser): …. Omit if the repo doesn't use scopes (check git log --oneline -20 and match style).
  4. Subject line: imperative, lowercase, no period, ≤ 72 chars, and it must state the effect, not the activity — "fix: reject expired tokens" not "fix: update token check".
  5. Body (when the why isn't obvious): 1–3 sentences on why the change was needed and any non-obvious consequence. Wrap at 72. Never narrate the diff.
  6. Breaking change → footer BREAKING CHANGE: <what breaks and the migration>, and add ! after the type: feat(api)!: ….

Anti-patterns to reject

  • One commit doing two unrelated things — split it (git add -p).
  • "update", "misc fixes", "address comments" — say what changed.
  • Restating the conversation ("as discussed…") — the log has no conversation.
  • Explaining that the change is correct — that belongs in the PR, not the log.

Example

fix(ingest): treat mtime regressions as edits, not new files

Restored backups can move mtime backwards; we indexed those as fresh
documents, duplicating every chunk. Key on inode+path instead.

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.