ears-gap-fix
Skill1 starsChanged 5 months agoNo licenceView on GitHub
Third-pass gap closer for an EARS specification file produced by /springboot-to-ears. Given just the EARS file, reads the controller path(s) from the file's own `Source Controller(s)` header, re-walks the controller's full call chain, and finds anything that exists in the source code but is MISSING from the EARS file — business rules AND data-model elements (entity properties, enum states). It writes a reviewable GAP REPORT and — only after the user approves — applies fixes: unambiguous rules become code-free EARS statements in the right module; a missing entity/property or enum-state becomes a new or extended `### <Name>` block in Domain Entities / Domain Concepts (plus any rule-bearing fields as statements); ambiguous ones become [NEEDS REVIEW] Open Questions in the resolve-open-questions footer format. Each `## Module:` and content `### Subsection` carries a `> **Source files:**` annotation (springboot-to-ears Rule 14) which this skill reads, uses as a supplemental locate hint, preserves, and keeps accurate; it also refreshes the Extraction Summary including its rule-site coverage rows and per-file ledger. Trigger when the user types `/ears-gap-fix <path-to-EARS-file>` (controller path(s) may be passed as an optional override).
In this repository19 other files it gives its agents.
- article-summarizer-2minsSkill
- article-summarizerSkill
- book-summarizerSkill
- code-reviewSkill
- ears-to-dddSkill
- fix-dev-reviewsSkill
- grails-ears-gap-fixSkill
- grails-fix-dev-reviewsSkill
- grails-to-earsSkill
- graphifySkill
- implement-allSkill
- implement-queueSkill
- implement-ticketSkill
- implement-ticketsSkill
- merge-earsSkill
- prompt-masterSkill
- resolve-open-questionsSkill
- review-spring-bootSkill
- springboot-to-earsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 3 are distinctive, and 14 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
14
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.