forge

Enforce a test-first workflow with Red-Green-Refactor discipline.

67|10|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/GadaaLabs/claude-code-on-steroids --skill forge-gadaalabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge
Source: https://github.com/GadaaLabs/claude-code-on-steroids/tree/main/skills/forge
Command: npx skills add https://github.com/GadaaLabs/claude-code-on-steroids --skill forge-gadaalabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

FORGE enforces a test-first workflow: you write a failing test before production code, verify it fails for the right reason, then implement the minimal code to pass and refactor with confidence.

Core Features & Use Cases

  • Write the failing test first and watch it fail.
  • Implement minimal production code to make the test pass.
  • Refactor safely while keeping all tests green.
  • Enforce Red-Green-Refactor discipline for new features, bug fixes, and refactors.

Quick Start

Write a small failing test for the desired behavior, run it to confirm the failure, implement the minimal code needed to pass, and then refactor while keeping tests green.

Frequently Asked Questions about forge

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

FAQPage Schema
What is test-first workflow in software engineering?

Test-first workflow requires writing a failing test before production code, confirming the failure, implementing minimal code to pass, and refactoring while keeping all tests green.

How do I apply red-green-refactor discipline to new features and bug fixes?

To apply red-green-refactor, write a minimal failing test for the desired behavior, run it to confirm failure, implement the simplest code to pass, and refactor while maintaining all tests.

Can I use test-driven development for refactoring existing code?

Yes, test-driven development applies to refactoring by guiding you to maintain all tests green while improving code structure, ensuring existing behavior remains intact throughout the process.

What's the best way to enforce TDD discipline across a software team?

Enforce TDD discipline by requiring developers to write a failing test first, confirm it fails for the right reason, implement minimal code to pass, and refactor while keeping tests green.

Why do I need to watch a test fail before writing production code?

You need to watch a test fail before writing production code to confirm it fails for the right reason, ensuring the test is valid and actually validates the desired behavior before implementation.