ferrox-add-tests

Generate unit and end-to-end tests from phase documentation with gap reporting.

21|9|Updated Jul 21, 2026

Search Tags:#unit tests #testing #tdd #software engineering #e2e tests #verification

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the burden of designing coverage after a phase is already built, helping you turn completed implementation work into reliable unit and end-to-end tests that reflect the phase's documented promises.

Core Features & Use Cases

Specification-Driven Testing: Uses SUMMARY.md, CONTEXT.md, and VERIFICATION.md as the source of truth for expected behavior.
Test Classification: Separates implementation files into unit, browser E2E, or skip categories before writing any tests.
Gate-Preserved Workflow: Enforces approval checkpoints, RED-GREEN verification, and gap reporting so test creation stays deterministic and auditable.
Use Case: A finished feature phase can be reviewed and converted into committed test files without manually reconstructing the intended behavior from scratch.

Quick Start

Use the ferrox-add-tests skill to generate unit and E2E tests for phase 3 based on its phase documentation.

Frequently Asked Questions about ferrox-add-tests

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

FAQPage Schema

How do I generate unit and e2e tests for completed software phases?▼

To generate unit and end-to-end tests for completed software phases, provide phase summaries, context files, and verification documents. The skill uses these specifications to classify implementation files and deterministically produce committed test coverage with gap reporting.

Can I use specification documents to drive test creation for a finished feature?▼

You can use specification documents like SUMMARY.md, CONTEXT.md, and VERIFICATION.md to drive test creation. These files act as the source of truth for expected behavior, allowing the skill to convert finished feature phases into verified test files without reconstructing behavior manually.

How does test classification handle unit tests versus browser e2e tests?▼

Test classification separates implementation files into unit, browser e2e, or skip categories before writing any tests. This ensures deterministic RED-GREEN test generation by applying the correct testing methodology to each file based on its role in the phase.

Do I need approval gates to verify test generation in a phase-based build workflow?▼

You need approval gates to verify test generation in a phase-based build workflow. The skill enforces approval checkpoints and RED-GREEN verification to ensure test creation stays deterministic and auditable throughout the software engineering process.

What is the best way to automate test coverage for documented implementation phases?▼

The best way to automate test coverage for documented implementation phases is to use a specification-driven approach. By extracting expected behavior from documentation, the skill removes the burden of designing coverage after a phase is built and provides gap reporting for missing tests.

Why does test generation require phase summaries and verification documents?▼

Test generation requires phase summaries and verification documents because they serve as the documented specifications for expected behavior. Without these inputs, the skill cannot accurately classify implementation files or produce deterministic test coverage that reflects the phase's documented promises.