Saucebox Registry
← Browse

@michalvavra/commit

B

Create git commits using Conventional Commits format. Use when the user asks to commit changes or wants help crafting a commit message.

skillclaude

Install

agr install @michalvavra/commit --target claude

Writes 1 file into .claude/skills/, pinned to git-dd3e8f32.

  • .claude/skills/commit/SKILL.md

Document

name: commit description: Create git commits using Conventional Commits format. Use when the user asks to commit changes or wants help crafting a commit message. license: Apache-2.0 (see https://github.com/mitsuhiko/agent-stuff)

Create a git commit for the current changes using a concise Conventional Commits-style subject.

Format

<type>(<scope>): <summary>

  • type REQUIRED. Use feat for new features, fix for bug fixes. Other common types: docs, refactor, chore, test, perf.
  • scope OPTIONAL. Short noun in parentheses for the affected area (e.g., api, parser, ui).
  • summary REQUIRED. Short, imperative, <= 72 chars, no trailing period.

Notes

  • Body is OPTIONAL. If needed, add a blank line after the subject and write short paragraphs.
  • Do NOT include breaking-change markers or footers.
  • Do NOT add sign-offs (no Signed-off-by).
  • Only commit; do NOT push.
  • If it is unclear whether a file should be included, ask the user which files to commit.
  • Treat any caller-provided arguments as additional commit guidance. Common patterns:
    • Freeform instructions should influence scope, summary, and body.
    • File paths or globs should limit which files to commit. If files are specified, only stage/commit those unless the user explicitly asks otherwise.
    • If arguments combine files and instructions, honor both.

Steps

  1. Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
  2. Review git status and git diff to understand the current changes (limit to argument-specified files if provided).
  3. (Optional) Run git log -n 50 --pretty=format:%s to see commonly used scopes.
  4. If there are ambiguous extra files, ask the user for clarification before committing.
  5. Stage only the intended files (all changes if no files specified).
  6. Run git commit -m "<subject>" (and -m "<body>" if needed).

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-dd3e8f32ccc02026-07-31