quality-reviewing
Deep code review with web research. USE WHEN user says 'double check against latest', 'verify versions', 'check security'. Complements automatic quality hook with ecosystem verification.
When & Why to Use This Skill
The Quality Reviewing skill provides an advanced, research-driven code analysis layer that goes beyond standard static checks. By leveraging real-time web research, it validates your codebase against the latest 2025 ecosystem standards, identifying outdated library versions, security vulnerabilities, and deprecated API usage to ensure high-performance, secure, and modern software development.
Use Cases
- Version Verification: Automatically check if your project's libraries (e.g., React, Node.js) are running on the latest stable versions and identify critical upgrade paths to avoid technical debt.
- Security Auditing: Scan current dependencies against real-time web databases to flag and mitigate critical security vulnerabilities before they reach production.
- Documentation Compliance: Cross-reference your implementation with the most recent official documentation to ensure you are using the latest recommended patterns and avoiding deprecated functions.
- BDD Workflow Integration: Conduct targeted research during different development phases, from discovering architectural patterns during intake to verifying CI/CD checklists at the completion stage.
- Pre-change Deep Dive: Perform a comprehensive review of existing code before making major modifications to ensure the proposed architecture aligns with current industry best practices.
| name | quality-reviewing |
|---|---|
| description | Deep code review with web research. USE WHEN user says 'double check against latest', 'verify versions', 'check security'. Complements automatic quality hook with ecosystem verification. |
| allowed-tools | '*' |
Quality Reviewing
Deep review with web research to verify against current ecosystem. Complements automatic hook.
When to use this skill (not automatic hook):
- Explicit web research: "double check against latest docs", "verify versions", "check security"
- Deep dive needed: Performance, architecture, trade-offs beyond automatic hook
- Pre-change review: Review before making changes (hook only triggers after)
Relationship: Automatic hook does fast check with existing knowledge. This skill does deep dive with web research (2-3 min).
1. Detect Phase
If in BDD workflow, read current ticket from .safeword-project/tickets/ and apply phase-appropriate research:
| Phase | Research Focus |
|---|---|
| intake | Similar features in ecosystem, scope patterns |
| define-behavior | Testing patterns, BDD best practices |
| decomposition | Architecture patterns, test layer strategy |
| implement | Library versions, deprecated APIs, security |
| done | CI/CD patterns, release checklists |
2. Verify Versions (Primary Value)
CRITICAL: This is your main differentiator from automatic hook.
Search for: "[library name] latest stable version 2025" Search for: "[library name] security vulnerabilities"
Flag if outdated:
- Major versions behind -> WARN (e.g., React 17 when 19 is stable)
- Minor versions behind -> NOTE
- Security vulnerabilities -> CRITICAL (must upgrade)
- Using latest -> Confirm
3. Verify Documentation (Primary Value)
Fetch official documentation for libraries in use.
Look for:
- Deprecated APIs being used?
- Newer, better patterns available?
- Recent recommendation changes?
Output Format
## Quality Review
**Versions:** [✓/⚠️/❌] [Latest version check]
**Documentation:** [✓/⚠️/❌] [Current docs check]
**Security:** [✓/⚠️/❌] [Vulnerability check]
**Verdict:** [APPROVE / REQUEST CHANGES / NEEDS DISCUSSION]
**Critical issues:** [List or "None"]
**Suggested improvements:** [List or "None"]
Reminders
- Primary value: Web research - Verify versions, docs, security
- Complement automatic hook - Hook checks correctness/elegance/bloat, you verify ecosystem
- Phase matters - Adapt research focus to current BDD phase
- Be concise - Hook already prompts for general quality, focus on what it can't do