ferrox-ns-review

Route review and quality intents to the correct specialized Ferrox skill.

21|9|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-ns-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ferrox-ns-review
Source: https://github.com/FerroxLabs/ferrox-factory/tree/main/skills/ferrox-ns-review
Command: npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-ns-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes guesswork when a user needs a quality, review, audit, or debugging workflow by directing the request to the correct specialized Ferrox skill.

Core Features & Use Cases

  • Intent Routing: Maps user goals to the appropriate downstream skill for code review, security review, UI review, debugging, forensics, or evaluation.
  • Review Workflow Selection: Distinguishes between analysis, fix, audit, and validation paths so the right process is used from the start.
  • Use Case: If a user asks to review a failing feature, the skill routes them to the debugging path instead of a generic review flow.

Quick Start

Ask the skill to route your request to the correct Ferrox quality, review, or audit skill based on your goal.

Frequently Asked Questions about ferrox-ns-review

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

FAQPage Schema
How do I route a code review or debugging request to the right workflow?

Route code review and debugging requests by classifying your intent, which directs the goal to the correct specialized skill for analysis, security review, or forensics. Intent classification ensures the appropriate quality workflow is invoked from a single request.

What is the best way to distinguish between a code audit and a validation scenario?

Distinguish between a code audit and a validation scenario by defining your end goal, as review workflow selection maps analysis, fix, audit, and validation paths to separate downstream skills based on the specific quality task requested.

When do I need intent classification for security review and UI review tasks?

You need intent classification for security review and UI review tasks when managing multi-purpose quality workflows, ensuring the request applies to the correct specialized evaluation path rather than a generic review flow.

How does routing a failing feature review to a debugging path work?

Routing a failing feature review to a debugging path works by matching the user's fix intent, invoking the debugging skill directly instead of a generic code review flow to address the specific failure scenario.

Can I use a single request for multiple quality workflows like code review and forensics?

You can use a single request for multiple quality workflows like code review and forensics, as the routing skill maps your goal to the correct specialized path for evaluation, audit, or forensics scenarios.

What are the limitations of using automated routing for quality and audit tasks?

The limitation of using automated routing for quality and audit tasks is that it requires accurate intent classification, meaning ambiguous requests may route to the wrong specialized skill if the review or validation goal is not clearly defined.