Repository navigation
docs(agents): require an eval before a skill change ships - #331
Merged
Merged
Conversation
A diet of nine skills cut their size but proved only that links and routes held, not that the skills still did the same work. The user set the gate: a skill or playbook change is pushed only with a before/after eval showing no quality loss, and stays on a local branch until then.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Nine skills were cut down in one pass. Links and routes still held, but nothing showed that the skills still did the same work. The diets were reverted, and this PR writes down the rule that should have stopped them from reaching a commit.
What changed
AGENTS.md, Hard rules, one new entry: a change to a skill or playbook is pushed only with a before/after eval showing no quality loss (skill-diet/references/eval.mdfor model-invoked skills,yuu-mode/playbooks/eval.mdfor user-invoked skills and playbooks). Until then it stays on a local branch. A change no eval covers, such as a description's triggering, stays there too unless the user waives the eval for it. The commit message carries the pass rates per version.Evidence
Not verified: this is an instruction, and no check can run it. The first change shipped under it is the
test-auditPR, whose commit carries its eval results.Risk: low, docs only.
AGENTS.mdis a sensitive path, since every session in this repo loads it.ELI5
Before a skill change goes into the repo, someone has to show that the agent works at least as well with the new text as with the old one.