git-commit

A guide for making Git commits and pull requests in an organized way. It explains how to group changes, write commit messages, and open pull requests.

In plain words
What is it for?
Use it when committing code or opening a pull request with GitHub's command-line tool. It covers checking staged changes, splitting unrelated work, and recording tests or other checks.
Why use it?
It helps prevent unrelated files, secrets, or generated files from ending up in a commit. It also gives teams a shared format for describing changes.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/spinabot/brigade/git-commit
Any agent
npx skills add spinabot/brigade --skill git-commit
Clone the repo
git clone --depth 1 https://github.com/spinabot/brigade

Made for: Claude Code, Codex.

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 376 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00046 $0.00376
Opus 5 $0.00023 $0.00188
Sonnet 5 $0.00009 $0.00075
Haiku 4.5 $0.00005 $0.00038

Measured 2d ago against content hash accbb47fe093, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-commit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/git-commit/SKILL.md · 41 lines

What it actually says

Git commits & PRs

Use this when committing changes or opening a pull request.

Before committing

  • Run git status and git diff --staged to see exactly what's going in. Never git add -A blindly — stage the files that belong to this change.
  • Keep one logical change per commit. If the diff does two unrelated things, make two commits.
  • Don't commit secrets, large binaries, or generated artifacts. Check .gitignore covers them.

Message format

Conventional Commits:

<type>(<optional scope>): <short imperative summary>

<optional body — what changed and WHY, wrapped at ~72 cols>

Types: feat, fix, docs, refactor, test, chore, perf, build, ci.

  • Summary in the imperative mood ("add", not "added"), ≤72 chars, no trailing period.
  • The body explains the reasoning a future reader needs — not a restatement of the diff.

Pull requests (gh CLI)

  • git push -u origin <branch> then gh pr create --fill (or --title/--body).
  • PR body: what changed, why, and how it was verified (tests run, manual checks).
  • Confirm the base branch is correct before creating.

Conventions to honor

Match the repository's existing style — read recent git log --oneline first and follow whatever format the project already uses if it differs from the above.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 41 lines · 46 tokens per session scan A accbb47fe093

Subscribe to this mod's changes

git-commit is a skill published in the GitHub repository spinabot/brigade (3,186 stars, last pushed 5d ago), licensed MIT. It adds 46 tokens to every session and 376 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.