issue-review-two-phases-2

Reviewing staged git changes against an issue involves producing a structured improvement plan with What, Why, and Priority fields without applying edits. This validates code changes and identifies test file compaction opportunities before committing.

Test file compaction identifies opportunities to reduce test file size without losing coverage. It is a coordinated step in a staged changes review that helps streamline testing assets while maintaining validation integrity against the referenced issue.

Generating a structured improvement plan for staged work involves creating a numbered list of suggestions with What, Why, and Priority fields. The plan closes with a summary counting high, medium, and low priority items, ensuring no edits are applied.

Validating staged changes for an issue without modifying the code is possible through a plan-only review. It generates suggestions and checks test compaction opportunities, ensuring the staged work is assessed thoroughly before any edits are committed.

A structured improvement plan summary for staged changes includes a one-line summary counting how many suggestions are high, medium, and low priority. The full plan outputs numbered suggestions detailing What, Why, and Priority for each identified improvement.

A plan-only review for staged git changes is needed when you must validate work before committing but want to avoid direct edits. It is used to check, review, or validate staged work by producing structured improvement suggestions against a specific issue.