qa-bug
Skill0 starsChanged 28 days agoMITView on GitHub
Turn an observation, error message, log, screenshot or customer complaint into a reproducible, developer-ready bug report (minimal steps, severity/priority, evidence, duplicate check). Optionally files it to GitHub after approval.
In this repository10 other files it gives its agents.
- qa-auditSkill
- qa-automateSkill
- qa-casesSkill
- qa-diffSkill
- qa-exploreSkill
- qa-flakySkill
- qa-initSkill
- qa-planSkill
- qa-releaseSkill
- qaSkill
The file
Files
Delegate to the qa-bug-reporter subagent (it may appear as argus-qa:qa-bug-reporter).
Input: $ARGUMENTS. Include any image or log the user attached in this conversation, described or quoted in the brief, since the subagent can't see this chat.
Show the user the finished report. If --file was given or the user asks to file it, show the exact title and body, wait for explicit approval, and then run gh issue create --title … --body-file … (add the bug label if it exists).
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.