agentleFS
Sign inStart free
grooownowgrooownow/qa-pilot/skills/test/SKILL.md

test

Skill6 starsChanged 15 days agoLicence not identifiedView on GitHub

The everyday qa-pilot command for a task: `/qa-pilot:test [ticket | feature | \"in the browser\" | plan | nothing]`. It reads the context and does the right QA work. Before coding it makes a QA plan: AC check, impact map, test delta. After coding it verifies the change: diff vs plan, \"intended?\" questions, proof of coverage, missing tests under guards. With \"browser\" or a URL it runs exploratory testing in a real browser. With a test plan it writes the tests. With no context it inspects the branch, and asks once when the signals conflict. Use for \"протестируй\", \"проверь задачу\", \"покрой тестами\", \"что затронет это изменение\", \"покликай в браузере\", \"test this\", \"cover this\". Requires docs/qa/project-profile.md (else it runs qa-pilot:onboard first). Not for the whole project or a whole feature's requirements (use qa-pilot:audit), not for first setup (use qa-pilot:onboard).

179 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

The licence could not be identified — 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 154 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.

Check your setup, free