spec-review
Skill1k starsChanged 10 days agoMITView on GitHub
Review a code change against the specs in specs/ - contradicted rules, non-goals or constitution articles, capability statuses the change should move, missing capabilities, and spec/tracker updates left out. Use before committing or opening a PR, or when asked to check a change against the specs.
48 other projects use a version of this, 1 of them edited.
Trending
Quiet since March.about the whole repository
Most recently taken up by
- philoserf/claude-code-configtheir own version, first seen Nov 15, 2026
- xsyubin/clue-lenstheir own version, first seen Nov 15, 2026
- komluk/scaffoldingtheir own version, first seen Nov 15, 2026
- adamdaw/claude-code-skillstheir own version, first seen Nov 13, 2026
- markkj/skillstheir own version, first seen Nov 11, 2026
- utopia-rise/fmod-gdextensionedited, first seen Nov 9, 2026
Who's talking about utopia-rise/godot-kotlin-jvm
- @cyrilsebek.cz“You can go with C#, it has more similarities... And probably also try Java github.com/utopia-rise/...”Bluesky · Feb 14, 2025 · 2 likes
- godotengine/godot“Improve thread safety of `ScriptServer`”GitHub · Sep 30, 2023 · 1 reactions
- utopia-rise/godot-jvm“Clarify export documentation”GitHub · Mar 28, 2023 · 1 reactions
- utopia-rise/godot-jvm“Can't use custom jvm arguments that contain equal sign”GitHub · Mar 27, 2026
- utopia-rise/kotlin-preprocessors“Replace grgit and bump version”GitHub · Oct 19, 2025
The biggest 5 of 49 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 49
Talked about on GitHub and Bluesky (49 times).
On GitHub · 48
- Sep 30, 2023Improve thread safety of `ScriptServer` — godotengine/godot1 reaction · 34 comments
- Mar 28, 2023Clarify export documentation — utopia-rise/godot-jvm1 reaction
- Mar 27, 2026Can't use custom jvm arguments that contain equal sign — utopia-rise/godot-jvm0 reactions · 2 comments
- Oct 19, 2025Replace grgit and bump version — utopia-rise/kotlin-preprocessors0 reactions
- Aug 28, 2025String-only methods ignore vararg arguments. — utopia-rise/godot-jvm0 reactions
43 more on GitHub
- May 10, 2025iOS export issues — utopia-rise/godot-jvm0 reactions · 8 comments
- Apr 19, 2025GH-811 GH-813 Copy missing resource files for android exports — utopia-rise/godot-jvm0 reactions
- Mar 10, 2025Godot 4.4 upgrade — v79/ProjectKuiper0 reactions
- Nov 3, 2024Add GenerateEmbeddedJreTask to generate JRE — utopia-rise/godot-jvm0 reactions · 4 comments
- Oct 26, 2024Experimental: JDK 22 Foreign API — utopia-rise/godot-jvm0 reactions
- Aug 31, 2024Fix custom classes hint string — utopia-rise/godot-jvm0 reactions
- May 29, 2024Idea Plugin not upgarde to 0.9.1-4.2.2 — utopia-rise/godot-jvm0 reactions · 3 comments
- May 26, 2024[Kotlin 2.0] Fix `Variant::toGodot` call after KT-68339 is fixed — utopia-rise/godot-jvm0 reactions · 3 comments
- May 16, 2024Improve ci/cd cache setup — utopia-rise/godot-jvm0 reactions
- May 10, 2024Add better jni error reporting inside the godot editor — utopia-rise/godot-jvm0 reactions · 2 comments
- Apr 25, 2024Feature/ios/update to graal 23 — utopia-rise/godot-jvm0 reactions
- Apr 14, 2024Initial setup on Windows — gabryon99/postcat-kodee0 reactions · 11 comments
- Apr 3, 2024iOS static library export is broken — godotengine/godot0 reactions
- Feb 24, 2024Fix android export templates and fix export template target version — utopia-rise/godot-jvm0 reactions
- Feb 18, 2024Fix android export templates — utopia-rise/godot-jvm0 reactions · 3 comments
- Feb 14, 2024Rework KotlinLanguage to fix editor script operations — utopia-rise/godot-jvm0 reactions · 1 comment
- Feb 8, 2024[Bugfix] Fix typed array registration — utopia-rise/godot-jvm0 reactions · 2 comments
- Nov 8, 2023Implement an LRU cache for StringName objects. — utopia-rise/godot-jvm0 reactions
- Oct 23, 2023feat(api-gen): Generate bitfields using interface, value class and statics — utopia-rise/godot-jvm0 reactions · 3 comments
- Oct 18, 2023Can't build the project if there is a test source set — utopia-rise/godot-jvm0 reactions · 9 comments
- Jun 27, 2023Cannot attach Kotlin scripts — utopia-rise/godot-jvm0 reactions · 10 comments
- Jun 9, 2023Fix `3.x` release pipeline — utopia-rise/godot-jvm0 reactions
- Mar 7, 2023Support exporting of types extending node — utopia-rise/godot-jvm0 reactions
- Mar 7, 2023Update checks and refactoring tools in the IDE plugin — utopia-rise/godot-jvm0 reactions
- Mar 7, 2023Generate `gdj` and `kt` files from within the godot editor — utopia-rise/godot-jvm0 reactions · 2 comments
- Mar 7, 2023Relocate conflicting class files in fat jars — utopia-rise/godot-jvm0 reactions · 2 comments
- Mar 2, 2023Update/Fix property hints — utopia-rise/godot-jvm0 reactions
- May 28, 2022test resize and set for PoolRealArray, PoolVector2Array, PoolVector3Array — utopia-rise/godot-jvm0 reactions · 3 comments
- Mar 13, 2022Investigate `native_structures` in `api.json` — utopia-rise/godot-jvm0 reactions · 4 comments
- Mar 13, 2022Simplify GC leveraging `objectID` and `validatorCount` — utopia-rise/godot-jvm0 reactions
- Mar 13, 2022Finish API gen reimplementation — utopia-rise/godot-jvm0 reactions · 1 comment
- Mar 13, 2022Change CPP/JVM object handling to incorporate `objectID` changes — utopia-rise/godot-jvm0 reactions
- Mar 13, 2022Add/Rename hardcoded types in Entry-Gen — utopia-rise/godot-jvm0 reactions · 1 comment
- Aug 21, 2021Refactor gradle plugin — utopia-rise/godot-jvm0 reactions · 1 comment
- Jun 28, 2021Move JVM variant types and Set<Enum> registration to the new entry gen model. — utopia-rise/godot-jvm0 reactions · 2 comments
- Apr 24, 2021System conversions of float to string should be locale independent — godotengine/godot0 reactions · 6 comments
- Apr 23, 2021Add annotation to helper functions — utopia-rise/godot-kotlin-api-generator0 reactions
- Apr 19, 2021Generate changelog — utopia-rise/godot-jvm0 reactions
- Apr 17, 2021Fix stackoverflow by making recursive calls tailrec — utopia-rise/godot-kotlin-api-generator0 reactions
- Apr 16, 2021Make default value provider lazy — utopia-rise/godot-kotlin-entry-generator0 reactions
- Apr 1, 2021Fix ktPrefixExpression registration — utopia-rise/godot-jvm0 reactions
- Apr 1, 2021Fix KtPrefixExpression registration — utopia-rise/godot-kotlin-entry-generator0 reactions
- Mar 6, 2021Add doc generation — utopia-rise/godot-kotlin-api-generator0 reactions
On Bluesky · 1
- Feb 14, 2025You can go with C#, it has more similarities... And probably also try Java github.com/utopia-rise/... — @cyrilsebek.cz2 likes and reposts
Used with
Projects with it also use get-pr-reviews, push-everything and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
saffron-healthSkillget-pr-reviews
Get nicely formatted output of the last review comments on a PR. Used internally by other skills.
Also in 3 projects that use this
saffron-healthSkillpush-everything
Stage ALL changes in the repository (not just session changes), commit, and push. Use when you need to commit all pending changes.
Also in 3 projects that use this
fernandoxavier02Skillspec-requirements
Generate EARS-format requirements based on project description and steering context. Use when generating requirements from project description.
Also in 3 projects that use this
NVIDIASkillgenerate-spec
Produce a feature specification covering API changes, backward compatibility, cross-language impact, performance, and a file-level change plan. Use when designing a new feature, planning a significant change, or the user asks to spec something out.
Also in 3 projects that use this
telefrekSkillspec-init
Bootstrap the spec corpus for this project
Also in 3 projects that use this
xfstudioSkillspec-tasks
Generate actionable, dependency-ordered tasks.md organized by user story. Use when user says "/spec-tasks", "create tasks", "generate task list" after /spec-plan to prepare for implementation.
Also in 3 projects that use this
- +2 more from saffron-health
Other versions48 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- utopia-rise/fmod-gdextension★ 95496% same
Wrote their own version · 47
- microsoft/winappCli★ 1.4ksame name
- cashew-labs/libretto★ 911same name
- saffron-health/libretto★ 911same name
- liza-mas/liza★ 418same name
- HHU3637kr/skills★ 148same name
- saffron-health/opencode-gui★ 59same name
- agent-ix/quoin★ 20same name
- microsoft/WinAppVSCE★ 18same name
- azents/azents★ 16same name
- komluk/scaffolding★ 16same name
37 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- specs/CLAUDE.mdCLAUDE.md
- build-nativeSkill
- bump-godotSkill
- check-cppSkill
- godot-cpp-fork-commitSkill
- regenerate-apiSkill
- run-editor-probesSkill
- run-harness-testsSkill
- test-in-projectSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 43 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Read specs/CLAUDE.md, then specs/CONSTITUTION.md.
“Common” is measured: kept by at least 6 in 10 of the 43 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Spec review
Review a change against specs/ and report what it implies. This is read-only: do not edit any file unless the user then asks for the fixes.
Keep it in proportion
Specs are broad guidelines: what Godot-JVM should offer, what it deliberately does not, and the rules an implementation must respect. They are not an inventory of the code. Details and implementation choices live in the code, and most changes, such as a fix, a refactor, a new helper, an option or a small convenience, have nothing to do with a spec. That is the normal case, not a gap.
So report only what matters at the level of the specs: a rule or article the change breaks, a non-goal it goes against, a capability whose status it really changes, or a new capability large enough that a user would describe it as one. Never report "no spec covers this" for a trivial change or a small feature, and never suggest a spec for something a sentence in an existing spec's lead already covers in spirit. When in doubt, it is not a finding. "No spec impact" is the expected answer for most changes.
1. Get the change
- With an argument: a git range (
master..HEAD,HEAD~3..HEAD) or a PR number (gh pr diff <n>). - Without one:
git diff $(git merge-base HEAD master)(the branch's commits) plus uncommitted changes.
Ignore pure formatting and test-only refactors; they cannot affect a spec. Spec and tracker edits inside the change are claims to verify against the code, not the baseline.
2. Find the specs it touches
Read specs/CLAUDE.md, then specs/CONSTITUTION.md. List the categories and specs with python specs/check_specs.py --summary, pick every spec whose concept the changed code serves, and read those spec files whole (lead, capabilities, rules, non-goals) with their tracker lines (--summary <SpecID>). When unsure whether a spec is concerned, read it.
3. Check
For each concerned spec, against the actual code after the change:
- Rules, articles, non-goals. Does the change break a spec rule or a constitution article (taking each
Except:into account), or implement something a non-goal excludes without itsReopen if:holding? - Statuses. Does it make a
todoorpartialcapability's sentence true, or adoneone false or true only in part? Apply the status definitions ofspecs/TRACKER.md: untested paths are a caveat, only user-visible leftovers make a capabilitypartial. A capability moved todoneneeds a test that would fail without the change; otherwise say it is untested. - Missing capability. Does it add or remove a whole capability, something a user would name as a feature of Godot-JVM, that no spec states even broadly? Helpers, options, small conveniences and refinements of an existing capability are not findings.
- Spec edits in the change. If
specs/changed: doespython specs/check_specs.pypass, were rewordings and deletions followed by--accept, and do deleted IDs haveabandonedtracker lines? A rule rewording or a newExcept:that clears abreaksnote without any code change needs the maintainer's confirmation: flag it. - IDs outside specs. Spec IDs must not appear in code, comments, docs or CI files.
- Doc drift. User docs or API docs touched by the change must not contradict a spec rule.
4. Report
One table, most important first:
| Kind | Spec ID | Finding | Where (file:line) | Options (recommended first) |
Kinds: breaks rule, breaks article, against non-goal, status, missing capability, spec edit, ID outside specs, doc drift. Options are concrete and name each way to arbitrate the conflict: the code to change, the spec sentence to reword or add, or the tracker line to write (partial with a breaks note). Mark the one you recommend and why in a few words. The maintainer arbitrates: never apply a spec-side resolution without their decision. When nothing applies, say "No spec impact" and name the specs you checked.
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.

