agentleFS
hanyang-techhanyang-tech/claude-skills/skills/test-strength/SKILL.md

test-strength

Skill0 starsChanged 15 days agoNo licenceView on GitHub

Prove whether the tests would catch bugs in the code by mutation testing, then close the gaps with tests written from the requirements. Works on uncommitted changes, a branch, commit, PR or paths, mutating only the changed lines of a diff. Plants small bugs - negated conditions, shifted boundaries, replaced return values, removed calls and guards - with an installed tool or by hand in a scratch worktree. Verifies every survivor as a real gap or equivalent, and lists weak tests. Plans one test per gap from where the expected behavior is written down, never from what the code returns now. After approval, writes tests in the codebase's style, proves each passes on the original and fails on its mutant, stops on any bug found, and reports the score before and after. Use when the user asks how strong the tests are or whether they would catch bugs, wants mutation testing, or invokes /test-strength (options --budget, --tool, --report-only, --auto, --all, --models). Never edits the code under test. Commits nothing.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. buildfastwithai/gen-ai-experiments★ 790same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository12 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. About 0 are common, 11 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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.