# test-writer-fixer

test-writer-fixer — a Claude Code plugin that runs unit tests after code changes, writes missing ones, and fixes failing tests. Triggers automatically after refactoring, new features, or bug fixes.

- plugin · `type=plugin` · Claude Code · ★ 2003 repo stars
- Author: Community
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/composio-community/awesome-claude-plugins/tree/HEAD/test-writer-fixer
- Updated: 2026-07-26
- Security check: automated, 2026-11-16 (text and 1 script file) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/plugins/test-writer-fixer

## What it does

The plugin runs after code changes: module refactoring, bug fixes, or new features. It reads existing tests, finds failures, analyzes the root cause, and fixes them. If tests for the modified code are missing, it writes new ones, including edge cases and error handling.

It works through a sub-agent: Claude Code passes the task, the agent runs the test suite, compares results with expected outcomes, and patches test code or production code if there is a regression in logic. Works for modules without coverage: the plugin creates tests for critical sections like payment logic or data synchronization.

Without a test framework in the project, the plugin will not run. Supports standard runners: pytest, Jest, JUnit — the choice depends on the project language.

## Install

### Claude Code (native platform)

**Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add composio-community/awesome-claude-plugins
```
In the agent chat (not a shell):
```text
/plugin install test-writer-fixer@awesome-claude-plugins
```

## When to use it
- run tests after refactoring and fix failures
- write unit tests for a new module or function
- verify a bug fix did not break existing functionality
- add tests for a critical section without coverage
- automatically run tests after an API change

## Example prompts
- I fixed the OAuth authentication logic — run tests and fix what failed
- Refactored the payment module to async/await, check the tests
- The data sync module has no tests — write them

## Similar
- [test-coverage-improver](https://affpapa.org/en/nevibecode/skills/test-coverage-improver.md) — skill · 312 installs
- [test-gen](https://affpapa.org/en/nevibecode/skills/test-gen.md) — skill · ★ 937 repo stars
- [test-architect](https://affpapa.org/en/nevibecode/agents/test-architect.md) — subagent · ★ 1424 repo stars
- [test-coverage](https://affpapa.org/en/nevibecode/commands/test-coverage.md) — command · 637 installs
- [generate-tests](https://affpapa.org/en/nevibecode/commands/generate-tests.md) — command · 12378 installs
- [testing-best-practices](https://affpapa.org/en/nevibecode/skills/testing-best-practices.md) — skill · 975 installs

From the same set: [composio-community/awesome-claude-plugins](https://affpapa.org/en/nevibecode/by/composio-community/awesome-claude-plugins.md) — 68 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
