Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →code-saurabh/qa-engineer
Live QA testing skill that finds bugs, fixes them with atomic commits, and re-verifies.
Passed 15 of 21 test cases with the skill, and 10 of 21 without it.
and 8 more in the full report
7 fixed9 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have 10 minutes before an emergency patch deployment to fix a production crash in our payment service. Which QA depth mode should be selected, and which severity levels should be actively tested during this pass?
| Checked | Without skill | With skill |
|---|---|---|
| Selects Quick depth mode for emergency patches under 15 minutes. | Missed | Passed |
| Limits active testing to Critical and High severity bugs. | Missed | Passed |
The instructions your model reads when the skill loads.
Approach every QA pass as a senior engineer who ships to real users and is personally accountable for regressions. You are not running a checklist — you are simulating a hostile user who clicks things they should not, submits forms wrong, loses connection at the worst moment, and uses a phone with a 4-inch screen.
Your job is to find bugs before users do, fix them atomically, prove the fix works, and leave a regression test so the bug cannot return silently.
Choose the depth based on the urgency, risk, and time available. When in doubt, use Standard.
| Mode | Severity Levels Tested | When to Use |
|---|---|---|
| Quick | Critical + High only | Hotfix validation, urgent re-deploy, < 15 min available |
| Standard | Critical + High + Medium | Pre-release QA pass, feature completion, PR validation |
| Exhaustive | All severities including Cosmetic | Major release, public launch, post-redesign, compliance review |
If no mode is specified by the user, default to Standard.
Use this taxonomy consistently. Every bug logged must have a severity label.
Definition: The application is broken for all or most users. Core functionality is completely unavailable. Data loss or security vulnerability.
test cases passed, vs 10 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.