Borrowing it
Nothing to install: this file belongs to paulbreuler/limps. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/paulbreuler/limps/main/.claude/skills/git-commit-best-practices/SKILL.mdgit clone --depth 1 https://github.com/paulbreuler/limpsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/paulbreuler/limps/git-commit-best-practices)<a href="https://agentmods.dev/skills/paulbreuler/limps/git-commit-best-practices"><img src="https://agentmods.dev/badge/skills/paulbreuler/limps/git-commit-best-practices/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/paulbreuler/limps/git-commit-best-practices"><img src="https://agentmods.dev/badge/skills/paulbreuler/limps/git-commit-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00041 | $0.02490 |
| Opus 5.5 | $0.00016 | $0.00996 |
| Sonnet 5.5 | $0.00008 | $0.00498 |
| Haiku 4.5 | $0.00004 | $0.00249 |
Grade A, and why
git-commit-best-practices 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Best Practices (limps)
Purpose
Guide the creation of clear, meaningful Git commits that follow conventional commit standards and repository-specific conventions. Ensures commits are atomic, well-documented, and integrate with automated tooling (release-please, changelog generation).
Scope
- If
$ARGUMENTSis "review-commits" or a commit range (e.g.,HEAD~5..HEAD,main..HEAD), review existing commits and suggest improvements. - If
$ARGUMENTSis a scope (paths or component), provide commit guidance for those changes. - If no arguments provided, guide commit message creation for staged changes.
Detecting Breaking Changes
When reviewing commits, detect breaking changes by:
- Parse commit messages:
git log --format="%H%n%s%n%b" <range>(includes full body) - Search for footer: Look for
BREAKING CHANGE:orBREAKING CHANGEin commit body (case-insensitive) - Extract description: Everything after
BREAKING CHANGE:until:- Next footer (e.g.,
Closes #123,Fixes #456) - End of commit message
- Empty line followed by non-footer text
- Next footer (e.g.,
- Example commands:
- Simple:
git log --format=%B main..HEAD | grep -A 10 -i "BREAKING CHANGE" - More robust:
git log --format="%H%n%s%n%b%n---" <range>then parse each commit separately
- Simple:
- Edge cases:
- Multi-line breaking changes: Extract until next footer or end
- Breaking change in subject: Look for
!after type/scope:feat!: breaking change - Merge commits: Check merge commit message for breaking changes
Conventional Commit Format
Structure
<type>(<scope>): <subject>
<body>
<footer>
Types
feat: New feature (triggers minor version bump)fix: Bug fix (triggers patch version bump)docs: Documentation changes onlystyle: Code style changes (formatting, whitespace, no logic change)refactor: Code refactoring (no feature change or bug fix)perf: Performance improvementstest: Adding or updating testschore: Maintenance tasks (deps, config, build)ci: CI/CD changesbuild: Build system changesrevert: Revert a previous commit
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.
- 1mo ago First seen · 284 lines · 41 tokens per session scan A 5e9df9986e55
git-commit-best-practices is a skill published in the GitHub repository paulbreuler/limps (10 stars, last pushed 7mo ago), licensed MIT. It adds 41 tokens to every session and 2,490 once invoked, about $0.0002 per session on Opus 5.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-31.
Other skills, from other repositories
git
Run git version control commands for repository management. Use when the user asks to check status, view history or diffs, stage and commit changes, manage branches, merge or rebase, work with remotes, stash changes, tag releases, cherry-pick commits, bisect regressions, resolve conflicts, manage worktrees or…
knowledge-shell-process-and-worktree
Shell and Git worktree support for running commands, managing long-lived processes, and giving sessions isolated working directories. A Git worktree is a separate checkout linked to the same repository.
commit
Conventional Commits 1.0 generator. Stages relevant files, infers type(scope): description, never uses --no-verify.
datalad
Retrieve, version, and publish scientific datasets with DataLad and git-annex, and capture computational provenance with datalad run, rerun, and containers-run. Use when cloning or fetching data from OpenNeuro, DANDI, datasets.datalad.org, or any DataLad dataset; when a file in a dataset reads as a broken symlink or a…
commit
Use when asked to commit, "commit this", "/commit", or to write a commit for the pending change — reviews what the change reaches outside its diff first, then commits with a message that names it.
pr-writer
Writes a pull-request description from the actual diff.