agentsclimarketplace

Conventional commit

Skill K95M65/AI_ONBOARD/skills/conventional-commit

Portable agent workflow framework for Codex, Claude Code, and OpenCode—shared project context, focused skills, independent review, and safe updates.

Install
npx -y skills add K95M65/AI_ONBOARD --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

  • 21 days oldThe repository was created 21 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

Writes a Conventional Commits message from the currently staged git changes. Use when the user asks to commit, wants a commit message drafted, or asks you to figure out the right commit type/scope for staged work.

SKILL.md

2.0 KB, 458 tokens by cl100k_base, as published. Nobody here has run it

Conventional Commit

Draft a well-formed Conventional Commits message from what's currently staged, then commit it.

When to use

The user has staged changes (or asks you to stage them) and wants a properly formatted commit — e.g. "commit this", "write a commit message", "what type should this commit be?".

Steps

  1. Inspect the staged changes — do not guess from memory:

    bash scripts/staged-summary.sh

    If it reports nothing staged, ask whether to git add the intended files first. Never git add -A without confirming scope.

  2. Choose the type from the diff:

    TypeUse when
    featA new feature / capability
    fixA bug fix
    docsDocs only
    refactorBehavior-preserving code change
    testAdding/adjusting tests
    choreTooling, deps, config, build
    perfPerformance improvement
    ciCI config/scripts

  3. Pick a scope (optional) — the package/area touched, from the file paths (e.g. api, auth, ui).

  4. Write the subject — imperative mood, lowercase, ≤ ~72 chars, no trailing period: type(scope): do the thing. Add a body only if the why isn't obvious. Add BREAKING CHANGE: footer (or ! after the type) for breaking changes.

  5. Commit — show the message first, then:

    git commit -m "type(scope): subject" -m "optional body"

Rules

  • Base the type/scope on the actual diff, not the user's phrasing.
  • One logical change per commit — if the diff spans unrelated concerns, say so and suggest splitting.
  • Never invent a co-author or trailer the user didn't ask for.

What ships with it: 1 file

717 B alongside SKILL.md, 1 of them executable

scripts/

Keep looking

Skills are one crate of 327,132. 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.