Change Plan Reviewer

The problem

Coding before planning leads to broken production data, circular dependencies, and massive PRs that are impossible to review. Developers often jump into implementation without considering backward compatibility, rollback procedures, or migration sequencing.

What it does

• Analyzes proposed file changes to identify missing dependencies or incorrect targets.
• Evaluates implementation sequences to prevent deployment-time failures in shared contracts or database migrations.
• Strips unrelated refactors and scope creep from the plan to keep PRs focused and safe.
• Defines mandatory test coverage and verification steps for each stage of the change.
• Provides a structured Ready/Revise/Do-not-execute verdict based on a 100-point quality rubric.

Why this beats prompting it yourself

Generic LLM prompts usually greenlight any plan that looks plausible. This skill applies a rigid risk catalog and execution-sequencing framework to catch subtle architectural violations, data integrity risks, and "point of no return" deployment flaws that simple prompts ignore.

Use cases

• Reviewing complex database schema migrations and data backfill strategies.
• Validating API contract changes between microservices to ensure backward compatibility.
• Refining high-risk infrastructure or authentication logic changes before touching a single file.
• Scoping feature implementations to ensure they don't leak logic across architectural boundaries.

Known limitations

This tool reviews plans but does not execute code, run tests, or modify files. It cannot verify findings perfectly if repository context (like full schema or architecture docs) is missing.