code-review

Review code diffs against project specs, decisions, and FLOW_RULES.

6|Updated May 29, 2026
One-click install
npx skills add https://github.com/fusebase-dev/fusebase-flow --skill code-review-fusebase-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/fusebase-dev/fusebase-flow/tree/main/flow-skills/code-review
Command: npx skills add https://github.com/fusebase-dev/fusebase-flow --skill code-review-fusebase-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shipping code with undetected spec violations, scope creep, or maintainability issues leads to costly rollbacks, rework, and broken user experiences. This Skill eliminates that risk by performing a thorough independent review of code diffs before commit, deploy, or PR merge, surfacing only critical blockers and actionable improvements.

Core Features & Use Cases

  • Pre-ship diff validation: Reviews code changes against the project spec, locked product decisions, and FLOW_RULES to catch compliance gaps before they reach production.
  • Prioritized issue surfacing: Clearly distinguishes must-fix blockers from non-blocker improvements, so teams can address critical risks without delaying low-priority refinements.
  • Use case: Before merging a PR for a new client-facing feature, run this review to confirm the implementation matches the original spec, adheres to locked product decisions, and has no rollback safety risks.

Quick Start

Ask the AI to review the current code diff against the project specification before you commit or deploy any changes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I validate code diffs against project specifications before deployment?

Pre-ship diff validation reviews code changes against the project spec, locked product decisions, and FLOW_RULES to catch compliance gaps before they reach production. It clearly distinguishes must-fix blockers from non-blocker improvements so teams can address critical risks without delaying refinements.

What is the best way to catch scope creep and maintainability issues in a PR?

Catching scope creep and maintainability issues in a PR requires an independent code review that surfaces critical blockers and actionable improvements. It confirms the implementation matches the original spec, adheres to locked product decisions, and has no rollback safety risks before merging.

How do I check rollback safety for production code changes before commit?

Checking rollback safety for production code changes is performed by reviewing code diffs against FLOW_RULES and locked product decisions before commit. This pre-ship validation ensures the implementation has no rollback safety risks and satisfies decision compliance requirements.

Can I use automated diff review for AI-assisted development workflows?

Automated diff review can be used for AI-assisted development workflows by applying post-gate verification, midpoint refactor reviews, and team PR merge checks. It enforces comment policy and validates scope adherence against project specification contracts before deployment.

Does pre-ship code validation work without integrating external dependencies?

Pre-ship code validation works without external dependencies by performing an independent review of the code diff against the project spec and locked product decisions. It prioritizes issue surfacing to distinguish must-fix blockers from non-blocker improvements natively.