test-fixing
CheckedRun 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
Install on your platform
Showing OpenClaw.
- 1
Run this in your terminal
terminal$
What we know about this skill
Publisher
mhattingpete
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned mhattingpete/claude-skills-marketplace at b5b34bcf4c.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- b5b34bcf4c
- Scanned
- 1 file, 108 lines
About this skill
What it does
This skill automatically addresses failing unit tests by intelligently grouping errors and suggesting fixes. It identifies patterns in test failures, allowing for efficient resolution of multiple issues at once. The skill is designed to streamline the debugging process when a test suite fails, reducing manual effort required to identify and correct problems.
When to use it
- When you run a test suite and encounter failing tests.
- If a user explicitly requests assistance in fixing failing tests.
- After making code changes that introduce new test failures.
- To quickly resolve a series of related errors identified during testing.
Key capabilities
- Error grouping based on patterns.
- Automated suggestion of fixes for failing tests.
- Systematic approach to resolving multiple test failures simultaneously.
- Handles requests to fix failing tests.
Example prompts
- "The tests are failing, can you help me fix them?"
- "I ran the test suite and got a bunch of errors; what's wrong?"
- "Fix these failing unit tests."
Tips & gotchas
This skill assumes that the codebase has a well-defined test suite. It is most effective when failures are due to logical or implementation errors, rather than environmental issues (e.g., database connection problems).