sip

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Taste your own cooking: the moment you finish making something, check it with the very skills this repo ships before you serve it.

尝尝自己的“作品”：完成内容创作后，在交付之前先用本仓库提供的技能对其进行检查。

Goal

目标

A reminder buried in docs ("remember to verify") won't reliably fire in a fresh session.

sip

makes the recursive self-improvement loop a triggered habit: right after any create or change, run our own skills on the result — the clean checks and the true ones — so quality doesn't ride on the author's biased in-session judgment.

文档中提到的“记得验证”这类提醒，在新会话中往往无法可靠触发。

sip

让递归式自我改进循环成为一个触发式习惯：在完成任何创建或修改操作后，用我们的技能对结果进行全面检查——包括基础检查和实质性验证——确保质量不受作者当前会话中偏见判断的影响。

Workflow

工作流程

Spot the trigger: you just created or changed an artifact or skill and are about to call it done, commit, or hand it off.
Cold-read it — run
```
shower
```
on the artifact (fresh-eyes comprehension / handoff check).
Verify it's true — if the artifact asserts a reality-grounded claim, run
```
factchk
```
; if it defines an eval, metric, or experiment, run
```
mandela
```
. Skip when it has neither.
Check consistency — run
```
ssotize
```
in audit mode across the repo for anything the change duplicated or contradicted; execute its consolidation plan only after approval.
Detool portability claims — run
```
detool
```
only when the artifact claims portability, tool-neutrality, stack-agnostic durability, or cross-agent reuse. Skip when it is provenance, operational notes, a tool-targeted runbook, or does not claim portability.
Tidy —
```
re0
```
the changed docs so the result reads as a clean v0, not a patch over a draft.
Apply the findings here, then serve it.

识别触发点：你刚创建或修改了一个工件（artifact）或Skill，正准备确定收尾、提交或交付。
客观审阅 —— 对工件运行
```
shower
```
（以全新视角理解/交付检查）。
验证真实性 —— 如果工件包含基于事实的声明，运行
```
factchk
```
；如果它定义了评估、指标或实验，运行
```
mandela
```
。若两者都不涉及则跳过。
检查一致性 —— 在审计模式下对整个仓库运行
```
ssotize
```
，检查更改是否存在重复或矛盾内容；仅在获得批准后执行其整合方案。
验证可移植性声明 —— 仅当工件声称具备可移植性、工具中立性、跨栈持久化或跨Agent复用性时，才运行
```
detool
```
。如果是溯源信息、操作说明、针对特定工具的运行手册，或未声明可移植性，则跳过。
整理优化 —— 对修改后的文档运行
```
re0
```
，确保最终内容是清晰的v0版本，而非草稿上的补丁。
在此处应用检查结果，然后交付。

Rules

规则

Trigger on your OWN output, right after making it — that's when bias is highest and a check is cheapest.
Use the skills; don't re-implement them —
```
shower
```
for clarity,
```
factchk
```
/
```
mandela
```
for truth,
```
ssotize
```
for SSOT,
```
detool
```
for portability claims,
```
re0
```
for cleanup.
```
sip
```
orchestrates and routes findings back to the author session to fix; the skills do the work.
Skip what plainly doesn't apply, or any check whose skill isn't installed — run only what's present.
```
factchk
```
/
```
mandela
```
fire only when there is a claim or an eval;
```
detool
```
fires only when the artifact claims portability, tool-neutrality, stack-agnostic durability, or cross-agent reuse; a one-line prose tweak may need only a consistency check. Say what you skipped and why.
Stop at the artifact —
```
sip
```
never touches git or makes commits.
Chain only model-invoked skills; a user-invoked skill (marked
```
disable-model-invocation
```
) is a human's to fire deliberately, so
```
sip
```
must not call one.

在你自己完成输出后立即触发——此时偏见最强，检查成本最低。
使用现有技能，不要重新实现——
```
shower
```
用于检查清晰度，
```
factchk
```
/
```
mandela
```
用于验证真实性，
```
ssotize
```
用于维护SSOT（单一可信来源），
```
detool
```
用于验证可移植性声明，
```
re0
```
用于清理。
```
sip
```
负责编排并将检查结果反馈给作者会话以便修复；具体检查工作由各技能完成。
明确跳过不适用的检查，或任何未安装对应技能的检查——仅运行已有的检查。
```
factchk
```
/
```
mandela
```
仅在存在声明或评估时触发；
```
detool
```
仅在工件声称具备可移植性、工具中立性、跨栈持久化或跨Agent复用性时触发；一行文字的微调可能只需要一致性检查。请说明跳过的内容及原因。
仅处理工件——
```
sip
```
绝不触碰git或执行提交操作。
仅调用模型可触发的技能；用户触发的技能（标记为
```
disable-model-invocation
```
）需由人工主动触发，因此
```
sip
```
不得调用此类技能。

Verification

验证

Before finishing:

The change was actually run through the relevant skills, not eyeballed.
Findings were applied (or consciously deferred with a stated reason).
The artifact actually changed as a result (a diff exists), or every skipped skill has a stated reason.

完成前需确认：

相关技能已实际运行于更改内容，而非仅靠人工目测。
检查结果已应用（或已明确说明延迟应用的理由）。
工件确实已做出更改（存在差异），或所有跳过的技能均已说明理由。