跳到正文
cccskills
免费在 GitHub 公开

correct

Find recurring agent mistakes in a repository and prevent them through architecture, types, automated checks, or tests. Verify each safeguard against a real past mistake, and record how each rule is enforced in the agent instructions.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

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.

实测评分 未实测

查看安装方法

适用场景

  • Prevent repeated mistakes found in reviews
  • Replace duplicated definitions with one source of truth
  • Enforce coding rules with types and automated checks
  • Verify safeguards against real past mistakes

包含的文件(1)

  • SKILL.md2.4 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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 still passes when the behavior it checks breaks, or that fails when only the internals change.
  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.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

architect

免费

Plan types, function inputs and outputs, and module boundaries before implementation. Compare structurally different designs from multiple AI models, document the chosen approach, and guide coding while tracking changes to the agreed design.

中文简介正在准备中。当前显示英语简介。

  • Designing a complex feature before coding
  • Comparing alternative module structures
  • Keeping implementation aligned with design decisions
michael-denyer/pstack-claude33722026年10月23日 更新

arena

免费

Generate several candidate solutions in parallel, compare them against concrete criteria, and choose a base. Combine useful parts from other candidates, then verify the final artifact and document why each major choice was made.

中文简介正在准备中。当前显示英语简介。

  • Compare multiple designs before choosing a direction
  • Explore different implementations of the same task
  • Combine useful elements from competing drafts
michael-denyer/pstack-claude33722026年10月23日 更新

Turn recurring work habits and communication preferences into a personal agent skill. It combines evidence from workspace conversations with direct questions, then drafts or updates instructions for how agents should work with you.

中文简介正在准备中。当前显示英语简介。

  • Capture preferred response length and tone
  • Document testing and review expectations
  • Update personal instructions as work habits change
michael-denyer/pstack-claude33722026年10月23日 更新

babysit

免费

Monitor an open pull request, fix failing automated checks and merge conflicts, and address straightforward review feedback. Recheck after updates, report the resulting status, and hand decisions requiring design judgment back to the user.

中文简介正在准备中。当前显示英语简介。

  • Following up on an open PR without repeated prompts
  • Fixing failed automated checks and rechecking results
  • Addressing straightforward review comments
michael-denyer/pstack-claude33722026年10月23日 更新

Checks whether performance measurements support a speedup, slowdown, or technology choice. It examines bottlenecks, production settings, errors, repeatability, and completed work, then guides reporting with run counts, ranges, and a clear verdict.

中文简介正在准备中。当前显示英语简介。

  • Checking before-and-after performance claims in a PR
  • Comparing libraries or configurations fairly
  • Investigating suspicious benchmark results
michael-denyer/pstack-claude33722026年10月23日 更新

Investigate what a code change could break beyond the edited files. Trace downstream effects, identify the key assumption behind its safety, and test that assumption with real code while clearly reporting unresolved risks.

中文简介正在准备中。当前显示英语简介。

  • Checking the wider impact of a small code change
  • Verifying assumptions about existing code before design
  • Testing the safety assumption before merging a change
michael-denyer/pstack-claude33722026年10月23日 更新

查看 michael-denyer 的全部技能

报告此技能的问题