qa-reviewer
AI work QA review.
What this skill does
# QA Reviewer: Systematic Work Verification ## Purpose Structured framework for reviewing AI agent work before finalizing changes. Catches bugs, verifies accuracy, ensures completeness, validates solutions match requirements. **Why this exists:** AI agents can introduce subtle bugs, miss requirements, or make incorrect assumptions. ## When to Use - User says "check your work" or "review this" - After completing complex multi-step implementations - Before committing major refactors - When modifying commands or skills - After implementing new features - Proactively after any task >5 steps ## QA Workflow Phases ### 1. Context Gathering - Review original task and requirements - List all deliverables (files created/modified/deleted) - Check critical rules (CLAUDE.md — repo-level and global) ### 2. Requirement Verification - Create checklist of all requirements - Verify solution alignment - Check for edge cases ### 3. Accuracy Verification - Verify file paths exist - Confirm patterns match codebase - Cross-reference citations ### 4. Bug Detection - Check syntax (markdown, code, paths) - Look for logic errors - Verify project-specific rules ### 5. Completeness Audit - Reconcile todo list - Verify all mentioned files changed - Check for side effects ### 6. Optimization Review - Evaluate solution quality - Check pattern consistency - Consider alternatives ## Quick Verification Commands ```bash # Verify file exists ls -la <file-path> # Check balanced code blocks grep -c '```' file.md # Find violations grep -r "console\.log" <files> grep -r ": any" <files> ``` ## Project Rules Check - [ ] No console.log (use logger) - [ ] No `any` types - [ ] No inline interfaces - [ ] AGENTS/CLAUDE/CODEX files intact - [ ] .agents/ folders untouched - [ ] Multi-tenancy preserved ## Final Assessment Categories - **Approve** - Ready to commit - **Conditional** - Fix issues first - **Reject** - Significant problems --- **For complete workflow phases, output format template, common issue patterns, and advanced techniques, see:** `references/full-guide.md`
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.