flow-code-review

Review branch diffs against repository standards and specs with ranked actionable findings.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/AO-HyS/aohys.com --skill flow-code-review-ao-hys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flow-code-review
Source: https://github.com/AO-HyS/aohys.com/tree/main/.agents/skills/flow-code-review
Command: npx skills add https://github.com/AO-HyS/aohys.com --skill flow-code-review-ao-hys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss either convention violations or spec mismatches, and findings arrive unranked or duplicated. This Skill structures a diff review along two axes—Standards and Spec—so every finding is validated, deduplicated, and ranked by user impact. ## Core Features & Use Cases - Dual-axis review: Inspects the diff against repository standards (AGENTS.md, conventions, security, correctness) and against the spec (missing requirements, scope creep, incorrect behavior). - Proportional isolation: Uses a single reviewer for ordinary changes and blind independent reviewers for security, migrations, or cross-cutting changes. - Verified, ranked findings: Validates each candidate against the actual diff, merges duplicates, and ranks by regression risk with tight file and line references. - Use Case: Before merging a pull request, run the review to get an integrated list of actionable findings plus a Standards/Spec verdict and residual verification gaps. ## Quick Start Review the current branch diff against the repo standards and the linked spec, then rank the actionable findings.

Frequently Asked Questions about flow-code-review

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

FAQPage Schema
How do I review a pull request diff against a spec?▼

Provide the branch or fixed point and the spec source, and the review runs two lanes: Standards checks conventions, security, and correctness, while Spec checks missing requirements and scope creep. Findings are validated against the actual diff and ranked by user impact.

How is the base branch for the diff comparison chosen?▼

The fixed point comes from the user, or is inferred from the pull request base, configured upstream, remote default branch, then origin/develop, origin/main, or origin/master. The ref must resolve and produce a non-empty three-dot diff before review starts.

When does the review use independent reviewers?▼

Independent blind reviewers are used when security, migrations, cross-cutting changes, or an explicit user request justify them. Ordinary changes are reviewed by a single reviewer covering both Standards and Spec axes.

What happens if there is no spec for the change?▼

If no spec is found in issue references, user-supplied paths, or docs/, specs/, or .scratch/ directories, the Spec lane is skipped and the review states that explicitly. The Standards lane still runs normally.

Does the review modify the code it finds problems with?▼

No. The review only reports validated, ranked findings with file and line references. Product code is edited only when the user explicitly asks to address the findings.