commit

A guided Git workflow for checking code, creating commits that follow project rules, and pushing them safely.

In plain words
What is it for?
Use it when committing or pushing code in projects that use TypeScript, Biome, Vitest, Husky, and related repository checks.
Why use it?
It helps prevent commits with failing checks, invalid messages, outdated specifications, or changes sent to protected branches.

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/dgouron/review-flow/commit
Any agent
npx skills add DGouron/review-flow --skill commit
Clone the repo
git clone --depth 1 https://github.com/DGouron/review-flow

Made for: Claude Code, Codex.

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 965 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.00030 $0.00965
Opus 5 $0.00015 $0.00483
Sonnet 5 $0.00006 $0.00193
Haiku 4.5 $0.00003 $0.00097

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

Security

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 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.

.claude/skills/commit/SKILL.md · 159 lines

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:

  1. Check docs/feature-tracker.md — any feature in implementing status should be updated to implemented
  2. Check corresponding spec — should have ## Status: implemented if feature is complete
  3. 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

Read the full file on GitHub · 159 lines

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 · 159 lines · 30 tokens per session scan A b998567b5217

Subscribe to this mod's changes

commit is a skill published in the GitHub repository DGouron/review-flow (42 stars, last pushed 18d ago), licensed MIT. It adds 30 tokens to every session and 965 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.

Related

Other skills, from other repositories

industry-chain

产业链下钻与不可替代性判定方法:以龙头为"需求入口"沿供应链逐层下钻(整机 / 龙头 → 部件 → 核心器件 → 材料 → 衬底与设备),用物理 / 材料约束(扩产周期、良率、认证周期、有无替代)当筛子找供给刚性的卡口;给每个标的贴不可替代性标签(techmoat / capacitymoat / both / 待补)并列证据;含"卡口越硬越贵"与预期差四问的校准。当任务涉及产业链位置、上下游、护城河、不可替代性、供给瓶颈、竞争格局时加载;单纯取数、估值计算、财报拆分等不涉及产业链结构的任务不要加载。只产出框架与证据表,不给投资动作建议。.

simonlin1212/Vibe-Research · 212 tokens

selecting-vizro-charts

Use this skill when choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards, or adding tables (AG Grid) to Vizro dashboards. Activate when the user asks which chart fits their data, needs custom chart functions, wants to set colors or palettes, is creating KPI metric cards, or…

mckinsey/vizro · 78 tokens

verify-changes

Verify a code change in this repo before committing or opening a PR. Use after editing collector (backend), web (frontend), shared package, or the Go agent — picks the minimal sufficient check set per touched area.

foru17/neko-master · 47 tokens

openai-docs

Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations (for example: Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, model capabilities or limits); prioritize OpenAI docs MCP tools and restrict any fallback browsing to…

Soju06/codex-lb · 74 tokens

new-skill

Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…

hyhmrright/brooks-lint · 145 tokens

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…

hyhmrright/brooks-lint · 178 tokens