test-writer-fixer — Claude Code subagent: what it does, how to install
test-writer-fixer creates missing test suites, runs test runners after code changes, and updates failing checks. It keeps your test suite aligned with refactored logic.
no license ★ 2,003 updated 2026-07-26
/plugin marketplace add composio-community/awesome-claude-plugins
/plugin install test-writer-fixer@awesome-claude-pluginsWhat test-writer-fixer does
This subagent handles test workflows after feature additions or refactoring. It determines affected test files, targets the needed scope, and runs test runners like jest or pytest. Terminal output and stack traces are analyzed to locate the root cause of each failure.
Test repair follows strict rules. When application behavior intentionally changes, the subagent updates test assertions. For fragile assertions, it restructures the test using the Arrange-Act-Assert pattern. If an actual defect in the application code causes the failure, the agent reports the bug instead of modifying the source code.
Suites run in isolation before running the entire suite to filter out flaky behavior. The agent follows explicit execution targets: under 100ms for unit tests and under 1s for integration runs.
What it helps with
- generate unit and integration suites for untested modules
- detect breaking regressions after refactoring function signatures
- diagnose failure root causes from stack traces and runner output
- adjust obsolete assertions when code behavior changes intentionally
- refactor fragile test cases without lowering assertion strictness
Example prompts for the agent
- I updated the authentication module to OAuth, run test-writer-fixer to catch regressions
- Our payment processing module has no tests, create unit tests for edge cases and errors
- Several tests failed after async refactoring, analyze the errors and update the assertions
How to install test-writer-fixer
1Plugin marketplace
/plugin marketplace add composio-community/awesome-claude-plugins/plugin install test-writer-fixer@awesome-claude-plugins2Manually: put the files in place
.claude/agents/test-writer-fixer.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/test-writer-fixer.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/test-writer-fixer.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about test-writer-fixer
How to install test-writer-fixer in Claude Code?
Run /plugin marketplace add composio-community/awesome-claude-plugins, then run /plugin install test-writer-fixer@awesome-claude-plugins.
What does test-writer-fixer do?
It identifies modified modules, runs test runners such as jest or pytest, and repairs broken tests. It also generates new test coverage for uncovered files.
How does the agent handle bugs found in application code?
It separates outdated assertions from genuine software bugs. If the issue lies in the application code, the agent flags the problem without editing the implementation.