ln-810-performance-optimization-coordinator
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChinesePaths: File paths (,shared/,references/) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.../ln-*
路径说明: 文件路径(、shared/、references/)是相对于技能仓库根目录的。如果在当前工作目录(CWD)中未找到,则定位到该SKILL.md所在目录,然后向上一级即为仓库根目录。../ln-*
ln-810-performance-optimization-coordinator
ln-810-performance-optimization-coordinator
Type: L2 Domain Coordinator
Category: 8XX Optimization
Coordinates performance optimization by delegating to L3 workers: ln-811 (algorithm), ln-812 (query), ln-813 (runtime). Workers run in parallel when inputs are independent.
类型: L2领域协调器
分类: 8XX优化类
通过委托给L3级Worker(ln-811(算法优化)、ln-812(查询优化)、ln-813(运行时优化))来协调性能优化工作。当输入相互独立时,Worker会并行运行。
Overview
概述
| Aspect | Details |
|---|---|
| Input | Target file/module OR audit report (ln-650 output) |
| Output | Optimized code with verification proof |
| Workers | ln-811 (algorithm), ln-812 (query), ln-813 (runtime) |
| 方面 | 详情 |
|---|---|
| 输入 | 目标文件/模块 或 审计报告(ln-650的输出结果) |
| 输出 | 带有验证证明的优化后代码 |
| Worker | ln-811(算法)、ln-812(查询)、ln-813(运行时) |
Workflow
工作流程
Phases: Pre-flight → Analyze Input → Delegate → Collect → Verify → Report
阶段: 预检 → 分析输入 → 委托任务 → 收集结果 → 验证 → 生成报告
Phase 0: Pre-flight Checks
阶段0:预检检查
| Check | Required | Action if Missing |
|---|---|---|
| Target file OR audit report | Yes | Block optimization |
| Git clean state | Yes | Block (need clean baseline for revert) |
| Test infrastructure | Yes | Block (workers need tests for keep/discard) |
MANDATORY READ: Load for test/build detection.
shared/references/ci_tool_detection.md| 检查项 | 是否必填 | 缺失时操作 |
|---|---|---|
| 目标文件或审计报告 | 是 | 阻止优化操作 |
| Git仓库处于干净状态 | 是 | 阻止操作(需要干净的基线用于回滚) |
| 测试基础设施 | 是 | 阻止操作(Worker需要测试环境来决定保留/丢弃优化) |
必读提示: 加载以检测测试/构建工具。
shared/references/ci_tool_detection.mdPhase 1: Analyze Input
阶段1:输入分析
Input Sources
输入来源
| Source | Detection | Workers Activated |
|---|---|---|
| ln-650 output exists | ln-812 (query) + ln-813 (runtime) |
| Target file + function | User-specified | ln-811 (algorithm) |
| Full audit report | All ln-65X sections present | All three workers |
| 来源 | 检测条件 | 激活的Worker |
|---|---|---|
| 存在ln-650的输出结果 | ln-812(查询)+ ln-813(运行时) |
| 目标文件+函数 | 用户指定 | ln-811(算法) |
| 完整审计报告 | 包含所有ln-65X部分的内容 | 三个Worker全部激活 |
Worker Selection
Worker选择逻辑
| Condition | ln-811 | ln-812 | ln-813 |
|---|---|---|---|
| Target function specified | Yes | No | No |
| ln-651 findings present | No | Yes | No |
| ln-653 findings present | No | No | Yes |
| All audit findings | Conditional* | Yes | Yes |
*ln-811 activated only if specific algorithmic inefficiency identified in audit.
| 条件 | ln-811 | ln-812 | ln-813 |
|---|---|---|---|
| 指定了目标函数 | 是 | 否 | 否 |
| 存在ln-651的检测结果 | 否 | 是 | 否 |
| 存在ln-653的检测结果 | 否 | 否 | 是 |
| 包含所有审计结果 | 条件触发* | 是 | 是 |
*仅当审计中识别出特定算法低效问题时,才会激活ln-811。
Phase 2: Delegate to Workers
阶段2:委托任务给Worker
CRITICAL: All delegations use Task tool withandsubagent_type: "general-purpose"— each worker creates its own branch perisolation: "worktree".shared/references/git_worktree_fallback.md
重要提示: 所有委托操作均使用Task工具,配置和subagent_type: "general-purpose"—— 每个Worker会根据isolation: "worktree"创建自己的分支。shared/references/git_worktree_fallback.md
Delegation Protocol
委托协议
FOR each selected worker:
Task(description: "Optimize via ln-81X",
prompt: "Execute ln-81X-{worker}. Read skill from ln-81X-{worker}/SKILL.md. Context: {delegationContext}",
subagent_type: "general-purpose",
isolation: "worktree")FOR each selected worker:
Task(description: "Optimize via ln-81X",
prompt: "Execute ln-81X-{worker}. Read skill from ln-81X-{worker}/SKILL.md. Context: {delegationContext}",
subagent_type: "general-purpose",
isolation: "worktree")Delegation Context
委托上下文
| Field | Type | Description |
|---|---|---|
| projectPath | string | Absolute path to project |
| auditReport | string | Path to persistence_audit.md (if applicable) |
| targetFile | string | Target file path (if applicable) |
| targetFunction | string | Target function name (if applicable) |
| options.runTests | bool | Run tests after optimization |
| options.runLint | bool | Run lint after optimization |
| 字段 | 类型 | 描述 |
|---|---|---|
| projectPath | 字符串 | 项目的绝对路径 |
| auditReport | 字符串 | persistence_audit.md的路径(如适用) |
| targetFile | 字符串 | 目标文件路径(如适用) |
| targetFunction | 字符串 | 目标函数名称(如适用) |
| options.runTests | 布尔值 | 优化后是否运行测试 |
| options.runLint | 布尔值 | 优化后是否运行代码检查 |
Parallelism
并行规则
| Workers | Can Parallel | Reason |
|---|---|---|
| ln-812 + ln-813 | Yes | Different files, different fix types |
| ln-811 + ln-812 | Depends | Only if targeting different files |
| ln-811 + ln-813 | Depends | Only if targeting different files |
Rules:
- If workers target the SAME file, run sequentially (ln-811 first, then ln-812/813).
- Dependent workers share branch: If worker B depends on worker A's output (e.g., ln-813 needs ln-812's query changes), launch worker B in worker A's branch — so B sees A's changes.
| Worker组合 | 是否可并行 | 原因 |
|---|---|---|
| ln-812 + ln-813 | 是 | 处理不同文件,修复类型不同 |
| ln-811 + ln-812 | 视情况而定 | 仅当目标为不同文件时可并行 |
| ln-811 + ln-813 | 视情况而定 | 仅当目标为不同文件时可并行 |
规则:
- 如果Worker的目标是同一个文件,则按顺序运行(先ln-811,再ln-812/813)。
- 依赖Worker共享分支: 如果Worker B依赖Worker A的输出(例如ln-813需要ln-812的查询修改结果),则在Worker A的分支中启动Worker B —— 这样B就能看到A的修改。
Phase 3: Collect Results
阶段3:收集结果
Each worker produces an isolated branch. Coordinator aggregates branch reports.
每个Worker会生成一个独立分支。协调器会汇总各分支的报告。
Worker Branches
Worker分支
| Worker | Branch Pattern | Contents |
|---|---|---|
| ln-811 | | Algorithm optimizations with benchmarks |
| ln-812 | | Query optimizations |
| ln-813 | | Runtime optimizations |
| Worker | 分支命名规则 | 内容 |
|---|---|---|
| ln-811 | | 带有基准测试数据的算法优化结果 |
| ln-812 | | 查询优化结果 |
| ln-813 | | 运行时优化结果 |
Result Schema
结果数据结构
| Field | Type | Description |
|---|---|---|
| worker | string | ln-811, ln-812, or ln-813 |
| status | enum | success, partial, failed |
| branch | string | Worker's result branch name |
| fixes_applied | int | Number of kept optimizations |
| fixes_discarded | int | Number of discarded attempts |
| details | object | Worker-specific report |
| 字段 | 类型 | 描述 |
|---|---|---|
| worker | 字符串 | ln-811、ln-812或ln-813 |
| status | 枚举值 | success(成功)、partial(部分成功)、failed(失败) |
| branch | 字符串 | Worker生成的结果分支名称 |
| fixes_applied | 整数 | 保留的优化修复数量 |
| fixes_discarded | 整数 | 丢弃的优化尝试数量 |
| details | 对象 | Worker专属的详细报告 |
Phase 4: Aggregate Reports
阶段4:汇总报告
Each worker verified independently in its branch (tests, build, lint run by worker itself). Coordinator does NOT rerun verification or revert worker changes.
每个Worker会在自己的分支中独立完成验证(测试、构建、代码检查由Worker自行运行)。协调器不会重新运行验证或回滚Worker的修改。
On Failure
失败处理
- Branch with failing tests logged as "failed" in report
- User reviews failed branch independently
- 将测试失败的分支在报告中标记为“failed”
- 用户需独立审查失败分支
Phase 5: Report Summary
阶段5:报告摘要
Report Schema
报告数据结构
| Field | Description |
|---|---|
| input_source | Audit report or target file |
| workers_activated | Which workers ran |
| total_fixes_applied | Sum across all workers |
| total_fixes_discarded | Sum across all workers |
| build_verified | PASSED or FAILED |
| per_worker[] | Individual worker reports |
| algorithm_improvement | Benchmark improvement % (ln-811 only) |
| 字段 | 描述 |
|---|---|
| input_source | 输入来源(审计报告或目标文件) |
| workers_activated | 已激活的Worker列表 |
| total_fixes_applied | 所有Worker保留的修复总数 |
| total_fixes_discarded | 所有Worker丢弃的修复总数 |
| build_verified | 构建验证结果(PASSED或FAILED) |
| per_worker[] | 各Worker的独立报告 |
| algorithm_improvement | 算法性能提升百分比(仅ln-811提供) |
Configuration
配置项
yaml
Options:
# Input
audit_report: "docs/project/persistence_audit.md"
target_file: ""
target_function: ""
# Workers
enable_algorithm: true
enable_query: true
enable_runtime: true
# Verification
run_tests: true
run_build: true
run_lint: true
# Safety
revert_on_build_failure: trueyaml
Options:
# Input
audit_report: "docs/project/persistence_audit.md"
target_file: ""
target_function: ""
# Workers
enable_algorithm: true
enable_query: true
enable_runtime: true
# Verification
run_tests: true
run_build: true
run_lint: true
# Safety
revert_on_build_failure: trueError Handling
错误处理
Recoverable Errors
可恢复错误
| Error | Recovery |
|---|---|
| Worker timeout | Log timeout, continue with other workers |
| Single worker failure | Revert worker changes, report partial success |
| Build failure | Revert last worker, re-verify |
| 错误类型 | 恢复措施 |
|---|---|
| Worker超时 | 记录超时信息,继续执行其他Worker |
| 单个Worker失败 | 回滚该Worker的修改,报告部分成功 |
| 构建失败 | 回滚最后一个Worker的修改,重新验证 |
Fatal Errors
致命错误
| Error | Action |
|---|---|
| No workers activated | Report "no optimization targets found" |
| All workers failed | Report failures, suggest manual review |
| Dirty git state | Block with "commit or stash changes first" |
| 错误类型 | 操作 |
|---|---|
| 无Worker被激活 | 报告“未找到优化目标” |
| 所有Worker均失败 | 报告所有失败情况,建议手动审查 |
| Git仓库状态未清理 | 阻止操作,提示“请先提交或暂存更改” |
References
参考文档
../ln-811-algorithm-optimizer/SKILL.md../ln-812-query-optimizer/SKILL.md../ln-813-runtime-optimizer/SKILL.mdshared/references/ci_tool_detection.md
../ln-811-algorithm-optimizer/SKILL.md../ln-812-query-optimizer/SKILL.md../ln-813-runtime-optimizer/SKILL.mdshared/references/ci_tool_detection.md
Definition of Done
完成标准
- Input analyzed (audit report or target file/function)
- Appropriate workers selected based on input type
- Workers delegated with worktree isolation ()
isolation: "worktree" - Each worker produces isolated branch, pushed to remote
- Coordinator report aggregates per-worker results (branch, fixes, status)
Version: 1.0.0
Last Updated: 2026-03-08
- 已完成输入分析(审计报告或目标文件/函数)
- 根据输入类型选择了合适的Worker
- 已使用worktree隔离模式()委托Worker执行任务
isolation: "worktree" - 每个Worker均生成独立分支并推送到远程仓库
- 协调器报告已汇总各Worker的结果(分支、修复数量、状态)
版本: 1.0.0
最后更新时间: 2026-03-08