skills.rest
gyuha
gyuhaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sg-review

Review git-changed files and write findings to SUMMARY.md and HANDOFF.md.

2|Updated May 15, 2026
Search Tags:#static analysis#code review#documentation#requirements validation#phase planning#git diff#learning loop
One-click install
npx skills add https://github.com/gyuha/super-gsd --skill sg-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sg-review
Source: https://github.com/gyuha/super-gsd/tree/main/.agents/skills/sg-review
Command: npx skills add https://github.com/gyuha/super-gsd --skill sg-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the fragile, manual handoff needed to review changes by performing a direct prose code review on the user’s modified files and recording the results for the next learning step.

Core Features & Use Cases

  • Direct git-range review: Computes a BASE..HEAD range (or uses an explicit SHA/range) and identifies changed files to review.
  • Plan-aware findings: Reads the current phase from planning state and pulls phase requirements from the matching PLAN file when available.
  • Durable workflow outputs: Writes a consolidated finding summary to SUMMARY.md and appends a review entry row to .planning/HANDOFF.md for traceability.
  • Works without Superpowers code review: Performs the review directly in prose mode because Superpowers integration is unavailable on this platform.

Quick Start

Run sg-review to review changes in your current working branch against the inferred base commit, then save findings to SUMMARY.md and record the handoff to HANDOFF.md.

Frequently Asked Questions about sg-review

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

FAQPage Schema
How do I review git diff changes against phase requirements without a dedicated code review tool?▼

Perform a prose code review directly on git-changed files between a computed BASE_SHA and HEAD_SHA. It reads phase context from .planning/STATE.md and requirements from the matching PLAN file to generate actionable findings without needing external tools.

What is a prose code review for a git working branch?▼

A prose code review reads modified git files directly, extracts phase context from .planning/STATE.md, and validates implementation against matching PLAN file requirements. It writes results to SUMMARY.md and records entries in .planning/HANDOFF.md.

Can I validate implementation against planning requirements when Superpowers code review is unavailable?▼

Yes, you can validate implementation by running a direct prose review that reads changed files and extracts phase requirements from your PLAN file. It bypasses unavailable Superpowers integration and still records validated results in SUMMARY.md and .planning/HANDOFF.md.

How do I record code review results for a learning loop workflow?▼

Record code review results by writing a consolidated finding summary to SUMMARY.md and appending a review entry row to .planning/HANDOFF.md. This creates durable traceability for your GSD to Superpowers to sg-retro learning loop.

Do I need to specify a base commit range for git code review?▼

No, you do not need to specify a base commit manually. The review automatically computes a BASE..HEAD git range from your working branch, though you can also provide an explicit SHA or range if needed.

Related Skills

Explore More Software Engineering Skills→
alffeialffei
69

requesting-code-review

Dispatch a code-reviewer subagent to validate git changes before merging.

Community
Intermediate
gyuhagyuha
2

sg-health

Validate GSD, Superpowers, and hook installation and registration with OK/WARN/FAIL reports.

Community
Basic
gyuhagyuha
2

sg-new

Start a new GSD milestone and recommend the next not-started phase.

Community
Intermediate
Fantasia1999Fantasia1999

code-reviewer

Analyze git diffs for complexity, risk, and SOLID violations across multiple languages.

Community
Advanced