Skip to content

mgiovani/ai-arsenal / skills/git-commit

git-commit

Verified

Generate a conventional commit message (conventionalcommits.org) from the staged/unstaged diff and create the commit. Use when the user wants to commit, stage changes, or needs a commit message written. Not for release commits or changelogs (use git-release) or branch-finish workflows (use gitflow).

FileKindSize
SKILL.mdskill md3.3 KB
evals/evals.jsonconfig1.8 KB
evals/trigger-eval.jsonconfig1.6 KB
scripts/pre-commit-lint.shexecutablescript4.7 KB

evals/evals.json

View on GitHub
{
  "skill": "git-commit",
  "evals": [
    {
      "id": "single-feature-commit",
      "prompt": "/git-commit I added OAuth2 login support to the auth module, please commit it",
      "assertions": [
        "Runs git status and git diff --staged (or git diff) before drafting a message",
        "Produces a conventional commit in the form type(scope): description",
        "Uses feat as the type since a new feature was added",
        "Description is in imperative mood (e.g. 'add' not 'added') and roughly 50 characters or less",
        "Creates the commit via git commit rather than only printing the message"
      ]
    },
    {
      "id": "mixed-concerns-split",
      "prompt": "/git-commit commit my changes: I fixed a null pointer bug in the user endpoint, updated the README, and bumped lodash",
      "assertions": [
        "Detects that the diff mixes unrelated concerns (fix, docs, dependency bump)",
        "Splits the work into separate commits by staging file groups individually with git add before each commit",
        "Assigns distinct correct types across the commits (fix, docs, build or chore for the dependency bump)",
        "Does not lump all three concerns into a single commit message"
      ]
    },
    {
      "id": "breaking-change-commit",
      "prompt": "/git-commit I removed the old calculate() method from the shopping cart and replaced it with computeTotal(), commit this",
      "assertions": [
        "Identifies the removed/changed export as a breaking change from the diff",
        "Appends ! after the type/scope in the commit header (e.g. feat(shopping-cart)!:)",
        "Includes a BREAKING CHANGE: footer describing the migration (calculate removed, use computeTotal)",
        "Asks for confirmation before committing given the breaking, non-trivial nature of the change"
      ]
    }
  ]
}
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 321kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 321kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 321kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 321kUpdated Claude CodeCodexVerifiedInstall