Test writing and fixing methodology. Covers TDD, investigating failures, and delegating fixes to agents. Use when writing tests or diagnosing test failures.
Investigates test failures to determine root cause, applies TDD methodology, and delegates fixes to agents.
npx claudepluginhub captaincrouton89/crouton-kitThis skill inherits all available tools. When active, it can use any tool Claude has access to.
A failing test signals one of two things:
Don't assume. Read the failure, trace the code path, determine which is true before changing anything.
Common signs the test is wrong:
Common signs the code is broken:
When adding new functionality, write tests first:
Benefits:
Skip TDD when: fixing obvious bugs, exploratory prototyping, or when the test setup cost exceeds the implementation.
When using agents to fix test failures:
Why agents don't run tests:
In agent instructions, include:
Fix the failing test. Do NOT run the test suite—make your change and exit.
If an agent encounters ambiguity about whether to fix the test or the code, it should stop and report a blocker.
If no, keep investigating.
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.