Gentleman Guardian Angel is an AI code-review tool that checks staged files against a repository’s coding standards. Developers use it as a Git pre-commit hook or to review full pull requests, with different AI providers available. The catalogue add-ons support its workflows.
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.
npx skills add Gentleman-Programming/gentleman-guardian-angel --skill commit-hygienegit clone --depth 1 https://github.com/Gentleman-Programming/gentleman-guardian-angelWrote 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/gentleman-programming/gentleman-guardian-angel/commit-hygiene)<a href="https://agentmods.dev/skills/gentleman-programming/gentleman-guardian-angel/commit-hygiene"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentleman-guardian-angel/commit-hygiene/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/gentleman-programming/gentleman-guardian-angel/commit-hygiene"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentleman-guardian-angel/commit-hygiene.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.00602 |
| Opus 5 | $0.00000 | $0.00301 |
| Sonnet 5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
commit-hygiene 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 9d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: gga-commit-hygiene
Purpose
Enforce conventional commits and a clean, readable history for GGA.
When to Use
Any commit creation, review, or branch cleanup.
Format
type(scope): description
Validated by regex:
^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)(\([a-z0-9\._-]+\))?!?: .+
Valid Types
| Type | Use For |
|---|---|
| feat | New feature or behavior |
| fix | Bug fix |
| docs | Documentation only |
| chore | Maintenance, dependencies, tooling |
| refactor | Restructuring without behavior change |
| test | Adding or fixing tests |
| ci | CI/CD pipeline changes |
| style | Formatting, whitespace, no logic change |
| perf | Performance improvement |
| build | Build system, Makefile changes |
| revert | Reverting a previous commit |
Valid Scopes for GGA
| Scope | Covers |
|---|---|
| providers | lib/providers.sh, any AI provider integration |
| hooks | Hook system, marker injection, pre-commit logic |
| cache | lib/cache.sh, hash logic |
| cli | bin/gga flags, argument parsing, output |
| ci | GitHub Actions workflows |
| config | .gga config file parsing |
| install | install.sh, uninstall.sh |
Critical Rules
- NEVER add
Co-Authored-Byor any AI attribution trailers - One logical change per commit — no "add X and fix Y and update docs"
- Use imperative mood: "add" not "added", "fix" not "fixed"
- Reference issue numbers when relevant:
feat(providers): add GitHub Models support (#12) - Keep subject line ≤ 72 characters
- If a commit needs explanation, add a body separated by a blank line
Examples
feat(providers): add GitHub Models provider support
fix(hooks): resolve marker injection in existing hooks
fix(cache): handle hash collision on empty files
test(cache): add unit tests for hash invalidation
test(hooks): add integration tests for marker injection
refactor(cli): extract provider dispatch to lib/providers.sh
ci: split unit and integration test jobs
docs(contributing): add label system documentation
chore: update shellspec to 0.28.1
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.
- 9d ago First seen · 86 lines · 0 tokens per session scan A 4de554b12ee2
commit-hygiene is a skill published in the GitHub repository Gentleman-Programming/gentleman-guardian-angel (1,145 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 602 tokens. 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.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…