Back to Details

review-debt

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Review Tech Debt (internal)

审查技术债务（内部）

Composed by 
review-change
/ 
product-audit
within their conversation — on any agent, follow this file inline as the routed step. Findings only; never edits, never refactors.
由对话中的
review-change
/ 
product-audit
组合而成——针对任何agent，需按此文件作为路由步骤执行。仅输出发现结果；绝不编辑、重构代码。

Scope

范围

The caller's synthesized findings table (the fused, classified decision table). This pass does not rescan the diff: debt-shaped findings are already in the table, and every ownership decision already happened in the finder axes (
review-code
, 
review-verify
, …). State the scope — the change the table was synthesized over — at the top of the returned table.
调用方的合成发现表格（融合后的分类决策表）。此流程不会重新扫描差异：类债务的发现已存在于表格中，所有归属决策已在发现者维度（
review-code
、
review-verify
等）完成。需在返回表格顶部说明范围——即表格所基于的变更内容。

Transform (evaluate EVERY row — none is optional; n/a must be stated)

转换规则（需评估每一行——无例外；不适用项必须明确标注）

Turn the table's tech-debt-shaped rows (TODO/FIXME/HACK, duplication, stale or orphaned abstractions, dead code, complexity hotspots, missing tests, workarounds pinned to upstream fixes) into explicit, payable debt items:
✓ Restate each debt-shaped finding at 
file:line
with what it defers ✓ Attribute it to the axis already recorded in the table — never re-litigate ownership ✓ Confirm every debt item carries a TRIGGER: the condition under which it must be paid (e.g. "3rd consumer appears", ">100k rows") — a debt item without a trigger is itself a finding ✓ Verify no current-unit debt was mislabeled non-blocking: current-unit work cannot be 
postpone
/
tradeoff
/
wontfix
— a table showing one is flagged back to the classifier, never reclassified here ✓ Honor the dead-code exception: staged/planned code cross-checked against the roadmap/SPEC/TASKS is not dead code — mark verify when unsure, never assert
将表格中类债务的行（TODO/FIXME/HACK、重复代码、过时或孤立的抽象、死代码、复杂度热点、缺失测试、依赖上游修复的临时方案）转换为明确的可处理债务项：
✓ 按
file:line
重述每个类债务发现，并说明其延迟处理的内容 ✓ 将其归属到表格中已记录的维度——绝不重新讨论归属权 ✓ 确认每个债务项都带有TRIGGER（触发条件）：即必须处理该债务的条件（例如“出现第3个使用者”、“>10万行数据”）——无触发条件的债务项本身即为一项发现 ✓ 验证当前单元的债务未被错误标记为非阻塞：当前单元的工作不能标记为
postpone
/
tradeoff
/
wontfix
——若表格中存在此类情况，需标记后返回给分类器，不得在此处重新分类 ✓ 遵守死代码例外规则：与roadmap/SPEC/TASKS交叉核对后的已排期/规划代码不属于死代码——不确定时标记verify，不得随意断言

Return exactly

返回格式要求

REVIEW TECH DEBT — scope: <scope>

| # | Finding | Sev | Evidence | Suggested fix |
|---|---------|-----|----------|---------------|
| 1 | <what>  | critical|major|minor | <file:line> | <trigger + smallest action> |

Rows: <n> transformed, <n> with trigger, <n> findings, <n> n/a (<which + why>)
Summary: <1-2 sentences>
Decision: PASS | FAIL
For this pass, the Suggested fix column carries the TRIGGER — the condition under which the debt must be paid — alongside the smallest action.
FAIL if any critical or major finding is open; PASS otherwise. Minor findings never block — they surface in the caller's report as debt notes.
REVIEW TECH DEBT — scope: <scope>

| # | Finding | Sev | Evidence | Suggested fix |
|---|---------|-----|----------|---------------|
| 1 | <what>  | critical|major|minor | <file:line> | <trigger + smallest action> |

Rows: <n> transformed, <n> with trigger, <n> findings, <n> n/a (<which + why>)
Summary: <1-2 sentences>
Decision: PASS | FAIL
在此流程中，“Suggested fix”列需同时包含TRIGGER（即必须处理债务的条件）以及最小执行动作。
若存在未处理的严重（critical）或主要（major）发现，返回FAIL；否则返回PASS。次要（minor）发现不会阻塞流程——它们会作为债务说明出现在调用方的报告中。

Done when

完成标准

  • Every debt-shaped row of the synthesized table was transformed with evidence (
    file:line
    ) or explicitly marked n/a with the reason.
  • Every debt item carries a trigger; no current-unit debt was mislabeled.
  • The fixed-format block above is returned — nothing more, nothing less — and no code was changed.
  • 合成表格中的每一行类债务内容均已转换并附上证据（
    file:line
    ），或明确标注不适用及原因。
  • 每个债务项均带有触发条件；当前单元的债务未被错误标记。
  • 返回上述固定格式内容——不多不少，且未修改任何代码。