Review

作者 parcadeid07ff4b06b62無授權條款3.9K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫8 個月前更新

Comprehensive code review workflow - parallel specialized reviews → synthesis

AI 產生的概覽

執行多視角程式碼審查流程,平行進行專項審查並給出最終綜合結論。

功能
此技能定義一套程式碼審查流程,將審查工作平行分派給多個專項代理,分別關注程式碼品質、架構一致性與變更影響。接著由綜合代理彙整各項發現,給出 APPROVE、REQUEST_CHANGES 或 NEEDS_DISCUSSION 的最終結論,並列出依優先順序排列的阻擋與非阻擋事項。它也說明了完整審查、快速審查、安全專項審查與拉取請求審查等模式。
適用情境
適用於被要求審查程式碼、拉取請求或合併前的實作,或需要設置品質關卡的場合。也適合針對重要變更取得回饋與風險評估的要求。
執行需求
僅為說明性指示,未包含指令碼。它假定執行環境支援依指定代理類型(critic、plan-reviewer、review-agent,以及選用的 aegis)分派子代理任務,並支援背景執行。

/review - Code Review Workflow

Multi-perspective code review with parallel specialists.

When to Use

  • "Review this code"
  • "Review my PR"
  • "Check this before I merge"
  • "Get feedback on implementation"
  • Before merging significant changes
  • Quality gates

Workflow Overview

         ┌──────────┐         │  critic  │ ─┐         │ (code)   │  │         └──────────┘  │                       │         ┌──────────┐  │      ┌──────────────┐         │plan-reviewer│ ─┼────▶ │ review-agent │         │ (plan)   │  │      │ (synthesis)  │         └──────────┘  │      └──────────────┘                       │         ┌──────────┐  │         │plan-reviewer│ ─┘         │ (change) │         └──────────┘
         Parallel                Sequential         perspectives            synthesis

Agent Sequence

#AgentFocusExecution
1criticCode quality, patterns, readabilityParallel
1plan-reviewerArchitecture, plan adherenceParallel
1plan-reviewerChange impact, risk assessmentParallel
2review-agentSynthesize all reviews, final verdictAfter 1

Review Perspectives

  • critic: Is this good code? (Style, patterns, readability)
  • plan-reviewer: Does this match the design? (Architecture, plan)
  • plan-reviewer: Is this change safe? (Risk, impact, regressions)
  • review-agent: Overall assessment and recommendations

Execution

Phase 1: Parallel Reviews

# Code quality reviewTask(  subagent_type="critic",  prompt="""  Review code quality: [SCOPE]
  Evaluate:  - Code style and consistency  - Design patterns used  - Readability and maintainability  - Error handling  - Test coverage
  Output: List of issues with severity (critical/major/minor)  """,  run_in_background=true)
# Architecture reviewTask(  subagent_type="plan-reviewer",  prompt="""  Review architecture alignment: [SCOPE]
  Check:  - Follows established patterns  - Matches implementation plan (if exists)  - Consistent with system design  - No architectural violations
  Output: Alignment assessment with concerns  """,  run_in_background=true)
# Change impact reviewTask(  subagent_type="plan-reviewer",  prompt="""  Review change impact: [SCOPE]
  Assess:  - Risk level of changes  - Affected systems/components  - Backward compatibility  - Potential regressions  - Security implications
  Output: Risk assessment with recommendations  """,  run_in_background=true)
# Wait for all parallel reviews[Check TaskOutput for all three]

Phase 2: Synthesis

Task(  subagent_type="review-agent",  prompt="""  Synthesize reviews for: [SCOPE]
  Reviews:  - critic: [code quality findings]  - plan-reviewer: [architecture findings]  - plan-reviewer: [change impact findings]
  Create final review:  - Overall verdict (APPROVE / REQUEST_CHANGES / NEEDS_DISCUSSION)  - Prioritized action items  - Blocking vs non-blocking issues  - Summary for PR description  """)

Review Modes

Full Review

User: /review→ All four agents, comprehensive review

Quick Review

User: /review --quick→ critic only, fast feedback

Security Focus

User: /review --security→ Add aegis (security agent) to parallel phase

PR Review

User: /review PR #123→ Fetch PR diff, review changes

Example

User: /review the authentication changes
Claude: Starting /review workflow...
Phase 1: Running parallel reviews...┌────────────────────────────────────────────┐│ critic: Reviewing code quality...          ││ plan-reviewer: Checking architecture...         ││ plan-reviewer: Assessing change impact...         │└────────────────────────────────────────────┘
critic: Found 2 issues- [minor] Inconsistent error messages in auth.ts- [major] Missing input validation in login()
plan-reviewer: ✅ Matches authentication plan
plan-reviewer: Medium risk- Affects: login, signup, password reset- Breaking change: session token format
Phase 2: Synthesizing...
┌─────────────────────────────────────────────┐│ Review Summary                              │├─────────────────────────────────────────────┤│ Verdict: REQUEST_CHANGES                    ││                                             ││ Blocking:                                   ││ 1. Add input validation to login()          ││                                             ││ Non-blocking:                               ││ 2. Standardize error messages               ││                                             ││ Notes:                                      ││ - Document session token format change      ││ - Consider migration path for existing      ││   sessions                                  │└─────────────────────────────────────────────┘

Verdicts

  • APPROVE: Ready to merge, all issues are minor
  • REQUEST_CHANGES: Blocking issues must be fixed
  • NEEDS_DISCUSSION: Architectural decisions need input

來源與署名

來源:parcadei/continuous-claude-v3位於.claude/skills/review提交d07ff4b

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架