agentleFS
Sign inStart free
AloisSeckarAloisSeckar/demos-java/.agents/skills/pr-create/SKILL.md

pr-create

Skill25 starsChanged 7 days agoUnlicenseView on GitHub

Branch, commit, and open a pull request for a finished JEP demo in demos-java, closing its GitHub issue. Use as the final step of demo-create and demo-update.

  • Commits and pushes

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pr-feedback, explore and 2 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.
  • dversozaSkill

    pr-feedback

    Address PR review feedback including inline threads, general comments, bot-generated reviews, PR description findings, check run annotations (inline lint/type/security findings shown in the Files changed tab), code scanning alerts, and CI failures. Use when asked to handle, address, resolve, respond to, or work through PR review comments, review feedback, inline findings, or CI check failures. Triggers on requests like "address PR comments", "handle review feedback", "resolve PR reviews", "fix review comments", "go through PR feedback", "check CI failures", "fix the inline findings on the PR".

    Also in 5 projects that use this

  • genomewalkerSkill

    explore

    RLM-style recursive memory exploration - dynamically navigate the memory graph

    Also in 4 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 5 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not install or log in to it on the user's behalf.

    line 22
  2. Very specific:

    Use gh issue list --state open --search "JEP <jep-number> in:title" if gh is available.

    line 28
  3. Distinctive:

    If there are no matches or several, ask the user which issue to use, or whether to proceed without one.

    line 32
  4. Very specific:

    Run git status and confirm the changes contain only demo-related files: the demo class(es), JDK<jdk>Info.json files, and …

    line 33
  5. Very specific:

    Create and switch to jep-<jep-number> from the current branch (normally an up-to-date master), so the uncommitted changes come along.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 23 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

Open a PR for a JEP Demo

Input: the JEP number the demo was implemented for. For demo-update, use the new JEP. The demo must already build and run as described in demo-create or demo-update.

Values used below:

  • <jdk>: the JDK release the JEP targets, i.e. the java<jdk> package holding the implementation.
  • Branch: jep-<jep-number>.
  • Title and commit message: feat(jdk<jdk>): add demo for JEP <jep-number>.

Prerequisite: GitHub CLI

The GitHub CLI (gh) is the preferred tool for steps 1 and 6. Check it with gh auth status. If gh is missing or not logged in, recommend that the user install it from https://cli.github.com/ and run gh auth login. Do not install or log in to it on the user's behalf. Continue with the fallbacks below, and repeat the recommendation in the final report.

Workflow

  1. Find the open issue for the JEP in AloisSeckar/demos-java. Use gh issue list --state open --search "JEP <jep-number> in:title" if gh is available. Otherwise use a GitHub issue tool or fetch https://github.com/AloisSeckar/demos-java/issues?q=is%3Aissue+is%3Aopen+%22JEP+<jep-number>%22+in%3Atitle. Accept only an issue whose title starts with JEP <jep-number> . If there are no matches or several, ask the user which issue to use, or whether to proceed without one.
  2. Run git status and confirm the changes contain only demo-related files: the demo class(es), JDK<jdk>Info.json files, and Java<jdk>DemoLoader.java loaders. Never stage target/, tmp/, or unrelated edits. Ask the user about anything unexpected.
  3. Create and switch to jep-<jep-number> from the current branch (normally an up-to-date master), so the uncommitted changes come along. If the branch already exists, ask the user before reusing it.
  4. Stage the demo-related files explicitly by path and commit them with the commit message above.
  5. Push with git push -u origin jep-<jep-number>. If origin is not writable (for example, a contributor working on the upstream repo), push to the user's fork and open the PR from <fork-owner>:jep-<jep-number>. In PowerShell, git writes progress to stderr and may report exit code 1 on success; don't add 2>&1, and verify with git ls-remote origin jep-<jep-number> instead of trusting the exit code.
  6. Open a PR against master of AloisSeckar/demos-java with the title above. Its body is Closes #<issue-number>, or nothing if the user chose to proceed without an issue. Use gh pr create --base master --head jep-<jep-number> --title "<title>" --body "<body>" if gh is available, otherwise any available GitHub PR tool. If neither works, give the user the compare URL https://github.com/AloisSeckar/demos-java/compare/master...jep-<jep-number>?expand=1 along with the title and body.
  7. Report the branch, commit, and PR URL.

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