ferrox-requesting-code-review

Reviews git diff changes for correctness, completeness, and production readiness before merging.

21|9|Updated Jul 21, 2026

Search Tags:#code review #quality gate #subagent #git diff #pre-merge

Ready to run

npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-requesting-code-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ferrox-requesting-code-review
Source: https://github.com/FerroxLabs/ferrox-factory/tree/main/skills-vendored/ferrox-requesting-code-review
Command: npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-requesting-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify completed work before it merges, so bugs, requirement gaps, and design mistakes are caught early instead of spreading through later tasks.

Core Features & Use Cases

Pre-merge review: Ask for a focused code review after finishing a task or major feature.
Task-by-task validation: Use it in subagent-driven workflows to review each increment against the plan.
Quality gate for changes: Check implementation accuracy, architecture, testing, and readiness before proceeding.
Use case: After adding a new feature, you can hand the reviewer the exact commit range and requirements so it evaluates the diff without being influenced by the rest of your session history.

Quick Start

Ask the assistant to review your completed change against the plan using the provided code reviewer template and the relevant git commit range.

Frequently Asked Questions about ferrox-requesting-code-review

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

FAQPage Schema

How do I review a git diff against requirements before merging?▼

To review a git diff against requirements before merging, provide a precise commit range so the reviewer can evaluate implementation accuracy, architecture, testing, and readiness without session history influence.

What is pre-merge code review in subagent-driven development?▼

Pre-merge code review in subagent-driven development validates each completed task increment against the original plan to catch bugs, requirement gaps, and design mistakes before they cascade into later work.

Can I use a quality gate to check production readiness for refactoring changes?▼

Yes, you can use a quality gate to check production readiness for refactoring changes by inspecting the exact git diff range to verify implementation accuracy, architecture, and testing.

How do I validate completed feature increments task-by-task?▼

Validate completed feature increments task-by-task by handing the reviewer the exact commit range and requirements for read-only inspection of the diff against the plan.

Do I need a specific git commit range to perform a code review?▼

Yes, you need a precise git diff range to perform a code review, ensuring the evaluation focuses strictly on the completed changes without being influenced by the rest of your session history.