Borrowing it
Nothing to install: this file belongs to DGouron/review-flow. 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/DGouron/review-flow/master/.claude/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/DGouron/review-flowWrote 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/dgouron/review-flow/commit)<a href="https://agentmods.dev/skills/dgouron/review-flow/commit"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/commit/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/dgouron/review-flow/commit"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 120 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Excessive Agency · line 20 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 112 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 123 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00030 | $0.00965 |
| Opus 5.5 | $0.00012 | $0.00386 |
| Sonnet 5.5 | $0.00006 | $0.00193 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
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 2mo 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit - Safe Git Workflow
Persona
Read .claude/roles/senior-dev.md — adopt this profile and follow all its rules.
Activation
This skill activates:
- On explicit request (
/commit) - When the user asks to commit/push code
Husky Hooks (automatic)
The project uses Husky which automatically runs:
| Hook | Action |
|---|---|
pre-commit |
TypeScript check + Biome lint (modified files) |
commit-msg |
commitlint (message format) |
pre-push |
Vitest tests (modified files since test) |
Claude Code Hooks (automatic)
The project also has PreToolUse hooks that run BEFORE git commands:
| Hook | Action |
|---|---|
protect-main-branch.sh |
Blocks commit on master |
pre-commit-gate.sh |
Runs tests before commit |
verify-spec-updated.sh |
Checks spec has ## Status: implemented |
protect-main-push.sh |
Blocks push to master and force push |
Workflow
Step 0: Quality Gates (BLOCKING)
BEFORE any commit, run:
yarn verify
If it fails: display errors and STOP. Do not commit until quality gates pass.
Step 0b: Spec & Tracker Verification
If staged files include src/ code:
- Check
docs/feature-tracker.md— any feature inimplementingstatus should be updated toimplemented - Check corresponding spec — should have
## Status: implementedif feature is complete - If missing, WARN the user (the hook will also catch this)
Step 1: Analyze Changes
git status --short
If nothing is staged, suggest:
git add <files>
Step 2: Create the Commit
Message Format (Conventional Commits)
<type>(<scope>): <description>
Allowed types:
| Type | Usage |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Formatting (no code change) |
refactor |
Refactoring (no new feature or fix) |
perf |
Performance improvement |
test |
Adding or fixing tests |
build |
Build system changes |
ci |
CI/CD changes |
chore |
Maintenance, dependencies |
revert |
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.
- 2mo ago First seen · 159 lines · 30 tokens per session scan A b998567b5217
commit is a skill published in the GitHub repository DGouron/review-flow (44 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 965 once invoked, about $0.0001 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-30.
Other skills, from other repositories
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
compiler-verify
Use when you need to run all compiler checks (tests, lint, format) before committing. Detects whether TS or Rust code changed and runs the appropriate checks.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
brooks-test
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow…
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…