Menu
Create a new feature directory with Quarkus worktree and isolated .m2
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when the user wants a quick summary of today's work from journal entries
Generate a Quarkus migration guide entry for a Hibernate version upgrade, in asciidoc format ready for the Quarkus wiki
Use when bumping Hibernate ORM, Reactive, Search, and Tools versions in a Quarkus feature branch — either from a dependabot PR URL or explicit version numbers
Generate Maven artifact relocations for renamed Quarkus extensions, including BOM entries and OpenRewrite recipes
Add a repository worktree to an existing feature directory
Clone all repos into main/, set up remotes, build all projects into ~/.m2
| name | create-feature |
| description | Create a new feature directory with Quarkus worktree and isolated .m2 |
| user_invocable | true |
Usage: /create-feature <name> [base-branch] (e.g., /create-feature 3223 or /create-feature 3.33-backport 3.33)
Creates a feature directory with a Quarkus worktree and an isolated .m2 seeded from ~/.m2/repository via hardlinks.
<name>: Feature name (used for directory and branch naming).[base-branch]: Optional upstream branch to base the worktree on. Defaults to upstream/main. If provided, fetch and use upstream/<base-branch> instead.main/ must be initialized (run /init-workspace first).~/.m2/repository must contain built artifacts.Validate: Check that main/quarkus exists. Fail with a clear message if not.
Create feature directory:
mkdir -p ~/git/hibernate/<number>/journal
Create Quarkus worktree from main/quarkus:
If a base branch was specified, fetch it first:
cd ~/git/hibernate/main/quarkus
git fetch upstream <base-branch>
Then create the worktree (use upstream/main if no base branch was specified):
git worktree add ~/git/hibernate/<name>/quarkus QUARKUS-<name>
If branch QUARKUS-<name> doesn't exist, create it from the base:
git worktree add -b QUARKUS-<name> ~/git/hibernate/<name>/quarkus upstream/<base-branch>
Seed .m2 via hardlinks from ~/.m2/repository:
rsync -a --link-dest=$HOME/.m2/repository/ $HOME/.m2/repository/ ~/git/hibernate/<name>/.m2/
Set up Maven config in the worktree:
Create or prepend to ~/git/hibernate/<name>/quarkus/.mvn/maven.config:
-Dmaven.repo.local=$HOME/git/hibernate/<name>/.m2
If .mvn/maven.config already exists (from the repo), prepend the line.
Build Quarkus into the feature's .m2:
cd ~/git/hibernate/<name>/quarkus
~/git/hibernate/scripts/build-fast.sh
(The -Dmaven.repo.local is already set via .mvn/maven.config.)
Verify SNAPSHOT artifacts were updated using the shared script:
~/git/hibernate/scripts/print-snapshot-timestamps.sh ~/git/hibernate/<name>/.m2 after
This prints a summary with jar count and timestamps to confirm the build populated the feature's .m2.
Confirm: Print the feature directory contents and remind the user to configure IntelliJ IDEA before opening ~/git/hibernate/<name>/quarkus:
IntelliJ setup (required):
~/git/hibernate/<name>/.m2. IntelliJ does not respect -Dmaven.repo.local from .mvn/maven.config for plugin resolution during import.--release flag: Settings → Build → Compiler → Java Compiler → uncheck "Use '--release' option for cross-compilation (Java 9 and later)". Without this, Quarkus fails to compile because --release conflicts with --add-exports for internal JDK APIs.