agentleFS
Sign inStart free
AloisSeckarAloisSeckar/demos-java/.agents/skills/demo-update/SKILL.md

demo-update

Skill25 starsChanged 8 days agoUnlicenseView on GitHub

Update an existing JEP demo in demos-java to a newer preview, incubator, or final iteration, linking earlier demos to the new implementation.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. AnjanJ/rails_error_dashboard★ 93same name

    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 repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow CONTRIBUTING.md and the existing demo's style.

    line 11
  2. Very specific:

    Read https://openjdk.org/jeps/<new-jep-number> and predecessor pages as needed to establish the full feature chain, official titles, JDK …

    line 15
  3. Distinctive:

    Check whether any earlier stub already links to the demo being superseded (a chain may span 3+ releases).

    line 18
  4. Very specific:

    Use a /// header with a feature/status summary, required runtime flags, concise API-change notes per intervening release, newest-first JEP …

    line 23
  5. Very specific:

    Update each affected src/main/resources/JDK<jdk>Info.json:

    line 31
  6. Very specific:

    Import and register the new demo and newly created stubs in their respective src/main/java/org/javademos/init/Java<jdk>DemoLoader.java.

    line 35
  7. Very specific:

    Run mvn clean install and the jar using the command in CONTRIBUTING.md.

    line 37

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

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

Update a JEP Demo

Inputs: the new JEP number and the JEP number holding the current implementation. Ask for any missing input. For a JEP without predecessors, use demo-create instead. Follow CONTRIBUTING.md and the existing demo's style.

Workflow

  1. Read https://openjdk.org/jeps/<new-jep-number> and predecessor pages as needed to establish the full feature chain, official titles, JDK releases, and API changes. Locate the existing implementation, earlier stubs, JSON entries, and loaders. Identify missing iterations between the existing and new JEPs. Check whether any earlier stub already links to the demo being superseded (a chain may span 3+ releases); it must be re-pointed too. If a similar multi-release chain already exists in the repo, use it as a template.
  2. Port the implementation to org.javademos.java<jdk>.jep<newJep>, keeping the class name unchanged and starting demo() with info(<newJep>). Check the installed JDK and API signatures, and adapt the code to the new API with small runnable examples of notable changes. Use a /// header with a feature/status summary, required runtime flags, concise API-change notes per intervening release, newest-first JEP history using official titles, and relevant reading links. Retain existing reading links and author attribution.
  3. Convert every superseded demo in the chain to a linking stub; create stubs for missing intermediate iterations too. Each stub keeps its original JDK/JEP package, class name, and author, but its /// doc comment shrinks to a one-line summary plus a "replaced by" pointer (drop API-change notes, JEP history, and reading links, which belong only on the current implementation). It calls only info(<itsJep>) in demo(), and has an @see pointing directly to the new implementation, never another stub.
  4. Update each affected src/main/resources/JDK<jdk>Info.json:
    • Old and intermediate entries: "link": true, "code": false, and dscr set to Up-to-date demo in `org.javademos.java<jdk>.jep<newJep>.<ClassName>`.
    • New implementation: the actual title/description, "link": false, "code": true. Import and register the new demo and newly created stubs in their respective src/main/java/org/javademos/init/Java<jdk>DemoLoader.java. Keep JSON and loader entries in ascending JEP order.
  5. Run mvn clean install and the jar using the command in CONTRIBUTING.md. Inspect the chain by appending --only=<jep1>,<jep2>,... to the jar command (other demos print exceptions on purpose). Confirm every JEP in the chain prints its header without exceptions and the new examples produce expected output. Check all earlier @see and JSON dscr references point to the new implementation, and review the diff for unrelated changes.
  6. Branch, commit, and open the PR by following pr-create for <new-jep-number>.

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.

Check your setup, free