← ClaudeAtlas

reviewlisted

Review an openEHR specification document for quality, completeness, and convention compliance in `specifications-XX` repos. This skill should be used when the user asks to review, lint, or quality-check an openEHR spec, validate its conventions, or run a pre-release review. Not for archetype/template review (openehr-assistant plugin), the governance process (use governance), or non-openEHR documents.
openEHR/ai-plugins · ★ 2 · Code & Development · score 75
Install: claude install-skill openEHR/ai-plugins
# openEHR Specification Document Review This skill performs a structured review of an openEHR specification document against the conventions used across all `specifications-XX` repositories. ## Review Process 1. **Identify the target** — determine the spec directory (e.g., `docs/ehr/`) and read the key files 2. **Run each check category** — work through the full catalog in `references/check-catalog.md`, collecting findings as ERROR, WARNING, or INFO 3. **Present findings** grouped by category with `file:line` references 4. **Propose fixes** for ERRORs and WARNINGs (only modify files if asked) ## Pre-Review: File Discovery Read these files for the target spec: - `master.adoc` — main entry point - `manifest_vars.adoc` — per-document variables - `master00-amendment_record.adoc` — amendment record - `master01-preface.adoc` — preface - At least 2-3 chapter files (`master02-*.adoc`, etc.) - The component's `manifest.json` (in the repo root) Also reference the shared infrastructure: - `specifications-AA_GLOBAL/docs/boilerplate/global_vars.adoc` - `specifications-AA_GLOBAL/docs/references/reference_definitions.adoc` ## Check Categories Run all eight categories. The full check list — each with an ID, severity, and condition — is in **`references/check-catalog.md`**; load it when performing a review. | # | Category (ID prefix) | Covers | |---|----------------------|--------| | 1 | Document Structure (STRUCT) | `master.adoc` include order, required files, section scaffolding