correct

Files (1)

• SKILL.md

SKILL.md (first lines)

# 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.

## Permissions and capabilities

Use the available repository read, history, write and execution tools under the [session capability contract](../../references/host-capabilities.md). Declare missing history, review comments or CI access. A correction does not authorize edits outside the agreed repository scope.

Before changing durable skills or agent instruction files, present the proposed edit for review and obtain explicit permission. Preserve this gate when updating the rule table. Commits need user authorization, and external actions need their own explicit authorization. If writes or execution are unavailable or unauthorized, report the evidence and proposed enforcement as reduced capability. Do not claim edits, checks or CI results you did not observe. If repository evidence is unavailable, state the block and request the relevant evidence.

## 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 within authorized scope, one commit each when commits are authorized. 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.

From yabasha/pstack-openai, MIT.

More from yabasha/pstack-openai