press

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

/press

Press may add or strengthen tests and make tiny corrective fixes only when a test exposes a clear defect in the cooked scope.

仅当测试发现已完成（cooked）范围内的明确缺陷时，Press才会添加或强化测试，并进行微小的修正性修复。

--hard propagation

--hard 传播

/press --hard

(propagated from

/cook --hard

) is pass-through only. Press runs no gate. Hand

--hard

forward to

/age

at the handoff so it eventually reaches

/cure

, which is the only pipeline skill that fires the metacognitive vibecheck. See

skills/hard-cheese/SKILL.md

/press --hard

（从

/cook --hard

传播而来）仅做透传处理。Press不运行门禁检查。在交接时将

--hard

传递给

/age

，最终传递给

/cure

——这是唯一会触发元认知检查（metacognitive vibecheck）的流水线skill。详见

skills/hard-cheese/SKILL.md

。

Baseline-aware gates

基线感知门禁

When the cooked diff's handoff slug carries a recorded

baseline:

block, press re-runs the project's gates but does not re-flag or re-halt on failures identical to that baseline (same test, same signature) — only new or changed failures affect readiness. See

../cook/references/quality-gates.md

for the classification and policy.

当已完成变更（cooked diff）的交接标识（handoff slug）包含已记录的

baseline:

块时，Press会重新运行项目的门禁检查，但不会对与基线完全一致的失败（相同测试、相同特征）重新标记或终止——只有新出现或变更的失败会影响就绪状态。分类和策略详见

../cook/references/quality-gates.md

。

Flow

流程

Read — load the spec or acceptance criteria and the cooked diff. If
```
.cheese/glossary/<slug>.md
```
exists, read it for naming consistency when hardening tests.
Map — for each changed behaviour, find the test(s) that cover it through semantic caller search.
Gap analysis — identify weak assertions, missing boundaries, and uncovered integration seams. See
```
references/gap-analysis.md
```
for what counts as a gap and the priority order.
Add focused tests — observe red first when behaviour changes. Apply precise stale-safe edits.
Corrective fixes — only for defects the hardening tests expose. No new behaviour.
Run checks — narrowest useful tests, then relevant wider gates already in the project. When the handoff carries a
```
baseline:
```
block, classify gate failures against it per
```
../cook/references/quality-gates.md
```
: identical failures do not affect readiness; only new or changed failures do.
Report — write
```
.cheese/press/<slug>.md
```
(slug carried from
```
/cook
```
, or derived from branch/task) and print the path. Mark readiness:
```
ready for /age
```
,
```
follow-up recommended
```
, or
```
blocked
```
.
Hand off — in manual mode, prompt the next step via the shared handoff gate (see
```
## Handoff
```
below); in
```
--auto
```
mode, chain forward per
```
## Auto mode
```
.

读取 — 加载需求规格或验收标准以及已完成的变更内容。如果存在
```
.cheese/glossary/<slug>.md
```
文件，读取该文件以确保测试强化时的命名一致性。
映射 — 针对每一项变更行为，通过语义调用搜索找到覆盖该行为的测试用例。
缺口分析 — 识别弱断言、缺失的边界以及未覆盖的集成点。缺口的定义和优先级顺序详见
```
references/gap-analysis.md
```
。
添加针对性测试 — 当行为变更时，先观察测试失败情况。应用精准的防失效编辑。
修正性修复 — 仅针对强化测试暴露的缺陷进行修复。禁止添加新功能。
运行检查 — 先运行最窄范围的有用测试，再运行项目中已有的相关宽范围门禁检查。当交接内容包含
```
baseline:
```
块时，按照
```
../cook/references/quality-gates.md
```
对门禁失败进行分类：与基线一致的失败不影响就绪状态；只有新出现或变更的失败会产生影响。
报告 — 写入
```
.cheese/press/<slug>.md
```
（标识从
```
/cook
```
继承，或从分支/任务派生）并打印路径。标记就绪状态：
```
ready for /age
```
、
```
follow-up recommended
```
或
```
blocked
```
。
交接 — 在手动模式下，通过共享交接门（见下文
```
## 交接
```
）提示下一步操作；在
```
--auto
```
模式下，按照
```
## 自动模式
```
进行链式传递。

Preferred tools and fallbacks

