菜单
Field/Validation canonical scoping review for exeris-sdk. Use whenever `@Field` or `@Validation` attributes (or the `FieldMetadata` AST record) are touched, or when generator-derived NOT NULL / not-blank semantics (from `FieldMetadata.required`) are in scope.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Maven Central publish-readiness review for exeris-sdk. Use whenever you bump a module version, touch `<distributionManagement>` or required POM metadata (`<url>`, `<licenses>`, `<developers>`, `<scm>`, `<issueManagement>`, `<organization>`), or add a new publishable Maven module — before a release goes out.
AST + Jackson 3 wire-format contract review for exeris-sdk. Use whenever you add/change/remove an AST record under `eu.exeris.sdk.sourcemodel.ast.*`, touch Jackson config (`@JsonInclude`, serializers/deserializers), or bump `jackson-annotations` / `jackson.version` in the BOM — during editing, not only at PR review.
Triage skill for exeris-sdk — use FIRST on any non-trivial SDK task, before editing annotations, AST records, UI kit, poms, or docs. Classifies task type (annotation contract / AST wire-format / UI kit / stability / docs / publish-readiness), scope, and severity, and routes to the right specialist agent.
Annotation contract review for exeris-sdk. Use whenever you add, change, or remove a public `@interface` in `exeris-sdk-annotations` (any package — root, `system`, `security`, or a newly introduced subpackage) — enforces `@Retention(SOURCE)` + `@Target`, the invariant every downstream consumer depends on.
Build-invariants review for exeris-sdk. Use whenever you touch `maven.compiler.release`, the `jacoco-maven-plugin` version, the reactor `<modules>` list, or root/parent build-plugin config — guards the JDK 26 floor, JaCoCo ≥0.8.14, and ui-kit-is-npm-only.
Coverage-gate review for exeris-sdk. Use whenever you add new code/branches to `exeris-sdk-source-model` (`ast.*`, `mutation.*`) or `exeris-sdk-ui-kit`, add or restructure a test, or hit a JaCoCo (85% BUNDLE) / Vitest (85% per-file) failure — enforces where new tests belong.
| name | exeris-sdk-field-validation-scoping-review |
| description | Field/Validation canonical scoping review for exeris-sdk. Use whenever `@Field` or `@Validation` attributes (or the `FieldMetadata` AST record) are touched, or when generator-derived NOT NULL / not-blank semantics (from `FieldMetadata.required`) are in scope. |
Enforce: @Field owns field-shape + lifecycle (required, inCreate, inUpdate + the presentation facets) and declares NO constraint attributes; @Validation owns ALL constraint declarations (min, max, minLength, maxLength, pattern, email, url, future, past, …); FieldMetadata is the single AST carrier of the constraint values, populated from @Validation by the processor and the -io reader; ValidationMetadata is deprecated (removal 1.0.0); @Validation.required / @Validation.validateOn deprecated; the 0.9.0 cut (ADR-054) is never reversed; rationale stays synced across BOTH package-info files.
This is the single most likely regression surface in the repo.
@Field.@Validation.FieldMetadata AST record (or attempting to resurrect the removed ValidationMetadata).FieldMetadata.required).docs/adr/ADR-054-field-validation-min-max-pattern-cut.md) + the repo CLAUDE.md scoping section.CLAUDE.md + package-info + ADR-054)@Field owns: required, inCreate, inUpdate + presentation / persistence facets. It declares no constraint attributes (the only pattern-shaped attribute it has ever had is maskPattern — log/PII masking, unrelated).@Validation owns: ALL constraint declarations — min, max, minLength, maxLength, pattern, email, url, future, past, etc.FieldMetadata is the single AST carrier of the constraint values (minLength / maxLength / min / max / pattern), populated from @Validation by the build-time processor and the -io reader. The four numeric bounds are per-component @JsonInclude(NON_NULL) (0.9.0) so zero-valued bounds survive the wire.ValidationMetadata was removed outright in 0.9.0 — never populated by any processor/reader, never referenced by DomainMetadata, never consumed by any generator, and no published artifact existed for anyone to depend on (the deprecation window would have been vacuous; 0.x permits the break).@Validation.required → moved to @Field.required.@Validation.validateOn → moved to @Field.inCreate / @Field.inUpdate.FieldMetadata.required.@Validation) informed it. REJECT reintroducing constraint attributes on @Field, resurrecting ValidationMetadata (growing or un-deprecating it), or adding any parallel AST validation carrier.@Field,@Validation.@Validation.required / @Validation.validateOn, confirm they stay @Deprecated(forRemoval = true) with a javadoc pointer to the canonical replacement (@Field.required / @Field.inCreate+inUpdate).FieldMetadata.required at generator level. Don't make them separately declarable.@Field, ValidationMetadata resurrected / grown / un-deprecated, or a new parallel AST validation carrier → hard reject.exeris-sdk-annotations/src/main/java/eu/exeris/sdk/annotation/package-info.javaexeris-sdk-source-model/src/main/java/eu/exeris/sdk/sourcemodel/ast/package-info.javaMIGRATION.md entry with diff.~/exeris-systems/exeris-tooling/exeris-processor/) when the scoping change visibly affects extraction logic (constraint-value extraction targets FieldMetadata; the -io reader must stay in parity per ADR-042).APPROVE / CONDITIONAL / REJECT.@Field (or field-shape on @Validation); deprecated attribute or ValidationMetadata revived; NOT NULL / not-blank made separately declarable; a parallel AST validation carrier introduced; package-infos out of sync.@Field / @Validation / metadata records touched)APPROVE / CONDITIONAL / REJECT)@Field or field-shape on @Validation.@Validation.required / @Validation.validateOn as non-deprecated.ValidationMetadata resurrected (removed in 0.9.0) or any parallel AST validation carrier.FieldMetadata.required at generator level).FieldMetadata.