test-first-changes
Skill259 starsChanged 35 days agoApache-2.0View on GitHub
Test-first procedure for every behaviour change in Noodle. Use before fixing a bug, changing how code behaves, or acting on a diagnosis made by reading the code; covers the failing test, the fix, the two runs to report, and the CI-safety constraints on tests.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- Applet/AGENTS.mdAGENTS.md
- Browser/AGENTS.mdAGENTS.md
- Computer/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- Hub/AGENTS.mdAGENTS.md
- Incubator/AGENTS.mdAGENTS.md
- Mobile/AGENTS.mdAGENTS.md
- Terminal/AGENTS.mdAGENTS.md
- Tools/AGENTS.mdAGENTS.md
- agents-md-symlinkSkill
- apple-history-utilitiesSkill
- helper-visibilitySkill
- mint-releaseSkill
- no-code-docsSkill
- sheet-and-settings-sizingSkill
- ui-copySkill
- version-bound-cleanupSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Do not change behaviour on the strength of reading the code.
- Distinctive: line 10
Write a test that exercises the specific code and fails because of the problem.
- Distinctive: line 11
Run it and see it fail.
- Distinctive: line 13
Run the same test and see it pass.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Behaviour changes are test-first
Do not change behaviour on the strength of reading the code.
- Write a test that exercises the specific code and fails because of the problem.
- Run it and see it fail.
- Make the change.
- Run the same test and see it pass.
- Report both runs.
A suspected cause that no test can reproduce is still a hypothesis; say so instead of changing code.
Tests must not depend on a harness account, a model, the network or timing, so that they also pass in CI.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.