Skip to content
TrustedSkillsbeta
Back to all skills

Test Fixing

Checked
mhattingpete·vlatest·testing·Apache-2.0

Automatically identifies and suggests fixes for common coding errors in Python scripts based on mhattingpete's testing methodology.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add mhattingpete/claude-skills-marketplace --skill test-fixing -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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
Manifest
engineering-workflow-plugin/skills/test-fixing/SKILL.md
Scanned
1 file, 108 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to automatically identify and resolve test failures within software projects. It streamlines the debugging process by analyzing failing tests and applying fixes directly to the codebase.

When to use it

  • You have a suite of automated tests that are currently failing and need immediate resolution.
  • You want to reduce manual time spent investigating why specific unit or integration tests are broken.
  • Your development workflow includes continuous integration pipelines where test failures halt deployment.
  • You need to maintain code quality by ensuring new changes do not introduce regressions in existing tests.

Key capabilities

  • Automatic detection of failing test cases.
  • Analysis of root causes behind test failures.
  • Implementation of code patches to restore passing test status.
  • Integration with standard testing frameworks and environments.

Example prompts

  • "Run the full test suite and fix any tests that are currently failing."
  • "Analyze why these specific unit tests are throwing errors and apply a patch."
  • "Identify regressions in the integration tests and correct the underlying code issues."

Tips & gotchas

Ensure your repository has a clear history of passing tests before attempting to use this skill, as it relies on comparing current failures against expected behavior. Limit the scope of fixes to avoid unintended changes to unrelated parts of the codebase.