atlas-review

# /atlas-review — is this vault sound right now **This skill writes nothing.** What it produces is one page: what is off, and what call fixes it. Fixing happens after a person has read it and decided. 1. **Two calls** - `validate_vault({})` — frontmatter and relation references - `query_ontology({ operation: 'health' })` — the graph integrity checks Do not `grep` or `sed` the frontmatter directly. You get the same answer more slowly, without relation resolution or schema validation. 2. **Do not report what passed** Listing healthy checks spends the reader's attention and buries the one thing they need to act on. Report **only what needs a hand**. If everything is sound, end in one line — "nothing to fix · N nodes · M relations". 3. **Three things per item** | | | |---|---| | What happened | One plain sentence. Do not paste the check's identifier | | Why it matters | What goes missing or renders wrong if it stays | | The fix | One line the reader can copy and run | The two you will see most: - **Unreachable nodes** (`components`) — a node the project root cannot reach belongs to no project, so it never appears on the map. It exists and is invisible. → `add_relation('<project>', 'domains/<new domain>', 'domains')` - **One-sided relations** (`relation_recommendations`) — a capability declares `domain: X` but `X` does not claim it back. → `add_relation('domains/X', 'capabilities/<capability>', 'capabilities')` 4. **If project meaning is yellow — stop here** Ne...