Fix Tests
Skill Verified ActiveSystematically fix all failing tests after business logic changes or refactoring
To ensure code stability and maintainability by systematically resolving all failing tests after changes.
Features
- Automated test failure identification
- Orchestrated agent-based test fixing
- Preserves test intent and business logic
- Iterative fixing process for remaining failures
- Supports user-specified focus on specific tests or modules
Use Cases
- Automatically fix broken tests after a refactoring session.
- Ensure all regression tests pass after a dependency update.
- Systematically resolve test failures following a major code change.
Non-Goals
- Writing new business logic or features.
- Refactoring code that is not directly related to test failures.
- Adding new tests where none existed previously.
Workflow
- Read available 'sadd' skill if present.
- Discover test infrastructure (test commands, project structure).
- Run all tests to establish a baseline.
- Identify all failing test files.
- Verify single test execution can be reliably run.
- Launch 'developer' agents in parallel for each failing test file.
- Provide agents with context, target file, guidance, resources, command, and goal to fix tests.
- Verify all fixes by running the full test suite again.
- Iterate by launching new agents for remaining failures until 100% pass rate.
Practices
- Test-Driven Development
- Code Quality
- Automation
Prerequisites
- A project with a test suite discoverable by standard commands (e.g., via package.json or README.md)
- Agents capable of understanding and executing code changes (e.g., provided by the Claude Code environment)
Installation
First, add the marketplace
/plugin marketplace add NeoLabHQ/context-engineering-kit/plugin install tdd@context-engineering-kitQuality Score
VerifiedTrust Signals
Similar Extensions
Use My Browser
100Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.
Telegram Crabbox E2e Proof
100Use when reviewing, reproducing, or proving OpenClaw Telegram behavior with a real Telegram user on Crabbox, including PR review workflows that need an agent-controlled Telegram Desktop recording, TDLib user-driver commands, Convex-leased credentials, WebVNC observation, and motion-trimmed artifacts.
Openclaw Testing
100Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
Agent Browser
100Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
Moyu (摸鱼)
100과잉 엔지니어링 패턴이 감지되면 자동으로 활성화됩니다: (1) 사용자가 명시적으로 변경을 요청하지 않은 코드나 파일을 수정하는 경우 (2) 요청되지 않은 새로운 추상화 레이어(class, interface, factory, wrapper)를 생성하는 경우 (3) 요청되지 않은 주석, 문서, JSDoc, 타입 어노테이션을 추가하는 경우 (4) 요청되지 않은 새로운 의존성을 도입하는 경우 (5) 최소한의 편집 대신 파일 전체를 다시 작성하는 경우 (6) diff 범위가 사용자의 요청을 명백히 초과하는 경우 (7) 사용자가 "너무 많아", "거기는 건드리지 마", "X만 변경해", "간단하게", "그만" 등의 신호를 보내는 경우 (8) 발생할 수 없는 시나리오에 대한 에러 처리, 유효성 검사, 방어적 코드를 추가하는 경우 (9) 요청되지 않은 테스트, 설정 스캐폴딩, 문서를 생성하는 경우
Cleanup Cycles
100Detect and untangle circular dependencies. Runs madge/skott (TS), pycycle (Py), or compiler-only checks (Go/Rust). Auto-fixes leaf-extractable cycles; reports core cycles for human review. Use when the user asks to find circular imports, fix dependency cycles, or untangle module graph. Example queries — "find circular imports", "fix dependency cycles", "untangle our module graph", "why is madge complaining".