pi-result-handling

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Pi Result Handling

Pi结果处理

When the helper returns Pi output:

Preserve the helper's verdict, summary, findings, and next steps structure.
For review output, present findings first and keep them ordered by severity.
Use the file paths and line numbers exactly as the helper reports them.
Preserve evidence boundaries. If Pi marked something as an inference, uncertainty, or follow-up question, keep that distinction.
Preserve output sections when the prompt asked for them, such as observed facts, inferences, open questions, touched files, or next steps.
If there are no findings, say that explicitly and keep the residual-risk note brief.
If Pi made edits, say so explicitly and list the touched files when the helper provides them.
For
```
pi:pi-rescue
```
, do not turn a failed or incomplete Pi run into a Claude-side implementation attempt. Report the failure and stop.
For
```
pi:pi-rescue
```
, if Pi was never successfully invoked, do not generate a substitute answer at all.
CRITICAL: After presenting review findings, STOP. Do not make any code changes. Do not fix any issues. You MUST explicitly ask the user which issues, if any, they want fixed before touching a single file. Auto-applying fixes from a review is strictly forbidden, even if the fix is obvious.
If the helper reports malformed output or a failed Pi run, include the most actionable stderr lines and stop there instead of guessing.
If the helper reports that setup is required (pi binary missing, no provider configured), direct the user to
```
/pi:setup
```
and do not improvise alternate flows.

当helper返回Pi输出时：

保留helper的结论、摘要、发现结果和后续步骤结构。
对于评审输出，先展示发现结果，并按严重程度排序。
严格使用helper报告的文件路径和行号。
保留证据边界。如果Pi将某内容标记为推断、不确定或跟进问题，需保留该区分。
当提示要求特定输出部分时，保留这些部分，例如已观察事实、推断内容、未解决问题、涉及文件或后续步骤。
如果没有发现结果，需明确说明，并简要保留剩余风险提示。
如果Pi进行了编辑，需明确说明，并在helper提供相关信息时列出涉及的文件。
对于
```
pi:pi-rescue
```
，不要将Pi的失败或不完整运行转换为Claude端的实现尝试。只需报告失败并停止操作。
对于
```
pi:pi-rescue
```
，如果Pi从未成功调用，则完全不要生成替代答案。
重要提示：展示评审发现结果后，立即停止操作。不得进行任何代码修改，不得修复任何问题。在修改任何文件之前，必须明确询问用户希望修复哪些问题（如果有的话）。严格禁止自动应用评审得出的修复方案，即使修复方案看似显而易见。
如果helper报告输出格式错误或Pi运行失败，需包含最具可操作性的stderr行，然后停止操作，不要猜测。
如果helper报告需要进行设置（缺少pi二进制文件、未配置提供者），引导用户前往
```
/pi:setup
```
，不要自行设计替代流程。