review-pre-commit

Scan the current diff for stubs, debug leftovers, and incomplete work.

27|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/forecast-bio/ferray --skill review-pre-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pre-commit
Source: https://github.com/forecast-bio/ferray/tree/main/.claude/skills/review-pre-commit
Command: npx skills add https://github.com/forecast-bio/ferray --skill review-pre-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable review process to catch stub patterns (TODO/FIXME/unimplemented!()/todo!()), debug leftovers (dbg!, console.log, println!), and stray commented code before commits, and to verify the repository's lint, format, and test gates.

Core Features & Use Cases

  • Enforces a deterministic pre-commit review of the working diff, scanning for incomplete work and debugging leftovers.
  • Validates that lint, format, and test suites pass, and checks for crosslink/documentation consistency.
  • Use Case: A developer says "review my changes" and receives a PASS/FAIL checklist with actionable remediation steps before committing.

Quick Start

Run the review-pre-commit skill on your current changes to produce a PASS/FAIL checklist and proceed to commit.

Frequently Asked Questions about review-pre-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my git diff for TODOs and debug leftovers before committing?

Pre-commit review scans your current git diff to identify and fix stubs, debug leftovers like console.log, and stray commented code before committing changes.

Can I run lint, format, and test checks as a pre-commit quality gate?

Yes, this quality gate enforces a deterministic pre-commit review by validating that lint, format, and test suites pass before allowing a commit.

How do I validate crosslink and documentation completeness in my working diff?

Pre-commit review checks crosslink and documentation consistency within the current working diff to ensure all references and docs remain complete.

What is the best way to catch incomplete work like unimplemented or todo macros before a commit?

A structured pre-commit review catches incomplete work by scanning the working diff for stub patterns including unimplemented, todo, and FIXME macros.

Do I get a checklist output when reviewing my changes for a commit?

Yes, reviewing your changes produces an auditable PASS or FAIL checklist with actionable remediation steps to hand off to the commit step.