exeris-kernel

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.

Targeted single-subsystem review for Exeris Kernel via one mode-driven skill — one mode per contract doc in docs/subsystems/ (bootstrap, config, crypto, events, exceptions, flow, graph, http, memory, persistence, security, telemetry, transport). Use when a change is concentrated in one subsystem and you want its contract doc loaded as the primary source of truth plus mode-specific deep checks — without spawning multiple agents. State the mode (e.g. "review this as Transport").

Run the tagged test gates (integration / continuity / stress) that the default build EXCLUDES, mapped from what a change touched. Use before claiming definition-of-done when touched code is covered by @Tag'd tests, or to reproduce a CI gate (persistence RLS, Kafka, recovery continuity, transport stress) locally.

Single-pass triage for an Exeris Kernel task, PR, or request — classify the work, identify subsystem scope and required contract docs, pick the one primary risk, choose the owning specialist plus ordered handoffs, and set the validation gates. Replaces the former task-classifier / subsystem-scope-detector / risk-prioritizer / routing-planner / validation-gate-planner / multi-agent-handoff micro-skills. Use at the START of work when the owner is not obvious, the scope crosses domains, or several risks compete.

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.

Quick check of whether an Exeris Kernel change needs documentation/ADR updates and at what level (none / minor / docs-review / ADR-review). Use during triage to decide if a full exeris-docs-adr-check review is warranted before merging.

Disciplined JMH/JFR performance-research loop for Exeris Kernel — guards against single-run flukes, driver confounds, and wrong conclusions from hot-method noise. Use when investigating a throughput/latency/allocation regression or claim, reading a JFR recording, or running a benchmark on a research/<slug> branch.

TCK-first review for Exeris Kernel. Use when a change touches SPI interfaces, value/error contracts, lifecycle/state behavior, or provider bindings — to enforce that every contract change has executable Abstract*Tck coverage plus binding tests in Core/Community/Enterprise, with semantic (not happy-path-only) assertions. Trigger on new contract surface, changed error codes, or altered observable behavior.

Documentation and ADR consistency review for Exeris Kernel. Use when PRs may cause doc drift, architectural intent changes, or mismatch between repository reality and documented target-state.

Observability contract review for Exeris Kernel. Use for PRs touching bootstrap, telemetry, memory, transport, lifecycle/state machines, and exception mapping to enforce JFR-first events, lightweight emission, secret-safe payloads, L0/L1 boundaries, and error/rawArgs contracts.

Plugin-model and lifecycle PR review for Exeris Kernel. Use for changes touching ServiceLoader semantics, provider discovery, bootstrap DAG, fail-fast/degrade policy, and SPI→Core→Driver boundaries while keeping Core driver-agnostic.

Architectural PR review for Exeris Kernel. Use for every PR review to enforce docs/modules, docs/subsystems, ADR alignment, The Wall boundaries, SPI blindness, Core isolation, and dependency graph integrity.

Router/Planner docs skill for Exeris Kernel. Classifies expected documentation/ADR impact and required review level.

Documentation and ADR consistency review for Exeris Kernel. Use when PRs may cause doc drift, architectural intent changes, or mismatch between repository reality and documented target-state.

Java 26+ runtime PR review for Exeris Kernel. Use for every PR that touches concurrency, memory, native interop, and data carriers to enforce ScopedValue, StructuredTaskScope, Panama FFM, Valhalla readiness, immutable/early construction, and removal of legacy framework idioms.

Observability contract review for Exeris Kernel. Use for PRs touching bootstrap, telemetry, memory, transport, lifecycle/state machines, and exception mapping to enforce JFR-first events, lightweight emission, secret-safe payloads, L0/L1 boundaries, and error/rawArgs contracts.

Router/Planner coordination skill for Exeris Kernel. Builds ordered handoff chains and identifies blocking dependencies between specialist steps.

Performance-lawyer PR review for Exeris Kernel. Use for every PR review to enforce No Waste Compute, zero-allocation hot paths, structured concurrency, off-heap discipline, and mandatory JFR lifecycle telemetry.

Meta PR review persona for Exeris Kernel. Use as default review style to ruthlessly detect software inflation, enforce simplification, flag classes with >5 dependencies, reward lock-free/zero-copy/contract-pure patterns, and justify findings with architecture lore.

Router/Planner risk skill for Exeris Kernel. Identifies primary risk, justification, and secondary risks to drive routing priority.

Router/Planner skill for Exeris Kernel. Produces primary agent, required secondary handoffs, execution order, and minimal next action.

Plugin-model and lifecycle PR review for Exeris Kernel. Use for changes touching ServiceLoader semantics, provider discovery, bootstrap DAG, fail-fast/degrade policy, and SPI→Core→Driver boundaries while keeping Core driver-agnostic.

Optional Router/Planner scope skill for Exeris Kernel. Detects impacted subsystem(s), required contract docs, and single-vs-cross subsystem scope.

Subsystem-focused PR review for Exeris Kernel using one skill with modes: bootstrap, memory, crypto, transport, persistence, events, flow, http, security, config. Use when you want a targeted subsystem review without creating many separate agents.

Router/Planner triage skill for Exeris Kernel. Classifies task type, scope, severity, and recommends primary agent based on primary risk.

TCK-first PR review for Exeris Kernel. Use when changes touch SPI contracts, observable behavior, or provider bindings to enforce that every contract change has executable Abstract*Tck coverage and implementation bindings in Core/Community/Enterprise.

Router/Planner validation skill for Exeris Kernel. Defines required validation layers, merge gates, and optional checks based on risk and scope.