QA Test and Fix
When the user wants to find and fix bugs, or says 'QA this,' 'test this,' 'find bugs,' 'why is this broken,' 'it doesn't work,' 'check for bugs,' 'smoke test,' or after any significant code change. This is the full QA cycle: discover → reproduce → diagnose → fix → verify.
Install
npx skills add 0xranx/agentbrief --skill qa-test-and-fixgit clone --depth 1 https://github.com/0xranx/agentbrief.git /tmp/agentbrief
mkdir -p ~/.claude/skills
cp -r /tmp/agentbrief/briefs/qa-engineer/skills/qa-test-and-fix ~/.claude/skills/qa-test-and-fixPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# QA: Test & Fix You are running a full QA cycle. Your goal is to find bugs, fix them, and prove the fixes work — all with atomic commits. ## Intensity Tiers Choose based on the scope of changes: ### Tier 1: Smoke Test (quick) For small changes, single files, or quick checks. 1. Run existing test suite 2. Manually trace the changed code paths 3. Check the 3 most likely edge cases 4. Report findings ### Tier 2: Standard QA (default) For features, refactors, or anything touching user-facing code. 1. Run existing test suite 2. Read all changed files, understand the intent 3. Test happy path end-to-end 4. Test each edge case category (input, state, error, concurrency) 5. Write tests for any untested code paths 6. Fix found bugs with atomic commits 7. Re-run full test suite to verify no regressions ### Tier 3: Deep QA (thorough) For releases, security-sensitive changes, or critical features. 1. Everything in Tier 2 2. Fuzz inputs with boundary values 3. Test error recovery (kill process mid-operation, corrupt data) 4. Test concurrent access patterns 5. Review all error handling paths 6. Performance check (is anything unexpectedly slow?) 7. Security check (input validation, auth, data leaks) ## QA Process ### Step 1: Baseline ```bash # Run existing tests to establish baseline pnpm test # or npm test, pytest, go test, etc. ``` Record: X tests passing, Y tests failing, Z tests skipped. ### Step 2: Discover Read the code changes and identify risk areas:
Details
- Skill name
qa-test-and-fix- Repository
- 0xranx/agentbrief
- Path
briefs/qa-engineer/skills/qa-test-and-fix/SKILL.md- License
- MIT
- Repo updated
- 28 March 2026
FAQ
What does the QA Test and Fix skill do?
When the user wants to find and fix bugs, or says 'QA this,' 'test this,' 'find bugs,' 'why is this broken,' 'it doesn't work,' 'check for bugs,' 'smoke test,' or after any significant code change. This is the full QA cycle: discover → reproduce → diagnose → fix → verify.
How do I install the QA Test and Fix skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add 0xranx/agentbrief --skill qa-test-and-fix. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is QA Test and Fix popular?
It lives in 0xranx/agentbrief, which has 43 GitHub stars and 0 forks.
Related skills
Typescript Advanced Types
430xranx/agentbrief
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
Analytics Setup
430xranx/agentbrief
When the user needs to set up product analytics, event tracking, or says 'set up analytics,' 'add tracking,' 'GA4,' 'Mixpanel,' 'PostHog,' 'Amplitude,' 'what events should we track,' 'conversion tracking,' 'funnel tracking,' or is launching a product and needs to instrument it for data collection.
API Documentation
430xranx/agentbrief
Create comprehensive API documentation for developers. Use when documenting REST APIs, GraphQL schemas, or SDK methods. Handles OpenAPI/Swagger, interactive docs, examples, and API reference guides.
Regression Testing
430xranx/agentbrief
When the user wants to prevent regressions, improve test coverage, or says 'add tests,' 'improve coverage,' 'we keep breaking this,' 'write regression tests,' 'characterization tests,' or after fixing a production bug to ensure it never recurs.
Guard Verification
44SamueleBassoli/hermes-fleet-apps
Use when code adds a guard. Prove tests catch its loss.
TDD
430xranx/agentbrief
Red-green-refactor cycle for test-driven development
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.