首选工具与备选方案

Call source-code search, read, and edit backends directly according to

code-intelligence-routing.md

. For coverage and test discovery, use semantic caller search plus

tilth_deps

when available.

Portability reference:

../cheese/references/harness-portability.md

. It covers helper resolution, sub-agent dispatch, GitHub operations, and handoff transitions; prefer the bundled or repo-local helper first, and treat

${CLAUDE_SKILL_DIR}

as optional host-provided fallback. The handoff blocks below are the portable contract; slash commands are host renderings, not the control model.

Beyond source-code routing there are press-specific tools:

Need	Prefer	Fallback
Diff review	`delta`	plain `git diff`
Affected execution flows + risk scoring	semantic caller/dependency tracing and `tilth_deps`	manual flow tracing from changed files; note the precision loss

If optional tools are missing, press a narrower surface and state the residual risk.

直接根据

code-intelligence-routing.md

调用源代码搜索、读取和编辑后端。对于覆盖率和测试发现，优先使用语义调用搜索加

tilth_deps

（如果可用）。

可移植性参考：

../cheese/references/harness-portability.md

。它涵盖了助手解析、子Agent调度、GitHub操作和交接过渡；优先使用捆绑或仓库本地的助手，将

${CLAUDE_SKILL_DIR}

视为可选的宿主提供备选方案。以下交接块是可移植合约；斜杠命令是宿主渲染层，而非控制模型。

除源代码路由外，还有Press专属工具：

需求	首选工具	备选方案
变更评审	`delta`	原生 `git diff`
受影响的执行流 + 风险评分	语义调用/依赖追踪 + `tilth_deps`	从变更文件手动追踪流程；需注明精度损失

如果可选工具缺失，Press会缩小处理范围并说明剩余风险。

Output

输出

House style and citation form:

../cheese/references/formatting.md

. This section owns the press-report shape.

Write to

.cheese/press/<slug>.md

with a minimum handoff slug at the top so

/cook

's fan pathway and

/cheese --continue

can chain without re-parsing the report. The full report shape:

markdown

status: ok | halt: <one-line reason>
next: press | age | done
artifact: <path-if-any>
baseline: none | <recorded baseline block copied from the cook handoff — see ../cook/references/quality-gates.md>
<one-line orientation: what press did — e.g., "added 4 boundary tests; no defects exposed">

格式风格与引用规范：

../cheese/references/formatting.md

。本节定义了Press报告的格式。

向

.cheese/press/<slug>.md

写入内容，顶部需包含最小化交接标识，以便

/cook

的分支流程和

/cheese --continue

无需重新解析报告即可链式执行。完整报告格式如下：

markdown

status: ok | halt: <单行原因>
next: press | age | done
artifact: <路径（如有）>
baseline: none | <从cook交接中复制的已记录基线块——详见../cook/references/quality-gates.md>
<单行说明：Press执行的操作——例如，"添加4个边界测试；未发现缺陷">

Press Report — <slug>

Press报告 — <slug>

Orientation

说明

<one or two factual sentences about what press did this pass — the hardening added, the gaps closed, the readiness verdict.

/cheese --continue

surfaces the slug's orientation line to the user as "where you are", so press's orientation must describe press's own work, not duplicate cook's orientation.>

<1-2句关于本次Press执行内容的事实性描述——添加的强化措施、填补的缺口、就绪状态判定。

/cheese --continue

会向用户展示slug的说明行作为“当前进度”，因此Press的说明必须描述自身执行的工作，而非重复cook的说明。>

Checks run

已运行检查

<command>: <pass|fail|skipped with reason>

<命令>: <通过|失败|跳过（原因）>

Findings

发现

Severity	Category	Evidence	Recommendation

严重程度	类别	证据	建议

Coverage

覆盖率

Spec coverage:
Boundary coverage:
Assertion strength:

需求规格覆盖率:
边界覆盖率:
断言强度:

Readiness

就绪状态

Next step

下一步

<ready for /age>: /age <slug> — review the cooked + pressed diff <follow-up recommended>: /age <slug> — review-safe; documented follow-ups addressed after review <blocked>: resolve blocking issues before proceeding


