agentleFS
utopia-riseutopia-rise/godot-kotlin-jvm/.claude/skills/spec-review/SKILL.md

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

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the utopia-rise/godot-kotlin-jvm repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about utopia-rise/godot-kotlin-jvm

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

43 more on GitHub

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-healthSkill

    get-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-healthSkill

    push-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

  • fernandoxavier02Skill

    spec-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

  • NVIDIASkill

    generate-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

  • telefrekSkill

    spec-init

    Bootstrap the spec corpus for this project

    Also in 3 projects that use this

  • xfstudioSkill

    spec-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

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
  1. Very specific:

    Read specs/CLAUDE.md, then specs/CONSTITUTION.md.

    line 26

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. 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 its Reopen if: holding?
  2. Statuses. Does it make a todo or partial capability's sentence true, or a done one false or true only in part? Apply the status definitions of specs/TRACKER.md: untested paths are a caveat, only user-visible leftovers make a capability partial. A capability moved to done needs a test that would fail without the change; otherwise say it is untested.
  3. 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.
  4. Spec edits in the change. If specs/ changed: does python specs/check_specs.py pass, were rewordings and deletions followed by --accept, and do deleted IDs have abandoned tracker lines? A rule rewording or a new Except: that clears a breaks note without any code change needs the maintainer's confirmation: flag it.
  5. IDs outside specs. Spec IDs must not appear in code, comments, docs or CI files.
  6. Doc drift. User docs or API docs touched by the change must not contradict a spec rule.

4. Report

One table, most important first:

KindSpec IDFindingWhere (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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.