Run any Skill in Manus with one click

exeris-doc-impact-triage

Stars5

Forks0

UpdatedJune 18, 2026 at 05:17

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

exeris-systems

exeris-systems/exeris-kernel

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	exeris-doc-impact-triage
description	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.

Exeris Doc Impact Triage

Purpose

Quickly detect documentation and ADR drift risk in triage.

Output Contract

Return exactly one status:

NO_DOC_IMPACT
MINOR_DOC_IMPACT
DOCS_REVIEW_REQUIRED
ADR_REVIEW_POSSIBLE

And return:

why
suggested_doc_action

Triage Rules

No behavior/contract/boundary change → likely NO_DOC_IMPACT.
Terminology/config/default changes → often MINOR_DOC_IMPACT.
Observable behavior change or subsystem contract drift → DOCS_REVIEW_REQUIRED.
Architectural intent/boundary meaning changes → ADR_REVIEW_POSSIBLE.

Completion Criteria

Classification is complete only if status and action are both explicit.

More from this repository

same repository

exeris-architect-guardrails

exeris-systems/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.

2026-07-105

exeris-java26-panama-loom

exeris-systems/exeris-kernel

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.

2026-07-105

exeris-performance-contract

exeris-systems/exeris-kernel

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.

2026-07-105

exeris-pr-preflight

exeris-systems/exeris-kernel

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.

2026-07-105

exeris-pr-review-waste-hunter

exeris-systems/exeris-kernel

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.

2026-07-105

exeris-release-integration

exeris-systems/exeris-kernel

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.

2026-07-105

Run any Skill with one click