`status: ok` maps to readiness `ready for /age` or `follow-up recommended`; `status: halt: <reason>` maps to `blocked`. `next:` names the next runnable phase: `age` when review-safe, `press` when blocking issues must be resolved and the hardening phase rerun. Use `next: done` only for true terminal completion, not for a blocked-but-resumable halt. `/ultracook` still stops automatically on any `status: halt`; `next:` is the resume hint for `/cheese --continue`.

When `baseline:` is present, press honors it: identical recorded failures never move readiness off `ready for /age`; only new or changed failures do, per [`../cook/references/quality-gates.md`](../cook/references/quality-gates.md).

Then print:

Press report: .cheese/press/<slug>.md Next step: /age <slug> (when ready for /age or follow-up recommended) blocked — resolve before continuing (when blocked)

undefined

<ready for /age>: /age <slug> — 评审已完成+已强化的变更内容 <follow-up recommended>: /age <slug> — 可安全评审；已记录的后续事项在评审后处理 <blocked>: 解决阻塞问题后再继续


`status: ok`对应就绪状态`ready for /age`或`follow-up recommended`；`status: halt: <reason>`对应`blocked`。`next:`指定下一个可运行阶段：当可安全评审时为`age`；当必须解决阻塞问题并重新运行强化阶段时为`press`。仅当真正完成终端流程时使用`next: done`，而非阻塞但可恢复的终止。`/ultracook`仍会在任何`status: halt`时自动停止；`next:`是`/cheese --continue`的恢复提示。

当存在`baseline:`时，Press会遵循规则：与已记录的基线完全一致的失败绝不会使就绪状态偏离`ready for /age`；只有新出现或变更的失败会产生影响，详见[`../cook/references/quality-gates.md`](../cook/references/quality-gates.md)。

然后打印：

Press report: .cheese/press/<slug>.md Next step: /age <slug> (当状态为ready for /age或follow-up recommended时) blocked — resolve before continuing (当状态为blocked时)

undefined

Handoff

交接

Pipeline: culture → mold → cook → [press] → age → cure → plate

After the press report is on disk, ask via the shared handoff gate in

../cheese/references/handoff-gate.md

, following its Standard forward-step menu. Lead each option with the verb (what the user wants to do next); the skill command (with any in-scope

--hard

propagation) is the backing detail. Default options:

Review the diff (recommended when readiness is
ready for /age
or
follow-up recommended
) —
```
/age <slug>
```
. For
```
follow-up recommended
```
, documented follow-ups can be addressed after review.
Plate it —
```
/age <slug> --auto --open-pr
```
: run age → cure, then
```
/plate
```
resolves topology and publishes.
Checkpoint & stop —
```
/wheypoint
```
: write a resumable handoff and pause.
Stop — dispatch none; defer review (use this if you want to harden manually before /age, even though the contract is review-safe).

Pre-select Review the diff when ready. If blocked, do not pre-select Plate it. Run a non-stop selection immediately.

流水线： culture → mold → cook → [press] → age → cure → plate

Press报告写入磁盘后，通过

../cheese/references/handoff-gate.md

中的共享交接门询问用户，遵循其标准前进步骤菜单。每个选项以动词开头（用户接下来想要执行的操作）；skill命令（包含任何范围内的

--hard

传播）为后台细节。默认选项：

评审变更内容 (当就绪状态为
ready for /age
或
follow-up recommended
时推荐) —
```
/age <slug>
```
。对于
```
follow-up recommended
```
状态，已记录的后续事项可在评审后处理。
发布 —
```
/age <slug> --auto --open-pr
```
: 运行age → cure，然后
```
/plate
```
解析拓扑结构并发布。
检查点并停止 —
```
/wheypoint
```
: 写入可恢复的交接内容并暂停。
停止 — 不触发任何操作；延迟评审（即使合约标明可安全评审，若你希望在
```
/age
```
前手动强化测试，可使用此选项）。

当就绪时默认选中评审变更内容。若处于阻塞状态，不默认选中发布。立即执行非停止选项。

Auto mode

自动模式

When invoked with

--auto

