qa
Skill1 starsChanged 3 months agoNo licenceView on GitHub
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA".
In this repository28 other files it gives its agents.
- autoloopSkill
- claude-apiSkill
- compileSkill
- config-auditSkill
- deploySkill
- design-reviewSkill
- deslopSkill
- feature-flowSkill
- glow-upSkill
- hallmarkSkill
- investigateSkill
- learnSkill
- lintSkill
- office-hoursSkill
- ossSkill
- paperSkill
- plan-ceo-reviewSkill
- plan-design-reviewSkill
- plan-devex-reviewSkill
- plan-eng-reviewSkill
- prototypeSkill
- researchSkill
- session-handoffSkill
- session-kickoffSkill
- thinkSkill
- use-railwaySkill
- ux-auditSkill
- verifySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
150 rules. About 0 are common, 104 are distinctive, and 46 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈104
Distinctive · estimate
This author's own choices. Worth a look.
46
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
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.