pre-commit-reviewer

Review git diffs to comment out debug logging and flag TODOs.

25|5|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/Nimbalyst/skills --skill pre-commit-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-commit-reviewer
Source: https://github.com/Nimbalyst/skills/tree/main/skills/dev/pre-commit-reviewer
Command: npx skills add https://github.com/Nimbalyst/skills --skill pre-commit-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain code quality and consistency by automatically identifying and flagging common issues like debug logging, TODOs, and dead code before a commit is finalized.

Core Features & Use Cases

  • Debug Logging Removal: Comments out console.log and other verbose debug statements.
  • TODO/FIXME Flagging: Identifies and flags incomplete work items.
  • Dead Code Detection: Spots commented-out code blocks and unused variables.
  • Plan Status Check: Briefly reviews frontmatter of committed plan documents.
  • Use Case: Before committing a feature branch, use this skill to ensure no stray console.log statements or unfinished // TODO comments are included in the production code.

Quick Start

Use the pre-commit-reviewer skill to check the current git diff for debug logging and TODO comments.

Frequently Asked Questions about pre-commit-reviewer

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

FAQPage Schema
How do I automatically remove console.log statements before a git commit?

You can automatically clean up debug logging by reviewing your git diff to identify and comment out stray console.log statements. This ensures debug logging is excluded before finalizing a commit.

What is the best way to flag TODOs and FIXMEs in a git diff?

The best way to flag TODOs and FIXMEs in a git diff is to scan the changes for incomplete work items before committing. This detectsunfinished tasks and ensures code quality standards are met prior to the commit.

How do I detect dead code and unused variables before committing code?

You detect dead code and unused variables before committing by reviewing the git diff for commented-out code blocks. This process spots dead code to ensure your committed branch remains clean and maintainable.

Can I check plan document completion status during a pre-commit code review?

Yes, you can check plan document completion status during a pre-commit review by validating the document's frontmatter. This briefly reviews the committed plan documents to confirm their completion status.

Does pre-commit code review work without additional dependencies?

Pre-commit code review works without additional dependencies by analyzing the git diff directly. It identifies debug logging, TODOs, and dead code natively to ensure code quality before commits.