| name | quality-reviewer |
| description | Deep code review with web research to verify against latest ecosystem. Use when user says 'double check against latest', 'verify versions', 'check security', 'review against docs', or needs deep analysis beyond automatic quality hook. |
| allowed-tools | * |
Quality Reviewer
Deep quality review with web research to verify code against the latest ecosystem state.
Primary differentiator: Web research to verify against current versions, documentation, and best practices.
Triggers:
- Explicit web research request: "double check against latest docs", "verify we're using latest version", "check for security issues"
- Deep dive needed: User wants analysis beyond automatic hook (performance, architecture alternatives, trade-offs)
- No SAFEWORD.md/CLAUDE.md: Projects without context files (automatic hook won't run, manual review needed)
- Pre-change review: User wants review before making changes (automatic hook only triggers after changes)
Relationship to automatic quality hook:
- Automatic hook: Fast quality check using existing knowledge + project context (guaranteed, runs on every change)
- This skill: Deep review with web research when verification against current ecosystem is needed (on-demand, 2-3 min)
Review Protocol
1. Identify What Changed
Understand context:
- What files were just modified?
- What problem is being solved?
- What was the implementation approach?
