code-test

Enforce a test-first workflow requiring failing tests before implementation.

1|Updated Jan 12, 2026

Search Tags:#workflow #tdd #red-green-refactor #unit-testing #quality-gates #test-driven-development

Ready to run

npx skills add https://github.com/srnnkls/tropos --skill code-test-srnnkls

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-test
Source: https://github.com/srnnkls/tropos/tree/main/skills/code-test
Command: npx skills add https://github.com/srnnkls/tropos --skill code-test-srnnkls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write the test first. Watch it fail. Write minimal code to pass and verify the intent before adding features.

Core Features & Use Cases

Red-Green-Refactor cycle: write a failing test, observe failure, implement minimal code, run tests, then refactor.
Guardrails: enforce per-behavior testing to prevent regression and encourage incremental development.
Verification: maintain a strict test-first workflow to ensure correct behavior and documentation of changes.

Quick Start

Define a failing test for the new behavior, run the test suite to see it fail, then implement the minimal code required to make the test pass.

Frequently Asked Questions about code-test

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

FAQPage Schema

How do I enforce test-driven development workflow when implementing new features?▼

To enforce test-driven development, you must write a failing test for the new behavior first, run the test suite to observe the failure, and then implement minimal code to pass it.

What is the red-green-refactor cycle for unit testing?▼

The red-green-refactor cycle is a unit testing workflow where you write a failing test, implement minimal code to make it pass, and then refactor the codebase while maintaining test coverage.

How do I prevent regression when fixing bugs across a codebase?▼

To prevent regression when fixing bugs, write a failing unit test that reproduces the specific bug first, then implement minimal focused code changes to pass that test before refactoring.

Can I use this test-first workflow for behavior changes in existing projects?▼

Yes, this test-first workflow applies to behavior changes in existing projects by requiring you to define a failing test for the intended change before modifying production code.

Why does test-driven development require writing tests before production code?▼

Test-driven development requires writing tests before production code to verify the intended behavior and document changes immediately, ensuring incremental development and preventing regressions.