Saucebox Registry
← Browse

@jahands/auto-commit

A

Git commit guidelines for incremental commits. Read this when user asks you to auto commit as you go

skillclaude

Install

agr install @jahands/auto-commit --target claude

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

  • .claude/skills/auto-commit/SKILL.md

Document

name: auto-commit description: Git commit guidelines for incremental commits. Read this when user asks you to auto commit as you go

Git Commit Guidelines

When making changes to code, commit your changes incrementally as you work.

Commit Format

<type>: <subject>

<body>

Commit Types

  • feat: New feature or functionality
  • fix: Bug fix
  • chore: Maintenance tasks, dependency updates, configuration changes
  • docs: Documentation only changes
  • style: Code style/formatting changes (no functional changes)
  • refactor: Code restructuring without changing functionality
  • test: Adding or modifying tests
  • perf: Performance improvements

Subject Line Rules

  • Maximum 90 characters
  • Start with lowercase
  • No period at the end
  • Use imperative mood ("add" not "adds" or "added")

Body Rules

  • Separate from subject with blank line
  • Wrap at 72 characters
  • Explain what and why, not how
  • Only include when the change requires context

Commit Frequency

  • Commit after each logical unit of change
  • Each commit should represent one coherent change
  • Don't bundle unrelated changes

Examples

Good Examples

feat: add user authentication middleware

Implements JWT-based authentication for API routes.
Includes token validation and refresh logic.

fix: resolve null pointer in user lookup

chore: update dependencies to latest versions

Bad Examples

feat: added new feature to the application that allows users to authenticate using JWT tokens and also fixed some bugs and updated dependencies

fix: Fixed bug.

Key Principles

  • Be concise but descriptive
  • One commit = one logical change
  • Commit message should make sense without looking at the code
  • Skip the body if the subject line is self-explanatory

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-22e3d15a7f702026-07-31