issue-review-two-phases-2

Review staged git changes against an issue and output a numbered improvement plan.

Updated Mar 24, 2026

Search Tags:#git #refactoring #plan #code-review #issue-tracking #staged-changes #test-compaction

Ready to run

npx skills add https://github.com/stevenengland/sten-agent-skills --skill issue-review-two-phases-2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-review-two-phases-2
Source: https://github.com/stevenengland/sten-agent-skills/tree/main/skills/issue-review-two-phases-2
Command: npx skills add https://github.com/stevenengland/sten-agent-skills --skill issue-review-two-phases-2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review staged changes against an issue. Produces a structured improvement plan — no edits applied. Also identifies test file compaction opportunities. Use when asked to check, review, or validate staged work before committing. Part 2 of 3 in the issue-review-two-phases workflow.

Core Features & Use Cases

Step 1 — Change Review: Invoke your plan-reviewer skill and follow the process to generate a structured improvement plan.
Step 2 — Test Compaction: Invoke your test-file-compaction skill. Identify opportunities to reduce test file size without losing coverage.
Output: Produce a numbered list of suggestions with What, Why, and Priority fields. Close with a one-line summary: how many suggestions are high, medium, and low priority.

Quick Start

Review the current staged changes against the referenced issue and generate a structured improvement plan without applying any edits.

Frequently Asked Questions about issue-review-two-phases-2

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

FAQPage Schema

How do I review staged git changes against an issue before committing?▼

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.

What is test file compaction in a code review plan?▼

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.

How to generate a structured improvement plan for staged work without applying edits?▼

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.

Can I validate staged changes for an issue without modifying the code?▼

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.

What does a structured improvement plan summary for staged changes include?▼

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.

When do I need a plan-only review for staged git changes?▼

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.