agentleFS
Sign inStart free
emaraschioemaraschio/cursor-commands/.cursor/skill-contracts/run-all-tests-and-fix/SKILL.md

run-all-tests-and-fix

Skill9 starsChanged 3 months agoMITView on GitHub

Run full test suite and fix failures

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Check both unit and integration tests

    line 16
  2. Distinctive:

    Check if failures are related to recent changes

    line 20
  3. Distinctive:

    Start with the most critical failures

    line 22
  4. Distinctive:

    Never silently skip a failing test.

    line 37
  5. Distinctive:

    Do not commit, push, merge, or run destructive commands without explicit user consent.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Overview

Execute the full test suite and systematically fix any failures, ensuring code quality and functionality.

Steps

  1. Run test suite
    • Execute all tests in the project that are relevant to the current changes you are making
    • Capture output and identify failures
    • Check both unit and integration tests
  2. Analyze failures
    • Categorize by type: flaky, broken, new failures
    • Prioritize fixes based on impact
    • Check if failures are related to recent changes
  3. Fix issues systematically
    • Start with the most critical failures
    • Fix one issue at a time
    • Re-run tests after each fix

Test Recovery Checklist

  • Full test suite executed
  • Failures categorized and tracked
  • Root causes resolved
  • Tests re-run with passing results
  • Follow-up improvements noted

Guardrails

  • Fix the root cause of a failure; never delete or weaken a test to go green.
  • Never silently skip a failing test; report it and the reason.
  • Do not commit, push, merge, or run destructive commands without explicit user consent.

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