review

Review Git diffs for correctness, quality, and security before merging.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/RomainDECOSTER/ironforge --skill review-romaindecoster
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/RomainDECOSTER/ironforge/tree/main/copilot/skills/review
Command: npx skills add https://github.com/RomainDECOSTER/ironforge --skill review-romaindecoster

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews implemented code via agency-agents before merge. Delegates to engineering-code-reviewer on the diff, then testing-reality-checker for QA sign-off. Blocks on critical findings and loops back to /ironforge:implement for fixes.

Core Features & Use Cases

  • Two-pass review flow: initial code review followed by QA sign-off.
  • Blocking & remediation: halts merge on blocking issues and routes fixes back to implement.
  • Agent orchestration: uses agency-agents and specialized reviewers to ensure quality.

Quick Start

Run /ironforge:review to initiate the two-pass review workflow and obtain the actionable report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review and QA sign-off before merging a Git diff?

Automated code review and QA sign-off is handled by a two-pass agent workflow that analyzes a Git diff to verify correctness, quality, and security, producing blocking findings, non-blocking suggestions, and a final merge verdict.

How does the two-pass agent review workflow handle blocking findings?

The two-pass workflow delegates to specialized engineering and testing agents; when critical blocking findings are detected, it halts the merge process and loops back to the implementation phase for required remediation.

What inputs are needed to run an agent-assisted code review on my codebase?

Agent-assisted code review requires a Git diff, Sudocode specs, and architecture docs as inputs, which the agents rely on to evaluate changes and generate clear blocking or non-blocking suggestions.

Does the code review workflow support optional graph context for QA sign-off?

Yes, the code review and QA sign-off workflow supports optional graph context, applying it alongside the Git diff and architecture docs to ensure thorough correctness and security analysis before generating the final verdict.