Correct

作者 backnotprop3a604672c46c无许可证1.3K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库今天更新

Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.

AI 生成的概览

把仓库中反复出现的智能体错误转化为架构、类型、lint 或测试层面的防护,防止再次发生。

功能
该技能引导智能体查看近期提交、回滚、评审意见和指令文件,把反复出现的错误归类。针对每一类,它按有效性从高到低依次采用架构、类型、lint 或 CI 检查、测试,最后才是文档。产出包括每个修复一个提交、每个新检查在真实历史错误上失败的证明,以及把每条规则与其执行方式配对的规则表。
适用场景
当操作者因同样的错误反复纠正智能体时使用。适用于多次纠正之后,需要持久预防性改动而非又一次临时修复的场景。
运行要求
仅含指令,不含脚本。需要访问仓库历史、评审意见和智能体指令文件,并能运行本地与 CI 命令。

Correct

The operator keeps correcting agents in this repo for the same mistakes. Change the repo so the next agent can't make them.

Assume every contributor is an agent that sees only the files it opened, copies the nearest example, and takes the shortest path that compiles. Design the repo so a change that looks right from one file is right for the whole repo.

Find the mistake classes

First, read recent commits, reverts, review comments, agent instruction files, and comments that explain workarounds. Group the mistakes into classes. A class counts once it has happened twice.

Fix each class at the highest level that works

  1. Eliminate it with architecture. Give each piece of state one owner and each task one supported way. Hide internals so the wrong import fails. Replace hand-synced lists with one source of truth. Delete old ways and dead code an agent would copy.
  2. Enforce it with types so the bad state can't be written. If bad code still compiles, add a lint or CI check whose error names the file, type, or function to use instead. If the pattern is already common, fail only when a change adds more.
  3. Test the behavior. Fix or delete any test that would still pass if every function it calls returned nothing.
  4. Write docs or agent rules last, only for judgment calls. Nothing fails when an agent skips them.

Fix and prove

Then fix the most frequent classes now, one commit each. Prove each new check fails on a real past mistake. Run the same command locally and in CI. Exceptions go on the offending line with a reason, an expiry date, and a human's approval.

Keep the rule table

Last, keep a table in the agent instruction file that pairs each rule with what enforces it. When the operator corrects you, fix the mistake and add the rule. If the rule was already there and nothing enforces it, that's a repeat, so fix it at the highest level in the same change. Drop a rule once its mistake can't happen.

Reply: each class with its evidence, the level you picked, and why a higher level didn't work.

来源与署名

来源:backnotprop/pstack位于skills/correct提交3a60467

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架