Back to Details

quick

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Quick Code Review

快速代码审查

Context

上下文

  • Current branch: !
    git branch --show-current
  • Git status: !
    git status --porcelain
  • Base branch: !
    (git show-branch | grep '*' | grep -v "$(git rev-parse --abbrev-ref HEAD)" | head -1 | sed 's/.*\[\([^]]*\)\].*/\1/' | sed 's/\^.*//' 2>/dev/null) || echo "develop"
  • Changes since base: !
    BASE=$(git merge-base HEAD develop 2>/dev/null || git merge-base HEAD main 2>/dev/null) && git log --oneline $BASE..HEAD
  • Files changed since base: !
    BASE=$(git merge-base HEAD develop 2>/dev/null || git merge-base HEAD main 2>/dev/null) && git diff --name-only $BASE..HEAD
  • Test commands available: !
    ([ -f package.json ] && echo "npm/pnpm/yarn test") || ([ -f Cargo.toml ] && echo "cargo test") || ([ -f pyproject.toml ] && echo "pytest/uv run pytest") || ([ -f go.mod ] && echo "go test") || echo "no standard test framework detected"
  • 当前分支: !
    git branch --show-current
  • Git状态: !
    git status --porcelain
  • 基准分支: !
    (git show-branch | grep '*' | grep -v "$(git rev-parse --abbrev-ref HEAD)" | head -1 | sed 's/.*\[\([^]]*\)\].*/\1/' | sed 's/\^.*//' 2>/dev/null) || echo "develop"
  • 相对于基准分支的变更记录: !
    BASE=$(git merge-base HEAD develop 2>/dev/null || git merge-base HEAD main 2>/dev/null) && git log --oneline $BASE..HEAD
  • 相对于基准分支的变更文件: !
    BASE=$(git merge-base HEAD develop 2>/dev/null || git merge-base HEAD main 2>/dev/null) && git diff --name-only $BASE..HEAD
  • 可用测试命令: !
    ([ -f package.json ] && echo "npm/pnpm/yarn test") || ([ -f Cargo.toml ] && echo "cargo test") || ([ -f pyproject.toml ] && echo "pytest/uv run pytest") || ([ -f go.mod ] && echo "go test") || echo "no standard test framework detected"

Requirements

要求

  • Use @tech-lead-reviewer — architectural impact assessment — to scope the review and decide which specialized agents are required.
  • Launch only the necessary specialized reviews to minimize turnaround time.
  • Summarize results by priority (Critical → High → Medium → Low) and confidence (High → Medium → Low).
  • Offer optional implementation support and ensure resulting commits follow Git commit conventions (See 
    ${CLAUDE_PLUGIN_ROOT}/skills/references/git-commit-conventions.md
    for details).
  • 使用**@tech-lead-reviewer** — 架构影响评估 — 来确定审查范围，并决定需要哪些专项Agent。
  • 仅启动必要的专项审查，以缩短周转时间。
  • 按优先级（严重→高→中→低）和可信度（高→中→低）总结结果。
  • 提供可选的实现支持，并确保最终提交符合Git提交规范（详情见
    ${CLAUDE_PLUGIN_ROOT}/skills/references/git-commit-conventions.md
    ）。

Your Task

你的任务

IMPORTANT: You MUST use the Task tool to complete ALL tasks.
  1. Run an initial assessment with @tech-lead-reviewer — architectural impact assessment — to gauge architectural, security, and UX risk, and determine if a deeper review is needed.
  2. Trigger the relevant specialized reviews via the Task tool, gather targeted feedback, and resolve conflicting recommendations.
  3. Present a concise summary, ask whether the user wants fixes implemented, and if confirmed, apply changes, refactor with @code-simplifier — code simplification and optimization —, test, and stage commits before reporting outcomes.
重要提示：你必须使用Task工具完成所有任务。
  1. 与**@tech-lead-reviewer** — 架构影响评估 — 进行初始评估，以衡量架构、安全和UX风险，并判断是否需要深入审查。
  2. 通过Task工具触发相关专项审查，收集针对性反馈，并解决相互冲突的建议。
  3. 呈现简洁的总结，询问用户是否需要修复问题；若确认，则应用变更，通过**@code-simplifier** — 代码简化与优化 — 进行重构，测试并暂存提交，然后报告结果。

Targeted Review Flow

针对性审查流程

  • Selective Agents:
    • @code-reviewer — logic correctness, tests, error handling.
    • @security-reviewer — authentication, data protection, validation.
    • @ux-reviewer — usability and accessibility (skip if purely backend/CLI).
  • Results Analysis: Organize findings using the priority/confidence matrix and provide actionable steps.
  • Optional Implementation: Execute requested fixes, optimize the code, rerun tests, and prepare commits that adhere to the standards fragment.
  • Closure: Push updates if changes were made and confirm review completion with the user.
  • 可选Agent:
    • @code-reviewer — 逻辑正确性、测试、错误处理。
    • @security-reviewer — 身份验证、数据保护、验证。
    • @ux-reviewer — 可用性与可访问性（若为纯后端/CLI则跳过）。
  • 结果分析: 使用优先级/可信度矩阵整理发现的问题，并提供可执行步骤。
  • 可选实现: 执行用户要求的修复，优化代码，重新运行测试，并准备符合规范的提交。
  • 收尾: 若有变更则推送更新，并向用户确认审查完成。