Back to Details

conductor-review

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Conductor Review

Conductor审查

Overview

概述

This skill provides a meticulous, first-principles code review. It compares implementation diffs against the "Law" (Style Guides), the "Identity" (Product Guidelines), and the "Mission" (Spec and Plan). It identifies critical bugs, safety risks, and architectural deviations.
本Skill提供基于第一性原理的细致代码审查。它将实现差异与“准则”（风格指南）、“特性定位”（产品指南）和“目标”（规格与计划）进行对比，识别关键bug、安全风险和架构偏差。

When to Use

使用场景

  • When a user says "Review my changes," "Is this track ready?", or "Run a code review."
  • Before archiving or deleting a completed track.
  • 当用户说“审查我的变更”、“这个track是否可以发布？”或“执行代码审查”时。
  • 在归档或删除已完成的track之前。

Workflow

工作流程

  1. Scope Selection: Identify the track or changes to review.
  2. Context Loading: Retrieve guidelines, style guides, and the track's plan.
  3. Meticulous Analysis: Perform a deep dive into the diff, checking for intent, style, safety, and security.
  4. Automated Testing: Run the project's test suite and report results.
  5. Reporting: Generate a structured Review Report with severity-ranked findings.
  6. Resolution: Offer to automatically apply fixes and update the implementation plan.
  1. 范围选择： 确定要审查的track或变更内容。
  2. 上下文加载： 获取指南、风格指南和track的计划。
  3. 细致分析： 深入分析代码差异，检查意图、风格、安全性和合规性。
  4. 自动化测试： 运行项目的测试套件并报告结果。
  5. 报告生成： 生成包含严重程度分级结果的结构化审查报告。
  6. 问题解决： 提供自动应用修复方案并更新实施计划的选项。

Implementation Details

实现细节

Refer to the following protocols for detailed procedural instructions:
  • Resolution Protocol: references/resolution-protocol.md - How to find Conductor artifacts.
  • Review Protocol: references/review-protocol.md - The logic for deep analysis, report generation, and automated fixing.
请参考以下协议获取详细的流程说明：
  • 解决协议： references/resolution-protocol.md - 如何查找Conductor工件。
  • 审查协议： references/review-protocol.md - 深度分析、报告生成和自动修复的逻辑。

Mandatory Constraints

强制约束

  • Style is Law: Violations of 
    conductor/code_styleguides/*.md
    are HIGH severity.
  • Automated Verification: ALWAYS attempt to run existing tests to verify correctness.
  • Plan Integrity: If fixes are applied, the 
    plan.md
    MUST be updated to record the review-related tasks and commits.
  • 风格即准则： 违反
    conductor/code_styleguides/*.md
    的问题属于高严重级别。
  • 自动化验证： 始终尝试运行现有测试以验证正确性。
  • 计划完整性： 如果应用了修复，必须更新
    plan.md
    以记录与审查相关的任务和提交记录。