ferrox-code-review

Review changed source files and produce a severity-classified REVIEW.md artifact.

21|9|Updated Jul 21, 2026

Search Tags:#automation #code review #security #quality #bugs #phase workflow

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reviews code changes from a Ferrox Factory phase so bugs, security issues, and quality regressions are caught before the work is shipped.

Core Features & Use Cases

Phase-targeted review: Reviews the source files changed in a specific phase and produces a severity-classified REVIEW.md artifact.
Flexible depth control: Supports quick, standard, and deep review modes depending on how much analysis is needed.
Scoped file selection: Can review explicit files, phase summaries, or git-diff-derived changes with clear precedence rules.
Optional fix loop: Can spawn a fixer workflow to apply corrections and re-review the results.
Use case: A phase just finished and you want an automated review of the changed files before merge or ship.

Quick Start

Review phase 2 at standard depth and generate the review artifact.

Frequently Asked Questions about ferrox-code-review

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

FAQPage Schema

How do I automate code review for changed files before a merge?▼

Automate code review by analyzing changed source files from a phase workflow to identify bugs, security vulnerabilities, and quality regressions. It produces a severity-classified REVIEW.md artifact to highlight findings before shipping.

What is the best way to review git diffs for security vulnerabilities?▼

Reviewing git diffs for security vulnerabilities is handled by analyzing the derived changes with configurable depth modes. You can scope reviews to explicit files or diffs to ensure security issues are caught before work is shipped.

Can I scope an automated code review to specific source files?▼

Yes, you can scope automated code reviews to specific source files. The skill supports explicit file selection, phase summaries, or git-diff-derived changes with clear precedence rules to target the exact files you need checked.

How do I automatically fix bugs found during a code review?▼

Automatically fix bugs found during a code review by using the optional fix loop feature. It spawns a fixer workflow to apply corrections to the identified issues and then re-reviews the updated results to verify the resolutions.

Does code review depth affect bug detection in phase workflows?▼

Yes, code review depth affects bug detection in phase workflows. You can select quick, standard, or deep review modes to control the analysis depth, matching the level of scrutiny needed for your source file changes before shipping.