菜单
Authoring workflow for an Exeris ADR / RFC / Research doc — picks the right document shape, reserves the GLOBAL ADR number BEFORE writing content, and registers the row after landing. Use whenever asked to draft, write, or number an ADR/RFC/research note anywhere in the exeris-* ecosystem.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Architectural review for Exeris Kernel changes that touch module boundaries, SPI/Core/Community/Enterprise placement, dependency direction, provider wiring, or ADR-fixed structure. Use when a change adds or moves interfaces/providers, alters module layering, or risks a The-Wall breach (SPI implementation leak, Core driver leak). Not needed for pure intra-module edits with no boundary impact.
Java 26+ idiom review for Exeris Kernel. Use when a change touches concurrency, context propagation, native interop, memory APIs, or runtime data carriers — to enforce ScopedValue over ThreadLocal, StructuredTaskScope over ad-hoc async, Panama FFM (MemorySegment/Linker/SymbolLookup), Valhalla-ready immutable carriers, early construction, and removal of legacy framework idioms.
Performance-lawyer review enforcing No Waste Compute for Exeris Kernel. Use when a change touches runtime hot paths (transport, flow, memory, persistence, bootstrap, dispatch) or can affect allocations, structured concurrency, off-heap copies, or banned APIs (ThreadLocal, ExecutorService, CompletableFuture, ByteBuffer, Unsafe). Skip for docs-only or pure test/tooling changes.
Pre-PR gate for Exeris Kernel — run BEFORE opening or pushing any PR. Enforces lint-gate integrity (skip flags poison a green build's lint proof), the architecture guard test, fresh-branch-per-task discipline, and the register-ADR-before-claiming rule. Use whenever about to commit/push a branch or open a PR in the kernel repo.
Default entry-point for ANY Exeris Kernel PR/diff/branch review — start here. Triages software inflation, >5-dependency classes, and boundary/perf/contract risk, then dispatches to the focused lens skills (exeris-architect-guardrails, exeris-performance-contract, exeris-tck-first, exeris-jfr-telemetry-review, exeris-java26-panama-loom, exeris-subsystem-specialist) as the diff warrants. Trigger whenever asked to review, look at, audit, or assess a change.
Milestone release flow for Exeris Kernel — flip versions, write release notes, integrate development/X.Y.0 into main via a single release(x.y.z) PR, then open the next development line. Use when asked to prepare, cut, integrate, or finalize a milestone release, or to open the next development branch.
| name | exeris-adr-register |
| description | Authoring workflow for an Exeris ADR / RFC / Research doc — picks the right document shape, reserves the GLOBAL ADR number BEFORE writing content, and registers the row after landing. Use whenever asked to draft, write, or number an ADR/RFC/research note anywhere in the exeris-* ecosystem. |
Prevent ADR-number collisions and wrong-shape decision docs. ADR numbering is a single GLOBAL namespace across all exeris-* repos; claiming a number before reserving it caused the PR #129 / ADR-026 collision. This skill encodes the safe order of operations.
Three shapes for three question kinds (templates in ~/exeris-systems/exeris-docs/templates/); they are NOT interchangeable:
RESEARCH-TEMPLATE.md) — falsifiable hypothesis, lab-notebook, JMH/JFR-driven. Branch-scoped (research/<slug>). No central registry.RFC-TEMPLATE.md) — multi-option strategic question. File: RFC-YYYY-MM-DD <Short Title>.md. No central registry.ADR-TEMPLATE.md) — decision ALREADY made. File: ADR-NNN <Short Title>.md. Enters the registry.If upstream measurement or option comparison is missing, propose Research or RFC before going straight to ADR.
adr-index.md in the separate exeris-docs repo (locally ~/exeris-systems/exeris-docs/adr-index.md; requires that repo checked out alongside the kernel) and find the next free slot (numbering is chronological by decision date with reserved gap-fillers).exeris-* repos plus Corelio/ stack-level decisions. budgetHQ/ and pbm/ have their own internal namespaces — they do NOT enter adr-index.md.docs/adr/.docs/adr/ADR-NNN.link.md stub.public or enterprise-private (the old public-staged is deprecated).adr-index.md as a SEPARATE commit in the exeris-docs repo (separate from the content commit, separate repo).exeris-docs access. If it is not available in the current session, do NOT skip it silently — open a follow-up issue/note to register (or reserve) the number so the global namespace stays collision-safe.Legal / IP / financial / procurement decisions go in the private decision registry in ~/exeris-systems/exeris-business/, NOT the public tech registry. Public ADRs invoke a business policy descriptively (e.g. "the IP detachment commercial policy"), never by an internal id.
Exeris is pre-1.0 / TRL-3 with no external SPI consumers — do NOT use "breaking change" framing. Reserve that vocabulary for 1.0.0 GA / TRL-5+.
.link.md stubs + visibility tag.