New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Test Fixing

by davila7 in davila7/claude-code-templates

Run tests and systematically fix all failing tests using smart error grouping.

MITAuto-check passedTesting & QA

Install Test Fixing

skills CLI
$ npx skills add davila7/claude-code-templates --skill test-fixing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davila7/claude-code-templates test-fixing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-tool/components/skills/development/test-fixing .claude/skills/test-fixing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
test-fixing
GitHub stars
32k
Used in
7 other repos
Token cost
~739 tokens
SKILL.md length
357 words
Files
1
Skills in repo
477
Repo updated
First seen
Licence
MIT

At a glance

Run tests and systematically fix all failing tests using smart error grouping.

  • Works in 5 steps: Initial Test Run → Smart Error Grouping → Systematic Fixing Process → …
  • User asks to fix failing tests
  • SKILL.md covers When to Use, Systematic Approach, Best Practices and Example Workflow
  • Calls make and git

What it does

Test Fixing is an agent skill from davila7/claude-code-templates. Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.

Its SKILL.md is about 740 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Failing and flaky tests and Test generation. The repository describes itself as: CLI tool for configuring and monitoring Claude Code. The licence is MIT.

When your agent uses it

  • User asks to fix failing tests
  • Mentions test failures
  • Runs test suite and failures occur
  • Requests to make tests pass

Example prompts

  • “/test-fixing”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Initial Test Run
  2. Smart Error Grouping
  3. Systematic Fixing Process
  4. Fix Order Strategy
  5. Final Verification

What it can do on your machine

Read from SKILL.md and the folder at commit 4c82aba. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • make
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Test Fixing loads about 739 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 357 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~739

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from davila7/claude-code-templates at commit 4c82aba, republished under its MIT licence (© davila7). 357 words, ~739 tokens.

