tdd-fix-tests

Fix failing tests after business logic changes or refactoring.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Gamezar/opencode-cek --skill tdd-fix-tests-gamezar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-fix-tests
Source: https://github.com/Gamezar/opencode-cek/tree/main/plugins/tdd/skills/tdd-fix-tests
Command: npx skills add https://github.com/Gamezar/opencode-cek --skill tdd-fix-tests-gamezar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the common issue of failing tests after code changes, ensuring the test suite remains a reliable indicator of code health.

Core Features & Use Cases

  • Automated Test Fixing: Orchestrates agents to systematically fix all tests that fail due to business logic changes or refactoring.
  • Test Infrastructure Discovery: Identifies how to run tests and coverage reports within a project.
  • Use Case: After refactoring a complex module, your test suite breaks. This Skill can automatically identify and fix the failing tests, allowing you to quickly verify the refactoring's correctness.

Quick Start

Use the tdd-fix-tests skill to fix all failing tests in the current project.

Frequently Asked Questions about tdd-fix-tests

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

FAQPage Schema
How do I fix failing tests automatically after refactoring business logic?

Automated test fixing orchestrates specialized agents to systematically identify, analyze, and correct failing tests while preserving test intent and business logic integrity after code changes.

What is the process for discovering test infrastructure before running automated test fixes?

Test infrastructure discovery identifies how to execute test suites and coverage reports within a project, requiring project test infrastructure knowledge to orchestrate subsequent test correction agents.

Can I use automated test fixing to repair a broken test suite after modifying a complex module?

Automated test fixing targets broken test suites after complex module refactoring, identifying failing tests and correcting them to verify the refactoring's correctness while maintaining code health.

Does automated test fixing require understanding project test execution commands?

Automated test fixing requires understanding of project test infrastructure and execution commands to properly orchestrate agents that identify, analyze, and correct test failures across the software project.

What is the best way to preserve test intent when correcting failing tests?

Systematic test fixing preserves test intent by orchestrating specialized agents to analyze failures and apply corrections that maintain business logic integrity rather than simply overwriting assertions.

Why does automated test fixing focus on failures caused by business logic changes?

Automated test fixing addresses failures from business logic changes or refactoring because these scenarios require adjusting test expectations while preserving the original test intent and ensuring code health.