Saucebox Registry
← Browse

@phenobarbital/git-commit-formatter-3

A

Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.

skillclaude

Install

agr install @phenobarbital/git-commit-formatter-3 --target claude

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

  • .claude/skills/git-commit-formatter-3/SKILL.md

Document

name: git-commit-formatter description: Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.

Git Commit Formatter Skill

When writing a git commit message, you MUST follow the Conventional Commits specification.

Format <type>[optional scope]: <description>

Allowed Types

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • chore: Changes to the build process or auxiliary tools and libraries such as documentation generation

Instructions

  1. Analyze the changes to determine the primary type.
  2. Identify the scope if applicable (e.g., specific component or file).
  3. Write a concise description in an imperative mood (e.g., "add feature" not "added feature").
  4. If there are breaking changes, add a footer starting with BREAKING CHANGE:.

Example feat(auth): implement login with google

Trustgrade A

  • 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.

  • passLicense

    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-8458239539652026-07-31