Download SKILL.mdSave it as .claude/skills/test-fixing/SKILL.md (or your agent's skills folder).
name
test-fixing
description
Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.

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 failure
  • 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
    • Ensure group passes before moving on

  4. Move to next group

Show full SKILL.md (151 more words)Show less
4. Fix Order Strategy

Infrastructure first:

  • Import errors
  • Missing dependencies
  • Configuration issues

Then API changes:

  • Function signature changes
  • Module reorganization
  • Renamed variables/functions

Finally, logic issues:

  • Assertion failures
  • Business logic bugs
  • Edge case handling
5. Final Verification

After all groups fixed:

  • Run complete test suite: make test
  • Verify no regressions
  • Check test coverage remains intact

Best Practices

  • Fix one group at a time
  • Run focused tests after each fix
  • Use git diff to understand recent changes
  • Look for patterns in failures
  • Don't move to next group until current passes
  • Keep changes minimal and focused

Example Workflow

User: "The tests are failing after my refactor"

  1. Run make test → 15 failures identified
  2. Group errors:
    • 8 ImportErrors (module renamed)
    • 5 AttributeErrors (function signature changed)
    • 2 AssertionErrors (logic bugs)
  3. Fix ImportErrors first → Run subset → Verify
  4. Fix AttributeErrors → Run subset → Verify
  5. Fix AssertionErrors → Run subset → Verify
  6. Run full suite → All pass ✓

© davila7, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in cli-tool/components/skills/development/test-fixing of davila7/claude-code-templates.

Open the folder on GitHubat commit 4c82aba

Used in 7 other repositories

We found 22 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 7 other GitHub owners. This page covers the copy in davila7/claude-code-templates, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Test Fixing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Test Fixing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Test Fixing this skilldavila7/claude-code-templates32k7 repos~739Automated safety check: PassMIT
Swig Testswig/swig6.3k—~2.3kAutomated safety check: PassCustom licence
Wioworkersio/skills180—~5.8kAutomated safety check: PassMIT
Offloadimbue-ai/offload125—~3.1kAutomated safety check: PassMIT
Write Testsdzhng/skills1k—~2.4kAutomated safety check: PassMIT
Frappe Testing UnitImpertio-Studio/Frappe_Claude_Skill_Package187—~3kAutomated safety check: PassMIT

Similar skills

  • Swig Test

    swig/swig

    Run SWIG test suite for specific languages. An agent skill from swig/swig.

    6.3k GitHub stars~2.3k tokensUpdated today
    Testing & QAAuto-check passed

  • Wio

    workersio/skills

    Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health.

    180 GitHub stars~5.8k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed

  • Offload

    imbue-ai/offload

    Activate when you see offload.toml in a repo, offload referenced in build targets (justfile, Makefile, scripts), or when you need to run a large test suite in parallel.

    125 GitHub stars~3.1k tokensUpdated 11 days ago
    Testing & QAAuto-check passed

  • Write Tests

    dzhng/skills

    Write tests that pin real behavior instead of implementation details, config values, or lucky samples.

    1k GitHub stars~2.4k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Frappe Testing Unit

    Impertio-Studio/Frappe_Claude_Skill_Package

    A skill your agent uses when writing unit tests, integration tests, creating test fixtures, or running tests with bench run-tests.

    187 GitHub stars~3k tokensUpdated 20 days ago
    Testing & QAAuto-check passed

  • Test Deep

    sd0xdev/sd0x-harness

    Context-aware test orchestration. An agent skill from sd0xdev/sd0x-harness.

    192 GitHub stars~2.3k tokensUpdated yesterday
    Testing & QAAuto-check: notes

More from davila7/claude-code-templates

All 477 skills in this repo

  • Perplexity Web Search

    davila7/claude-code-templates

    Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.

    32k GitHub starsUsed in 12 repos~3.5k tokens
    Auto-check: notes

  • Neuropixels Data Analysis

    davila7/claude-code-templates

    Analyzes Neuropixels recordings from SpikeGLX or Open Ephys through preprocessing, drift correction, Kilosort4 spike sorting, quality metrics and curation.

    32k GitHub starsUsed in 10 repos~2.8k tokens
    Auto-check passed

  • Scientific Venue Templates

    davila7/claude-code-templates

    Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.

    32k GitHub starsUsed in 9 repos~5.1k tokens
    Auto-check: notes

  • Brand Voice Content Creator

    davila7/claude-code-templates

    Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.

    32k GitHub starsUsed in 2 repos~1.9k tokens
    Auto-check passed

  • CAPA Officer

    davila7/claude-code-templates

    Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.

    32k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Fda Consultant Specialist

    davila7/claude-code-templates

    Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.

    32k GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed

Categories

Questions about Test Fixing

What does Test Fixing do?

Run tests and systematically fix all failing tests using smart error grouping. Test Fixing is an agent skill from davila7/claude-code-templates. Run tests and systematically fix all failing tests using smart error grouping.

When should I use Test Fixing?

Test Fixing fits situations like: user asks to fix failing tests; mentions test failures; runs test suite and failures occur; requests to make tests pass.

How do I install Test Fixing in Claude Code?

Run `npx skills add davila7/claude-code-templates --skill test-fixing -a claude-code`. Or copy the skill folder (cli-tool/components/skills/development/test-fixing in davila7/claude-code-templates) into .claude/skills/test-fixing in your project. Claude Code loads it when a task matches its description.

How do I install Test Fixing in Codex?

Run `npx skills add davila7/claude-code-templates --skill test-fixing -a codex`. Or copy the skill folder (cli-tool/components/skills/development/test-fixing in davila7/claude-code-templates) into .agents/skills/test-fixing in your project. Codex loads it when a task matches its description.

Can I use Test Fixing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davila7/claude-code-templates --skill test-fixing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-fixing, .gemini/skills/test-fixing, .github/skills/test-fixing and .opencode/skills/test-fixing in your project.

What does Test Fixing need to run?

Going by SKILL.md and its folder, Test Fixing needs the command-line tools its instructions call (make and git).

Does Test Fixing access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Test Fixing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Test Fixing use?

Test Fixing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Fixing use?

About 739 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Test Fixing?

Skills that share tags, products or a category with Test Fixing: Swig Test (swig/swig, 6.3k stars), Wio (workersio/skills, 180 stars), Offload (imbue-ai/offload, 125 stars) and Write Tests (dzhng/skills, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Fixing?

davila7 (a GitHub user) maintains it in davila7/claude-code-templates, which has 32,432 GitHub stars. The repository holds 477 skills in this directory. The repository was last updated on October 7, 2026.

Source: davila7/claude-code-templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.