review-pre-commit

Scan working code diffs for stubs, debug leftovers, and crosslink documentation.

6|3|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/dollspace-gay/crosslink --skill review-pre-commit-dollspace-gay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pre-commit
Source: https://github.com/dollspace-gay/crosslink/tree/main/crosslink/resources/claude/skills/review-pre-commit
Command: npx skills add https://github.com/dollspace-gay/crosslink --skill review-pre-commit-dollspace-gay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of committing incomplete, broken, or poorly documented code that breaks the main codebase, requires extra cleanup work, and loses critical work context for future development sessions.

Core Features & Use Cases

  • Diff & Stub Scanning: Automatically detects stub patterns (TODO, FIXME, unimplemented!()) and debug leftovers (dbg!, console.log, commented-out code) in working diffs.
  • Multi-Language Quality Checks: Runs language-specific lint, format, and test suites for Rust, Node/TypeScript, Python, Go, and Elixir projects.
  • Crosslink Integration: Verifies active crosslink issues have proper documentation with plans and expected results to preserve work context across agent sessions.
  • Use Case: A developer finishing a bug fix can run this review to ensure no debug code is left, all tests pass, and the related crosslink issue is updated before committing, avoiding broken commits and missing context for future work.

Quick Start

Use the review-pre-commit skill to run a full pre-commit quality check on your current working diff before you commit your changes.

Frequently Asked Questions about review-pre-commit

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

FAQPage Schema
How do I prevent stub patterns and debug code from being committed?

To prevent stub patterns and debug code from being committed, you can run a pre-commit quality gate that scans working diffs for TODOs, FIXMEs, unimplemented!(), dbg!, and console.log artifacts before merge.

Can I run pre-commit lint and format checks across multiple programming languages?

Yes, you can run pre-commit lint and format checks across multiple languages, as this quality gate supports language-specific test suites and formatting for Rust, Node/TypeScript, Python, Go, and Elixir projects.

What is the best way to verify issue documentation before a code merge?

The best way to verify issue documentation before a code merge is to use a pre-commit review that checks active crosslink issues for proper plans and expected results, preserving work context for future agent sessions.

Does a pre-commit quality gate work with Rust and Elixir projects?

Yes, a pre-commit quality gate works with Rust and Elixir projects, automatically applying language-specific lint, format, and test checks to your working code diffs before they are merged into the main codebase.

Why do I need a pre-commit review to catch incomplete work?

You need a pre-commit review to catch incomplete work because it eliminates the risk of committing broken code that breaks the main codebase and loses critical work tracking context for future development sessions.