prepare-staged-for-review

Review staged code changes for cleanup, bugs, security, and refactoring.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/swtch1/dotfiles --skill prepare-staged-for-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prepare-staged-for-review
Source: https://github.com/swtch1/dotfiles/tree/main/.claude/skills/prepare-staged-for-review
Command: npx skills add https://github.com/swtch1/dotfiles --skill prepare-staged-for-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers ensure their staged code is clean, bug-free, and adheres to project standards before committing or pushing.

Core Features & Use Cases

  • Code Cleanup: Removes debug statements, dead code, and unused imports.
  • Bug & Security Assessment: Analyzes for boundary conditions, input validation issues, and potential security vulnerabilities.
  • Refactoring: Suggests and applies safe, behavior-preserving refactors.
  • Test Code Review: Evaluates test coverage and adherence to best practices.
  • Use Case: Before submitting a pull request, use this Skill to perform a thorough pre-review of your staged changes, catching potential issues and improving code quality.

Quick Start

Use the prepare-staged-for-review skill to review my staged code changes in the current directory.

Frequently Asked Questions about prepare-staged-for-review

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

FAQPage Schema
How do I review staged git changes for bugs and security issues before committing?

To review staged git changes, analyze the diff for boundary conditions, input validation issues, and potential security vulnerabilities. This pre-commit process ensures your staged code is clean and bug-free before you push it to a repository.

What is the best way to remove debug statements and dead code from staged files?

Code cleanup removes debug statements, dead code, and unused imports directly from your staged changes. This refactoring process ensures only necessary, behavior-preserving code is committed, improving overall code quality and maintainability.

Can I check test code coverage and project conventions on staged changes?

Yes, you can check test code coverage and project conventions on staged changes. The review evaluates test coverage against best practices and ensures adherence to project-specific standards, catching compliance issues early in development.

How do I perform a pre-commit refactoring assessment on my staged code?

Pre-commit refactoring assessment analyzes your staged code to suggest and apply safe, behavior-preserving refactors. It identifies architectural violations and improvement opportunities to optimize the code structure before final submission.

Does this pre-commit review work for analyzing backwards compatibility?

Yes, this pre-commit review works for analyzing backwards compatibility. It assesses your staged changes to ensure new modifications do not break existing functionality, maintaining system stability and architectural integrity.

Why should I run a pre-commit code review instead of waiting for the pull request?

Running a pre-commit code review catches potential issues before submitting a pull request. It performs a thorough check for cleanup, bugs, and security vulnerabilities early, reducing review iterations and improving code quality beforehand.