Skip to main content

qa-reviewer

Runs a multi-phase verification pass on finished AI agent work to catch bugs, missed requirements, and bad assumptions. Use after long multi-step tasks or on check your work.

Informations de source

Dépôt
shipshitdev/skills
Dernière activité de la source
7 octobre 2026 à 07:31
Langue détectée de SKILL.md
anglais
Étoiles
38
Forks
3

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers
3 fichiers

Affichage de SKILL.md

SKILL.md
Instructions source · Aperçu en lecture seule
name
qa-reviewer
description
Runs a multi-phase verification pass on finished AI agent work to catch bugs, missed requirements, and bad assumptions. Use after long multi-step tasks or on check your work.
metadata
{"version":"2.2.4","tags":"quality-assurance, verification, code-review, accuracy, completeness"}
when_to_use
check your work, verify before commit
# 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. ## 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 in the applicable `AGENTS.override.md` / `AGENTS.md` chain and explicitly configured fallback files; include `CLAUDE.md` for Claude-specific rules ### 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 - [ ] Applicable AGENTS files intact and scoped overrides intentional - [ ] Configured fallback instruction files exist and are nonempty - [ ] .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, load `${CLAUDE_SKILL_DIR}/references/full-guide.md` when performing a comprehensive QA pass or when the task has more than three deliverables.
Voir sur GitHub