skills/qa-reviewer/SKILL.md
Runs a structured multi-phase verification pass on completed AI agent work — catching bugs, missed requirements, and incorrect assumptions before changes are committed. Triggers on: "check your work", "review this", after complex multi-step implementations, before committing major refactors, or proactively after any task longer than five steps.
npx skillsauth add shipshitdev/library qa-reviewerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Structured framework for reviewing AI agent work before finalizing changes. Catches bugs, verifies accuracy, ensures completeness, validates solutions match requirements.
AGENTS.override.md / AGENTS.md
chain and explicitly configured fallback files; include CLAUDE.md for
Claude-specific rules# 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>
any typesFor 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.
development
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.