gf-code-review

Review code changes against the active GuanFu plan for quality gaps.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/Sailfishc/guanfu --skill gf-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gf-code-review
Source: https://github.com/Sailfishc/guanfu/tree/main/skills/gf-code-review
Command: npx skills add https://github.com/Sailfishc/guanfu --skill gf-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review implementation against the active plan, code quality, tests, verification evidence, architecture, and GuanFu taste.

Review catches the pattern, not just the bug. Findings route automatically to work, doc review, compound, or evolve.

Core Features & Use Cases

  • Checks plan compliance, code quality, tests, and verification evidence.
  • Routes findings to appropriate follow-up actions (gf-work, gf-doc-review, gf-compound, or gf-evolve).
  • Supports traceability and governance of code changes across GuanFu slices.

Quick Start

Initiate a review by providing the changed files and the active plan slice to trigger the review workflow.

Frequently Asked Questions about gf-code-review

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

FAQPage Schema
How do I review code quality and plan compliance for repository patches?

Review code quality and plan compliance by analyzing patches and diffs against the active GuanFu plan. This identifies gaps in tests, architecture, and verification evidence, routing findings to prescribed follow-up actions.

What is the best way to ensure code changes align with active plan slices?

Ensure code changes align with active plan slices by checking implementation against plan requirements and GuanFu taste. The review catches implementation patterns, verifying traceability and governance across repository modules.

How do I route code review findings to the correct follow-up workflow?

Route code review findings automatically to appropriate workflows like gf-work, gf-doc-review, or gf-compound. This ensures documentation, traceability, and escalation requirements are satisfied through prescribed review routes.

How do I start a code review for a specific plan slice?

Start a code review by providing the changed files and the active plan slice. This triggers the review workflow, which evaluates code quality, tests, and verification evidence against the active plan.

Can I check verification evidence and tests during a code review?

Check verification evidence and tests during code review by analyzing gaps in the implementation. The review evaluates provided patches and diffs, ensuring all tests and evidence satisfy active plan requirements.

Why does code review focus on catching patterns instead of just bugs?

Catching patterns instead of just bugs ensures broader code quality and architecture alignment. Reviewing implementation against the active GuanFu plan identifies systemic issues, routing findings to work, doc review, compound, or evolve actions.