How do I install the Review Pre Commit skill?

Run npx skillmds@latest add openwpm/review-pre-commit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Review Pre Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Review Pre Commit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Review Pre Commit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Review Pre Commit?

openwpm (@openwpm) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Review Pre Commit by openwpm — Agent Skill

Name: Review Pre Commit
Author: openwpm

Review Pre Commit

Use as a pre-commit quality gate — review the working diff for stub patterns (TODO/FIXME/`unimplemented!()`/`todo!()`), debug leftovers (`dbg!`, stray `console.log`/`println!`, commented-out code), then run the project's lint, format, and test suites and verify the active crosslink issue is documented. Prints a PASS/FAIL checklist and hands off to `commit`. Trigger when the user says "review my changes", "/review", "ready to commit?", or asks for a final pass before committing.

openwpm d60eead 3.1 KB Updated Sep 17, 2026

File contents

Review — pre-commit quality gate

You are about to commit. Run through this structured review to catch issues before they land.

1. Review full diff

jj diff

Read through every change. Look for:

Correctness: does the logic do what it should?
Edge cases: are boundary conditions handled?
Security: any injection, hardcoded secrets, or unsafe patterns?

2. Scan for stub patterns

Search the diff for patterns that indicate incomplete work:

TODO, FIXME, HACK, XXX
pass (Python), unimplemented!() / todo!() (Rust)
throw new Error("not implemented")
Empty function bodies or placeholder returns
... as implementation

If found: fix them now. Do not commit stubs.

3. Check for debug leftovers

Search for debug code that shouldn't be committed:

dbg!() (Rust)
console.log used for debugging (not logging)
print( / println! used for debugging
Commented-out code blocks (more than 2 consecutive commented lines)

If found: remove them.

4. Run lint and format checks

Detect the project's toolchain and run the appropriate checks:

Rust (if Cargo.toml exists):

cargo clippy -- -D warnings
cargo fmt --check

Python (OpenWPM — black/isort/mypy via pre-commit):

jj-precommit

Extension (TypeScript — run from the Extension/ dir; root package.json has no lint script):

cd Extension && npm run lint

Go (if go.mod exists):

go vet ./...
gofmt -l .

Elixir (if mix.exs exists):

mix format --check-formatted
mix credo --strict

Fix any issues found before proceeding.

5. Run test suite

Run the project's test suite:

Python (OpenWPM): pytest (markers pyonly / slow; spins a local HTTP server + real Firefox)
Extension: cd Extension && npm test (build + lint)
Rust: cargo test
Go: go test ./...
Elixir: mix test --seed 0

All tests must pass before committing.

6. Verify crosslink issue documentation

Check that the active crosslink issue has appropriate documentation:

crosslink session status

If working on an issue, verify it has a plan comment and will get a result comment:

crosslink issue show <issue-id>

7. Print checklist

Print a pass/fail summary:

Review checklist:
  [PASS] No stub patterns
  [PASS] No debug leftovers
  [PASS] Lint clean
  [PASS] Format clean
  [PASS] Tests pass
  [PASS] Issue documented

Ready to commit. Proceeding to commit skill.

If any items fail, fix them first, then re-run the failed checks.

Once all checks pass, hand off to the commit skill.

---name: review-pre-commitdescription: Use as a pre-commit quality gate — review the working diff for stub patterns (TODO/FIXME/`unimplemented!()`/`todo!()`), debug leftovers (`dbg!`, stray `console.log`/`println!`, commented-out code), then run the project's lint, format, and test suites and verify the active crosslink issue is documented. Prints a PASS/FAIL checklist and hands off to `commit`. Trigger when the user says "review my changes", "/review", "ready to commit?", or asks for a final pass before committing.---# Review — pre-commit quality gateYou are about to commit. Run through this structured review to catch issues before they land.## 1. Review full diff```bashjj diff```Read through every change. Look for:- Correctness: does the logic do what it should?- Edge cases: are boundary conditions handled?- Security: any injection, hardcoded secrets, or unsafe patterns?## 2. Scan for stub patternsSearch the diff for patterns that indicate incomplete work:- `TODO`, `FIXME`, `HACK`, `XXX`- `pass` (Python), `unimplemented!()` / `todo!()` (Rust)- `throw new Error("not implemented")`- Empty function bodies or placeholder returns- `...` as implementationIf found: fix them now. Do not commit stubs.## 3. Check for debug leftoversSearch for debug code that shouldn't be committed:- `dbg!()` (Rust)- `console.log` used for debugging (not logging)- `print(` / `println!` used for debugging- Commented-out code blocks (more than 2 consecutive commented lines)If found: remove them.## 4. Run lint and format checksDetect the project's toolchain and run the appropriate checks:**Rust** (if `Cargo.toml` exists):```bashcargo clippy -- -D warningscargo fmt --check```**Python** (OpenWPM — black/isort/mypy via pre-commit):```bashjj-precommit```**Extension** (TypeScript — run from the `Extension/` dir; root `package.json` has no lint script):```bashcd Extension && npm run lint```**Go** (if `go.mod` exists):```bashgo vet ./...gofmt -l .```**Elixir** (if `mix.exs` exists):```bashmix format --check-formattedmix credo --strict```Fix any issues found before proceeding.## 5. Run test suiteRun the project's test suite:- Python (OpenWPM): `pytest` (markers `pyonly` / `slow`; spins a local HTTP server + real Firefox)- Extension: `cd Extension && npm test` (build + lint)- Rust: `cargo test`- Go: `go test ./...`- Elixir: `mix test --seed 0`All tests must pass before committing.## 6. Verify crosslink issue documentationCheck that the active crosslink issue has appropriate documentation:```bashcrosslink session status```If working on an issue, verify it has a plan comment and will get a result comment:```bashcrosslink issue show <issue-id>```## 7. Print checklistPrint a pass/fail summary:```Review checklist: [PASS] No stub patterns [PASS] No debug leftovers [PASS] Lint clean [PASS] Format clean [PASS] Tests pass [PASS] Issue documentedReady to commit. Proceeding to commit skill.```If any items fail, fix them first, then re-run the failed checks.Once all checks pass, hand off to the `commit` skill.

Frequently asked questions