Test Fixing

Detect failing tests and propose targeted fixes.

Testing & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add mhattingpete/claude-skills-marketplace --skill test-fixing
Manual install
git clone --depth 1 https://github.com/mhattingpete/claude-skills-marketplace.git /tmp/claude-skills-marketplace
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-marketplace/engineering-workflow-plugin/skills/test-fixing ~/.claude/skills/test-fixing

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

What this skill does

Detects failing tests and proposes fixes. Automatically identify test failures and suggest solutions.

Trigger phrases

Claude loads this skill automatically when you say things like:

“fix tests”“failing tests”“test errors”“repair tests”

How it works

  1. Run test suite
  2. Analyze failures
  3. Propose fixes

When to use it

  • When tests are failing
  • For test maintenance
  • When debugging test issues

From the SKILL.md

# Test Fixing

Systematically identify and fix all failing tests using smart grouping strategies.

## When to Use

- Explicitly asks to fix tests ("fix these tests", "make tests pass")
- Reports test failures ("tests are failing", "test suite is broken")
- Completes implementation and wants tests passing
- Mentions CI/CD failures due to tests

## Systematic Approach

### 1. Initial Test Run

Run `make test` to identify all failing tests.

Analyze output for:
- Total number of failures
- Error types and patterns
- Affected modules/files

### 2. Smart Error Grouping

Group similar failures by:
- **Error type**: ImportError, AttributeError, AssertionError, etc.
- **Module/file**: Same file causing multiple test failures
- **Root cause**: Missing dependencies, API changes, refactoring impacts

Prioritize groups by:
- Number of affected tests (highest impact first)
- Dependency order (fix infrastructure before functionality)

### 3. Systematic Fixing Process

For each group (starting with highest impact):

1. **Identify root cause**
   - Read relevant code
   - Check recent changes with `git diff`
   - Understand the error pattern

2. **Implement fix**
   - Use Edit tool for code changes
   - Follow project conventions (see CLAUDE.md)
   - Make minimal, focused changes

3. **Verify fix**
   - Run subset of tests for this group
   - Use pytest markers or file patterns:
     ```bash
     uv run pytest tests/path/to/test_file.py -v
     uv run pytest -k "pattern" -v
     ```
Read the full skill on GitHub

Details

Skill name
test-fixing
Repository
mhattingpete/claude-skills-marketplace
Path
engineering-workflow-plugin/skills/test-fixing/SKILL.md
Listed in
BehiSecc/awesome-claude-skills, ComposioHQ/awesome-claude-skills, heilcheng/awesome-agent-skills

FAQ

What does the Test Fixing skill do?

Detects failing tests and proposes fixes. Automatically identify test failures and suggest solutions.

How do I install the Test Fixing skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add mhattingpete/claude-skills-marketplace --skill test-fixing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Related skills

Git Pushing

mhattingpete/claude-skills-marketplace

Automates git operations and repository interactions. Streamline your git workflow with automated commands.

Git & Code ReviewIn 3 lists

Review Implementing

mhattingpete/claude-skills-marketplace

Evaluates code implementation plans before execution. Review and validate implementation approaches.

Software DevelopmentIn 3 lists

Playwright

openai/skills

Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.

Testing & QAIn 2 lists

Playwright Skill

testdino-hq/playwright-skill

Current Playwright (1.64) patterns for writing, debugging, and scaling reliable test suites. Use for any Playwright task, even ones you think you know, because the guides cover APIs and CLI flags newer than most training data. Covers writing or fixing tests, locators, a failing or flaky test, a trace.zip or error message, playwright.config and projects, network mocking, auth, visual and accessibility testing, Docker and CI sharding, playwright-cli browser automation, Playwright Test Agents, page objects, migrating from Cypress or Selenium, and QA work: test case design, bug reports from failur

Testing & QAIn 2 lists

Coverage Guard

sametcelikbicak/coverage-guard

Use when the user wants to check test coverage, enforce 100% coverage, find uncovered code, add missing tests, or increase code coverage. Works with vitest, jest, react-scripts, and other test runners. Also for 'coverage', 'test coverage', 'cover', 'untested', 'uncovered', 'add tests for', 'increase coverage', 'coverage report', 'write tests', 'test all files'.

Testing & QAIn 1 list

Persona

takechanman1228/claude-persona

Build a persona panel, explore customer motivations through open-ended questions, and pressure-test product concepts before spending on fieldwork. Generates diverse AI persona panels, runs agent-separated interviews (qualitative ask or structured concept test), analyzes results with theme synthesis, cross-tabs, and charts, and delivers executive research reports. Use when the user wants to ask a panel about motivations or barriers, which concept to launch, who to target first, which message resonates, whether a value proposition works, or needs a reusable persona panel.

Testing & QAIn 2 lists

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.