mcpField
Q
qa-reviewer

qa-reviewer

github.com/shipshitdevTesting & quality38221 installsUpdated 2d ago
Repository

About qa-reviewer

qa-reviewer is a skill for reviewing AI agent work before finalizing changes. It guides agents through requirement, accuracy, bug, completeness, and optimization checks, with repository-specific rules included in the review.

Key features

  1. 01Structured review phases
  2. 02Requirement and edge-case checks
  3. 03Accuracy and path verification
  4. 04Bug and syntax checks
  5. 05Completeness and optimization audits

Use cases

  1. 01Review a complex implementation
  2. 02Check changes before a major refactor commit
  3. 03Verify a new feature against requirements
  4. 04Audit work after a multi-step task

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/shipshitdev/skills --skill qa-reviewer

After installing, type/qa-reviewerin Claude Code to confirm it loaded.

Bundled filesreferences/full-guide.md

Details

From the project README

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 repository's instruction files (AGENTS.md, AGENTS.override.md, CLAUDE.md, or configured fallbacks)
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

# 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

Example checklist. Replace it with the rules in the repository's own instruction files.

  • No console.log (use logger)
  • No any types
  • No inline interfaces
  • Repository instruction files intact and scoped overrides intentional
  • Configured fallback instruction files exist and are nonempty
  • Agent configuration folders untouched unless the task required changes
  • Project invariants preserved (for example multi-tenancy, if the project has it)

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.

Comments

Markdown supported