Back to Details

minimal-fix

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Minimal Fix Skill

最小化修复Skill

You fix one specific problem with the smallest diff that could work.

你需要用最小的代码差异来修复一个特定问题。

Inputs

输入信息

Exact failure message, reviewer comment, or issue description
File(s) implicated (if known)
Project build/test commands (from AGENTS.md or project skills)
Path denylist (from loop safety policy — never edit
```
.env
```
,
```
auth/
```
,
```
payments/
```
, secrets)

确切的失败信息、评审意见或问题描述
涉及的文件（若已知）
项目构建/测试命令（来自AGENTS.md或项目skills）
路径黑名单（来自循环安全策略——切勿编辑
```
.env
```
、
```
auth/
```
、
```
payments/
```
、机密文件）

Process

处理流程

Reproduce or confirm the failure locally if possible.
Identify the minimal root cause — not symptoms in distant files.
Change only what is required. No drive-by refactors.
Run tests/lint relevant to the change.
Summarize: what changed, why, what you ran.

尽可能在本地重现或确认失败情况。
确定最小化根本原因——而非远程文件中的症状。
仅修改必要内容。禁止顺带重构。
运行与变更相关的测试/代码检查。
总结：变更内容、原因以及执行的操作。

Output

输出格式

markdown

undefined

markdown

undefined

Minimal Fix Proposal

最小化修复提案

Target

目标

(one sentence)

(一句话描述)

Diff summary

差异摘要

(files + what changed)

(文件+变更内容)

Verification run

验证运行

(command + result)

(命令+结果)

Risks / human review needed?

风险/是否需要人工评审?

(yes/no + why)

undefined

(是/否 + 原因)

undefined

Rules

规则

One problem per invocation. Multiple failures → escalate or triage first.
Respect denylist paths — escalate instead of editing.
Prefer worktree isolation when the loop runs unattended.
Do not mark your own work done — the verifier decides.

每次调用仅处理一个问题。若存在多个失败情况，先上报或分类处理。
遵守路径黑名单——如需修改则上报，而非直接编辑。
当循环无人值守运行时，优先使用工作树隔离。
切勿自行标记工作完成——由验证者决定。