review
Reviews code for quality, security, performance, and accessibility issues. Use when user mentions レビュー, review, コードレビュー, セキュリティ, パフォーマンス, 品質チェック, セルフレビュー, PR, diff, 変更確認. Do NOT load for: 実装作業, 新機能開発, バグ修正, セットアップ.
plan-review
Expert technical reviewer for implementation plans. Reviews plans in docs/plans/ for correctness, completeness, and technical accuracy. Validates libraries, APIs, and approaches. Outputs feedback as markdown in the final response.
next-silent-failure-hunter
Identify silent failures, inadequate error handling, and inappropriate fallback behavior. Use when reviewing code with error handling, catch blocks, or fallback logic.
next-code-reviewer
Review code for adherence to project guidelines, style guides, and best practices. Use after writing or modifying code, before committing changes or creating pull requests.
code-review
Get quality code reviews from Claude Code - PR workflows, review prompts, checklists
ui-ux-a11y-static-review
This skill should be used when performing static UI/UX and accessibility reviews of frontend codebases and producing a three-step report (context mapping, violations, executive synthesis) from code only.
review-implementing
Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.
magic-model-review
Evaluates Magic Model (Triangle) frameworks for BlackBelt coaches using Ed Dale's frameworks. Produces Facebook-ready feedback comments.
offer-diamond-review
Evaluates Offer Diamonds for BlackBelt coaches using Ed Dale's frameworks. Produces Facebook-ready feedback comments.
proposal-reviewer
Acts as a Contextual Analyst. Reviews pending proposals by checking the codebase to establish *plausibility* and *value*. Approves proposals where the code context supports the suggested improvements.
technical-review
Validate completed implementation against plan tasks and acceptance criteria. Sixth phase of research-discussion-specification-plan-implement-review workflow. Use when: (1) Implementation phase is complete, (2) User wants validation before merging/shipping, (3) Quality gate check needed after implementation. Reviews ALL plan tasks for implementation correctness, test adequacy, and code quality. Produces structured feedback (approve, request changes, or comments) - does NOT fix code.
plan-reviewer
Review implementation plans for completeness and feasibility. Use when user says "review this plan before I start", "is this implementation plan complete", "check if this plan aligns with our patterns", "give me feedback on my implementation strategy", or "validate this plan before we execute it".
pr-issue-resolver
Fix PR issues including review comments and CI failures. Use when user says "fix the failing CI on my PR", "address the review comments on PR #123", "my PR has failing checks", "help me resolve the feedback on my pull request", "the build is failing on my PR", or "make my PR merge-ready".
pr-reviewer
Review pull requests for quality, security, and performance. Use when user says "review my changes before I merge", "do a code review on this PR", "check if this is ready to merge", "review the diff for any issues", "give me feedback on these changes", or "is this PR ready for review".
reviewing
Get second opinions from external models (Codex, Gemini) for adversarial review, tie-breaking, and multi-model consensus. Use when validating critical decisions or when stuck.
code-review
This skill should be used when the user asks to "review code", "review PR", "code review", "audit code", "check for bugs", "security review", "review my changes", "find issues in this code", "review the diff", or asks for pull request review or code audit.
oracle-codex
This skill should be used when the user asks to "use Codex", "ask Codex", "consult Codex", "Codex review", "use GPT for planning", "ask GPT to review", "get GPT's opinion", "what does GPT think", "second opinion on code", "consult the oracle", "ask the oracle", or mentions using an AI oracle for planning or code review. NOT for implementation tasks.
oracle-gemini
This skill should be used when the user asks to "use Gemini", "ask Gemini", "consult Gemini", "Gemini review", "use Gemini for planning", "ask Gemini to review", "get Gemini's opinion", "what does Gemini think", "second opinion from Gemini", mentions using Gemini as an oracle for planning or code review. NOT for implementation tasks.