dynamo-repair
Skill1 starsChanged 35 days agoNo licenceView on GitHub
Repair a failing automated review on a Dynamo task repository, then harden the rules so the same class cannot recur, and write the class back to the global corpus at ~/.claude/skills/dynamo/knowledge so every other task inherits the lesson. Use this whenever a CI static check, a PR bot comment, an AVA or deep-review gate, or a Per-Check QC item reports FAIL, BLOCK or a red X on a task, for example allow_internet, instruction_concision, no_extraneous_files, undisclosed thresholds, reward plumbing exploits or verifier coverage. Trigger it when the user pastes a screenshot or table of check results, says "fix it" about a failed check, or asks why a submission was rejected. Reach for it even when the fix looks like a one-line edit, because the one-line edit is usually only half the repair.
In this repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- board-reconcileSkill
- change-scoperSkill
- codebase-cartographerSkill
- commit-conventionsSkill
- debuggerSkill
- dynamo-bootstrapSkill
- dynamo-bootstrapSkill
- dynamo-designSkill
- dynamo-designSkill
- dynamo-probeSkill
- dynamo-probeSkill
- dynamo-rebuildSkill
- dynamo-rebuildSkill
- dynamo-repairSkill
- dynamo-reworkSkill
- dynamo-submissionSkill
- dynamo-submissionSkill
- dynamo-verifySkill
- dynamo-verifySkill
- feature-grafterSkill
- feature-integratorSkill
- grillingSkill
- intake-triageSkill
- phase-executorSkill
- pr-descriptionSkill
- product-architectSkill
- product-guideSkill
- product-state-initSkill
- quality-gateSkill
- refactor-stewardSkill
- regression-guardSkill
- root-cause-investigatorSkill
- safety-net-builderSkill
- surgical-fixerSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.