Write failing tests before implementation using red-green TDD workflows.
npx skills add https://github.com/linenoize/topia --skill test-linenoize
Please help me install this Agent Skill. Skill: test Source: https://github.com/linenoize/topia/tree/main/skills/test Command: npx skills add https://github.com/linenoize/topia --skill test-linenoize
This Skill enforces disciplined test-first development so code changes are validated by behavior, not by guesswork. It helps prevent fragile implementations, missed edge cases, and rushed changes that only appear correct.
Use the test skill to write one failing test for the current behavior, run it to confirm it fails, and then pass implementation work to the fix skill.
High-intent search queries and answers about installing and using this skill.
Red-green TDD workflow enforces writing a failing test first to validate expected behavior, confirming the failure, then verifying the implementation makes it pass. This prevents fragile code by targeting happy paths, edge cases, and error cases.
Behavior-focused test coverage validates code changes by targeting happy paths, edge cases, and error cases using the project's existing test framework. It maps requirements to test cases, preserving vertical slicing discipline and ensuring reliable verification through coverage checks.
This testing approach works with pytest, jest, and other frameworks by detecting the project's existing test conventions. It applies framework detection to write tests across unit, integration, end-to-end, or behavior tests without requiring additional dependencies.
Writing failing tests before implementation applies to unit, integration, end-to-end, and behavior tests. The process targets expected behavior using the project's existing conventions, enforcing red-green TDD and behavior-focused assertions for reliable verification.
Test-first development requires no additional dependencies, relying on framework detection to apply existing project conventions. It operates within the current test setup to enforce coverage checks, vertical slicing, and behavior-focused assertions for reliable verification.
The best way to validate expected behavior is disciplined test-first development, enforcing red-green TDD to prevent fragile implementations. By writing one failing test first and mapping requirements to test cases, code changes are validated by behavior, not guesswork.
RyoMurakami1983Standardize a Test-Driven Development workflow using test lists and the Red-Green-Refactor cycle.
minyeamerDiagnoses failing LinkMerce tests and guides minimal-fix reproduction-to-confirmation workflows.
robertolopezlopezImplement test-first development workflows through red-green-refactor iterations.
beekeeper-labGenerate traceability matrices mapping user stories and acceptance criteria to test cases.
