agentleFS
BryanBerger98BryanBerger98/claude-skills/deep-test/SKILL.md

deep-test

Skill1 starsChanged 4 months agoNo licenceView on GitHub

Deep-tests a set of features end to end — rebuilds the code graph, maps the UI/API surface, derives a testable behavior spec, dispatches parallel opus QA agents (browser e2e + HTTP) that score coherence, reliability, stability, errors and bugs, consolidates a ranked report, traces each problem to its code root cause, then runs an interactive approve-fix-retest loop. Use when the user wants a thorough autonomous QA sweep of one or more features across web UI and API — e.g. "deep-test the checkout flow", "full QA pass on auth with root-cause analysis and fixes". Do NOT use for a single known bug (use `diagnose`), reviewing a diff (use `code-review`), quick error fixes (use `fix-errors`), or just launching the app to eyeball a change (use `verify` or `run`).

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    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 measured: kept by at least 6 in 10 of the 3 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.

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.