(propagated from

/cook --auto

Skip the handoff gate entirely.
If readiness is
```
ready for /age
```
or
```
follow-up recommended
```
, invoke
```
/age <slug> --auto
```
directly (forward
```
--open-pr
```
when it is in scope).
If readiness is
```
blocked
```
, stop the auto chain and surface the press report to the user. Blocked criteria: defined once in
```
references/gap-analysis.md
```
.

当通过

--auto

调用（从

/cook --auto

传播而来）时：

完全跳过交接门。
若就绪状态为
```
ready for /age
```
或
```
follow-up recommended
```
，直接调用
```
/age <slug> --auto
```
（当范围内存在
```
--open-pr
```
时向前传递）。
若就绪状态为
```
blocked
```
，停止自动链式流程并向用户展示Press报告。阻塞标准在
```
references/gap-analysis.md
```
中定义。

Within cook's own fan pathway

在cook自身的分支流程中

When

/cook

's fan pathway (its retired-

/ultracook

mechanics, now self-hosted — see

skills/cook/SKILL.md

## Fan pathway

) spawns press as a fresh-context sub-agent, it owns the chain itself. When the spawn prompt explicitly says "for THIS PHASE ONLY" and "do not chain forward to the next phase," honour the override: write

.cheese/press/<slug>.md

(with the handoff slug at the top) and stop. Do not invoke

/age <slug> --auto

from inside the sub-agent regardless of readiness. The orchestrator reads the handoff slug and either chains to age (when

status: ok

and

next: age

) or halts (when

status: halt

, regardless of

next:

next:

remains the resume hint for

/cheese --continue

当

/cook

的分支流程（其已废弃的

/ultracook

机制，现为自托管——详见

skills/cook/SKILL.md

中的

## 分支流程

）将Press作为新上下文子Agent启动时，它拥有流程控制权。当启动提示明确说明“仅针对此阶段”且“不要链式传递到下一阶段”时，需遵守此覆盖规则：写入

.cheese/press/<slug>.md

（顶部包含交接标识）并停止。无论就绪状态如何，都不要从子Agent内部调用

/age <slug> --auto

。编排器会读取交接标识，要么链式传递到age（当

status: ok

且

next: age

时），要么终止（当

status: halt

时，无论

next:

是什么）。

next:

仍是

/cheese --continue

的恢复提示。

Rules

规则

Do not weaken assertions.
Do not broaden implementation beyond the cooked contract.
Every changed behaviour in the cooked diff leaves press with an executable hardening test that would fail if the change regressed. If press cannot produce a stable hardening test for a changed behaviour (flaky seam, missing infrastructure, design decision required), readiness is
```
blocked
```
— never
```
ready for /age
```
or
```
follow-up recommended
```
.
Cap iteration at three attempts per gap. Count test-edit + run cycles. On the third failed cycle on the same gap, mark readiness
```
blocked
```
with reason
```
spinning: <gap-description>
```
and surface the report. Do not loop indefinitely.
Surface medium and high findings explicitly; summarize low findings.
If the cooked diff or spec rests on a false premise (the contract is wrong, or the test surface is solving the wrong problem), stop and surface the premise before adding tests; do not harden the wrong angle.
Apply the shared voice kernel (lives at
```
../age/references/voice.md
```
): lead the press report with the readiness verdict, flag residual risk as
```
certain | speculating | don't know
```
, agree when coverage is already sufficient without manufacturing tests.

不得弱化断言。
不得超出已完成合约的范围扩展实现。
已完成变更中的每一项行为变更，在Press处理后都必须有可执行的强化测试——如果变更回归，该测试会失败。 如果Press无法为某项行为变更生成稳定的强化测试（如不稳定的集成点、缺失的基础设施、需要设计决策），则就绪状态为
```
blocked
```
——绝不能是
```
ready for /age
```
或
```
follow-up recommended
```
。
每个缺口的迭代次数上限为3次。 统计测试编辑+运行周期。同一缺口第三次尝试失败时，将就绪状态标记为
```
blocked
```
，原因填写
```
spinning: <缺口描述>
```
并展示报告。不得无限循环。
明确展示中等和高严重程度的发现；总结低严重程度的发现。
如果已完成的变更或需求规格基于错误前提（合约错误，或测试面解决的是错误问题），需停止并先指出该前提，再添加测试；不得针对错误方向进行强化。
应用共享语音内核（位于
```
../age/references/voice.md
```
）：Press报告开头需展示就绪状态判定，将剩余风险标记为
```
certain | speculating | don't know
```
，当覆盖率已足够时需认可现状，不得凭空生成测试。