agentleFS
Sign inStart free
TheArchitectitTheArchitectit/awesome-cline-skills/skills/test-fixing/SKILL.md

test-fixing

Skill8 starsChanged 3 months agoApache-2.0View on GitHub

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.

We split this skill into the rules it gives an agent

17 rules. 13 are common, 0 are distinctive, and 4 are very specific to this project.

  • 13

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run make test to identify all failing tests.

    line 21
  2. Common:

    Check recent changes with git diff

    line 48
  3. Common:

    Use Edit tool for code changes

    line 52
  4. Very specific:

    Follow project conventions (see .clinerules/ or AGENTS.md)

    line 53
  5. Common:

    Run subset of tests for this group

    line 57
  6. Common:

    Use pytest markers or file patterns:

    line 58
  7. Common:

    Ensure group passes before moving on

    line 65
  8. Common:

    After all groups fixed:

    line 91
  9. Very specific:

    Run complete test suite: make test

    line 93
  10. Common:

    Check test coverage remains intact

    line 95
  11. Common:

    Run focused tests after each fix

    line 100
  12. Common:

    Use git diff to understand recent changes

    line 101
  13. Common:

    Look for patterns in failures

    line 102
  14. Common:

    Don't move to next group until current passes

    line 103
  15. Common:

    Keep changes minimal and focused

    line 104
  16. Very specific:

    Run make test → 15 failures identified

    line 110
  17. Common:

    Run full suite → All pass ✓

    line 118

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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 .clinerules/ or AGENTS.md)
    • Make minimal, focused changes
  3. Verify fix
    • Run subset of tests for this group

    • Use pytest markers or file patterns:

      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

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 ✓

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free