tdd:fix-tests

User can provide to focus on specific tests or modules:

neolabhq/context-engineering-kit|Updated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGoose

Installation Guide

Select your AI agent

How to use tdd:fix-tests on Cursor

AI-first code editor with Composer

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

›Cursor installed and configured on your machine
›Node.js 16+ with npm — verify with node --version
›Active project directory where you want to add tdd:fix-tests

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/neolabhq/context-engineering-kit --skill tdd:fix-tests

Fetches tdd:fix-tests from neolabhq/context-engineering-kit and configures it for Cursor.

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?

│

│ ── Universal (.agents/skills) ────────────────

│ · Cline · Codex · Goose · Windsurf

│ ●Cursor(selected)

│ · Cursor · Aider · Continue

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/tdd:fix-tests

Restart Cursor to activate tdd:fix-tests. Access via /tdd:fix-tests in your agent's command palette.

⚠

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

›View source on GitHub ›Skills CLI docs ›About Cursor ›What are agent skills?

Documentation

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

✓

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

✓

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

✓

Improve work quality by 30-40% with less effort

Important Constraints

Focus on fixing tests - avoid changing business logic unless absolutely necessary

Preserve test intent - ensure tests still validate the expected behavior

"Analyse complexity of changes" -

if there 2 or more changed files, or one file with complex logic, then Do not write tests yourself - only orchestrate agents!
if there is only one changed file, and it's a simple change, then you can write tests yourself.

Workflow Steps

Preparation

Read sadd skill if available

If available, read the sadd skill to understand best practices for managing agents

Discover test infrastructure

Read @README.md and package.json (or equivalent project config)
Identify commands to run tests and coverage reports
Understand project structure and testing conventions

Run all tests

Execute full test suite to establish baseline

Identify all failing test files

Parse test output to get list of failing test files
Group by file for parallel agent execution

Analysis

Verify single test execution

Choose any test file
Launch haiku agent with instructions to find proper command to run this only test file
- Ask him to iterate until you can reliably run individual tests
After he complete try running a specific test file if it exists
This ensures agents can run tests in isolation

Test Fixing

Launch developer agents (parallel)

Launch one agent per failing test file
Provide each agent with clear instructions:
- Context: Why this test needs fixing (business logic changed)
- Target: Which specific file to fix
- Guidance: Read TDD skill (if available) for best practices how to write tests.
- Resources: Read README and relevant documentation
- Command: How to run this specific test file
- Goal: Iterate until test passes
- Constraint: Fix test, not business logic (unless clearly broken)

Verify all fixes

After all agents complete, run full test suite again
Verify all tests pass

Iterate if needed

If any tests still fail: Return to step 5
Launch new agents only for remaining failures
Continue until 100% pass rate

Agent Instructions Template

When launching agents, use this template:

The business logic has changed and test file {FILE_PATH} is now failing. Your task: 1. Read the test file and understand what it's testing 2. Read TDD skill (if available) for best practices on writing tests. 3. Read @README.md for project context 4. Run the test: {TEST_COMMAND} 5. Analyze the failure - is it: - Test expectations outdated? → Fix test assertions - Test setup broken? → Fix test setup/mocks - Business logic bug? → Fix logic (rare case) 6. Fix the test and verify it passes 7. Iterate until test passes

tdd:fix-tests

Installation Guide

How to use tdd:fix-tests on Cursor

Prerequisites

Run the install command

Select Cursor when prompted

Verify installation

Security Notice

Documentation

List & Monetize Your Skill

Use Cases

Task Automation & Efficiency

Knowledge Enhancement

Quality Improvement

Install Skill

Fix Tests

User Arguments

Context

Goal

Important Constraints

Workflow Steps

Preparation

Analysis

Test Fixing

Success Criteria

Agent Instructions Template

Implementation Guide

Best Practices

When to Use This

Learning Path

Related Skills

ddd:software-architecture

polyglot-test-agent

accessibility-testing

usability-testing

vitest

idor-vulnerability-testing

Reviews

Discussion