Back to Details

advanced-engineer

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Advanced Engineer

高级工程师技能指南

Use this skill when the task requires disciplined engineering execution rather than a quick patch.
当任务需要严谨的工程执行而非快速补丁时，使用此技能。

Mission

核心目标

  • Understand the problem before changing code.
  • Fix root causes, not symptoms.
  • Keep changes minimal and consistent with the surrounding code.
  • Verify the result with real evidence before claiming success.
  • 在修改代码前先理解问题。
  • 修复根本原因，而非表面症状。
  • 保持修改最小化，且与周边代码风格一致。
  • 在宣告成功前，用实际证据验证结果。

Default Loop

默认工作循环

Work in a strict 
Plan -> Act -> Reflect
loop:
  1. Plan the next concrete step and what evidence it should produce.
  2. Act by reading code, running commands, or making the smallest justified change.
  3. Reflect on what changed, what was learned, and whether the hypothesis still holds.
Do not chain random actions together without updating the model of the problem.
严格遵循
Plan -> Act -> Reflect
（规划→执行→反思）循环：
  1. 规划下一步具体操作，以及该操作应产生的证据。
  2. 执行操作：阅读代码、运行命令，或进行最合理的最小化修改。
  3. 反思变化内容、所学知识，以及假设是否仍然成立。
切勿在未更新问题认知模型的情况下随意串联操作。

Start Here

初始步骤

  • For bugs, test failures, and broken integrations, start with references/05-debugging-and-root-cause-analysis.md.
  • For larger or multi-stage tasks, read references/02-planning-and-execution.md before splitting the work.
  • Before declaring success, read references/03-verification-and-review.md.
  • If the change risks broad refactoring, abstraction creep, or unsafe defaults, read references/01-engineering-fundamentals.md.
  • If the task involves destructive, public, or hard-to-reverse actions, read references/04-safe-delivery.md.
  • 针对Bug、测试失败和集成故障，从references/05-debugging-and-root-cause-analysis.md开始。
  • 针对大型或多阶段任务，在拆分工作前先阅读references/02-planning-and-execution.md。
  • 在宣告成功前，阅读references/03-verification-and-review.md。
  • 若修改可能引发大范围重构、抽象过度或不安全默认设置，阅读references/01-engineering-fundamentals.md。
  • 若任务涉及破坏性、公开或难以撤销的操作，阅读references/04-safe-delivery.md。

Keep In SKILL Context

技能核心原则

  • Do not patch code you do not yet understand.
  • Prefer explicit hypotheses over intuition.
  • Increase investigation depth when an attempt fails.
  • Preserve existing behavior unless the task requires changing it.
  • Be explicit when verification is partial.
  • 不要修改尚未理解的代码。
  • 优先采用明确的假设而非直觉判断。
  • 当尝试失败时，加深调查深度。
  • 除非任务要求，否则保留现有行为。
  • 当验证不完整时，需明确说明。

Reference Index

参考文档索引

Read only the references needed for the current task.
仅阅读当前任务所需的参考文档。

references/01-engineering-fundamentals.md

references/01-engineering-fundamentals.md

Read for:
  • change scope discipline
  • avoiding over-engineering and premature abstractions
  • reading code before editing
  • boundary validation and secure-by-default decisions
  • what to do when an approach is blocked
阅读目的：
  • 变更范围管控
  • 避免过度工程与过早抽象
  • 编辑前先阅读代码
  • 边界验证与默认安全决策
  • 当方案受阻时的应对方法

references/02-planning-and-execution.md

references/02-planning-and-execution.md

Read for:
  • iterative planning
  • decomposition for larger tasks
  • parallel work or worker orchestration
  • completion protocol for delegated work
阅读目的：
  • 迭代式规划
  • 大型任务拆分
  • 并行工作或任务编排
  • 委托工作的完成流程

references/03-verification-and-review.md

references/03-verification-and-review.md

Read for:
  • adversarial verification
  • writing a verification plan
  • review and simplification passes before declaring completion
阅读目的：
  • 对抗性验证
  • 编写验证计划
  • 宣告完成前的审查与简化环节

references/04-safe-delivery.md

references/04-safe-delivery.md

Read for:
  • destructive action thresholds
  • git safety
  • commit, PR, and hook discipline
  • when to confirm with the user before taking irreversible actions
阅读目的：
  • 破坏性操作阈值
  • Git安全规范
  • 提交、PR与钩子规范
  • 执行不可逆操作前需与用户确认的场景

references/05-debugging-and-root-cause-analysis.md

references/05-debugging-and-root-cause-analysis.md

Read for:
  • Plan -> Act -> Reflect
  • investigation before modification
  • root-cause-first debugging
  • hypothesis-driven debugging
  • escalation strategy after failed attempts
  • verification pipeline and partial-verification rules
  • tool-first investigation and when to ask the user
阅读目的：
  • Plan -> Act -> Reflect
    循环
  • 修改前先调查
  • 以根因为导向的调试
  • 基于假设的调试
  • 尝试失败后的升级策略
  • 验证流程与部分验证规则
  • 工具优先的调查方法及何时向用户求助

Completion Criteria

完成标准

Treat the task as complete only when:
  • the root cause is understood
  • the fix addresses that cause
  • the result is verified, or the verification limit is stated clearly
  • nearby regressions have been checked
  • the chosen references were actually applied to the task at hand
Do not report success based on a plausible diff alone.
仅当满足以下所有条件时，才可视为任务完成：
  • 已明确问题根本原因
  • 修复方案针对该根本原因
  • 结果已验证，或明确说明验证限制
  • 已检查周边代码是否存在回归问题
  • 已将所选参考文档的内容应用于当前任务
切勿仅依据看似合理的代码差异就宣告成功。