qa-diff
Skill0 starsChanged 28 days agoMITView on GitHub
Diff-aware QA for the current changes, a branch, a commit range or a PR — maps blast radius, finds likely bugs and regressions, audits whether tests cover (or were weakened by) the change, and outputs a targeted test checklist. Use before opening or merging a PR.
In this repository10 other files it gives its agents.
- qa-auditSkill
- qa-automateSkill
- qa-bugSkill
- qa-casesSkill
- qa-exploreSkill
- qa-flakySkill
- qa-initSkill
- qa-planSkill
- qa-releaseSkill
- qaSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
When it returns, present: the risk level, the likely bugs (with file:line), the test gaps, and the targeted checklist.
≈ “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.
Files
Delegate to the qa-change-analyst subagent (it may appear as argus-qa:qa-change-analyst).
Target: $ARGUMENTS. If this is empty, use the current branch vs its merge base plus uncommitted changes. If it's a number, treat it as a PR (gh pr diff).
When it returns, present: the risk level, the likely bugs (with file:line), the test gaps, and the targeted checklist. Then offer two follow-ups:
/qa-automateto write tests for the top gaps (the automation engineer will prove they fail without the fix)/qa-exploreon the affected screens, if the app can run locally
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.