메뉴
Regenerates the openEHR spec + ITS layer from the vendored specs (emit / emit-xml / emit-rest) and checks for drift. Use after changing the openehr-codegen emitter or bumping a vendored spec, or when asked to regenerate the generated crates or run the codegen drift check.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | regen-codegen |
| description | Regenerates the openEHR spec + ITS layer from the vendored specs (emit / emit-xml / emit-rest) and checks for drift. Use after changing the openehr-codegen emitter or bumping a vendored spec, or when asked to regenerate the generated crates or run the codegen drift check. |
| allowed-tools | ["Bash","Read"] |
| argument-hint | (none) |
Regenerate everything openehr-codegen produces, in-session, and verify it is
in sync with the vendored specs. Never hand-edit // @generated
files — that is what this regenerates.
scripts/check-codegen-drift.sh runs — spec crates first):
cargo run -p openehr-codegen -- emit # openehr-base/rm/am/term/lang (rm incl. src/model)
cargo run -p openehr-codegen -- emit-xml # openehr-its XML ToXml/FromXml
cargo run -p openehr-codegen -- emit-json # openehr-its canonical-JSON ToJson/FromJson codec
cargo run -p openehr-codegen -- emit-rest # openehr-its ITS-REST contract
cargo run -p openehr-codegen -- emit-opt # openehr-its opt14 (OPT 1.4 model + XML codec)
cargo run -p openehr-codegen -- emit-rm-model # openehr-rm src/model (static RM attribute/type model)
cargo run -p openehr-codegen -- emit-validate # openehr-rm src/validate/generated.rs (RM invariant cores)
emit already emits openehr-rm/src/model; emit-rm-model refreshes just
that subtree and is byte-identical, so run order does not matter.)cargo build -q -p openehr-base -p openehr-rm -p openehr-am -p openehr-term -p openehr-lang -p openehr-its
cargo clippy -q -p openehr-codegen -p openehr-its --all-targets
cargo nextest run -p openehr-its # fidelity gates: JSON round-trip + schema + XML round-trip + EHRbase XML
bash scripts/check-codegen-drift.sh
codegen-drift job.) If it reports drift after your emitter
change, that is expected — commit the emitter change and the regenerated
output together.@generated file — investigate, don't commit.tools/openehr-codegen/vendor/bmm/, XSD/OAS/JSON at
crates/openehr-its/{schemas,vendor}/ (each with PROVENANCE.md).tools/openehr-codegen/src/, the load/→analyze/→plan/→render/
pipeline stages) or a *_impl.rs sibling — see .claude/rules/codegen.md.Closes a tracker issue: verifies the work is genuinely done (exit criteria, gates, docs, changelog), writes the close narrative into the PR description, ensures the PR declares `Closes #N`, posts the handoff comment, and deletes the implemented plan file. Use when the user says a work item is complete or asks to close it out.
Runs the CNF 2.0 conformance pipeline (scripts/conformance.sh) — the reference runner over the committed machine-readable catalogue and the acceptance instrument — against the Docker-composed server (or any BYO SUT). Use when the user asks to check conformance, run the conformance/CNF suite, verify spec compliance, or at phase close for the zero-drift gate.
Audits an implemented subsystem, endpoint group, or diff against the vendored openEHR spec text and the CNF Platform Conformance Test Schedule (docs/specs/openehr/), producing a findings list of divergences with spec citations. Use when the user asks "are we following the spec", "audit X against the spec/CNF", before closing a spec-facing phase, or after a conformance failure.
Reads the tracker (GitHub Issues), picks the pinned/top open issue (or the issue the user names), and restates it as a concrete in-session work plan naming the files and crates involved. Use when the user asks "what's next" or "what should I work on".
Prints the tracker's open issues (pinned first), any linked plan file's unchecked tasks, and a short git status. Use when the user asks "where are we", "what's in flight", or at the start of a work session to orient.
Creates a new workspace crate directory (crates/, app/, or tools/) with a Cargo.toml wired to the workspace (inherited package fields, [lints] workspace = true, path deps per the docs/architecture.md dependency arrows), a doc-comment-only lib.rs/main.rs, and the crate's nested CLAUDE.md. Use when a plan calls for standing up a crate that does not exist yet.