receiving-thermo-review 指南

这个 skill 做什么

Use this skill after a thermo report or equivalent structural review feedback. It builds a disposition ledger for every finding, decomposition gap, recursive coverage row, line-count threshold item, candidate sweep entry, and blind spot before changing code, adds a behavior-parity ledger for touched user-visible or unknown-impact surfaces, then fixes only verified structural issues while preserving Git staging and avoiding unapproved architecture refactors.

什么时候使用

01Verifying harsh structural findings against the current diff, line counts, call sites, and ownership boundaries.
02Resolving 350-line threshold concerns, decomposition gaps, recursive coverage gaps, and candidate sweep items.
03Applying scoped behavior-preserving simplifications while checking source, guard, output, and extension-point parity.

如何工作

01
Read the full report and confirm scope, baseline, completion status, and current checkout still match.
02
Create a disposition ledger from findings, decomposition gaps, recursive coverage rows, line-count rows, sweep rows, and blind spots.
03
Resolve report inconsistencies or stale line counts before editing.
04
Present a structural change plan with behavior-parity, ownership, verification, and no-staging notes before changing code.
05
Fix or disprove Blocker and Major items first, then decide Minor, Question, decomposition, and coverage items.
06
Recompute affected line counts and run targeted verification for every touched surface.

你会得到什么

01A full disposition ledger for every consumed thermo report item.
02Scoped structural fixes or evidence-backed challenges, waivers, and carry-forward decisions.
03Updated line-count, coverage, and behavior-parity status for affected surfaces.

重要边界

01Do not blindly apply thermo review feedback.
02Do not start broad architecture refactors without approved scope.
03Do not hide potential user-visible regressions behind structural cleanup.
04Do not stage changes unless the current request explicitly asks for staging, committing, or PR publication.
05Do not claim the thermo gate is resolved until every finding, decomposition gap, threshold item, and open coverage row is accounted for.

值得打开的文件

Workflowskills/receiving-thermo-review/SKILL.mdDisposition ledger, structural response rules, and Git staging guardrails.Runtime metadataskills/receiving-thermo-review/agents/openai.yamlOptional agent runtime metadata for this skill.

上一个 skillthermo-reviewWrite harsh structural quality reports.下一个 skillreceiving-code-review消费 code-review 报告，并在改代码前验证每个条目。

这个 skill 做什么

什么时候使用

01Verifying harsh structural findings against the current diff, line counts, call sites, and ownership boundaries.
02Resolving 350-line threshold concerns, decomposition gaps, recursive coverage gaps, and candidate sweep items.
03Applying scoped behavior-preserving simplifications while checking source, guard, output, and extension-point parity.

如何工作

01
Read the full report and confirm scope, baseline, completion status, and current checkout still match.
02
Create a disposition ledger from findings, decomposition gaps, recursive coverage rows, line-count rows, sweep rows, and blind spots.
03
Resolve report inconsistencies or stale line counts before editing.
04
Present a structural change plan with behavior-parity, ownership, verification, and no-staging notes before changing code.
05
Fix or disprove Blocker and Major items first, then decide Minor, Question, decomposition, and coverage items.
06
Recompute affected line counts and run targeted verification for every touched surface.

重要边界

01Do not blindly apply thermo review feedback.
02Do not start broad architecture refactors without approved scope.
03Do not hide potential user-visible regressions behind structural cleanup.
04Do not stage changes unless the current request explicitly asks for staging, committing, or PR publication.
05Do not claim the thermo gate is resolved until every finding, decomposition gap, threshold item, and open coverage row is accounted for.