Polaris: Skill for Claude Code

Wiki Sync

$wiki-sync maintains the derived Living Entity Wiki around a specific change.

It is not a whole-wiki audit. The $wiki-lint skill owns the separate repository-wide audit and is not invoked as part of $wiki-sync.

authoritative architecture + implementation evidence
                    ↓
               wiki/entities/

Never modify authoritative sources merely to make them agree with the wiki.

Context Economy

Preserve correctness while minimizing rediscovery.

• Reuse affected entities, governing authorities, source conclusions, and architecture context already established by the parent workflow or an earlier $wiki-sync pass.
• Search before reading. Locate the relevant claim, citation, symbol, or call site, then read the smallest useful surrounding range. Expand only when relevant behavior is distributed.
• Do not reread unchanged authority already established in the current workflow unless new evidence creates ambiguity or contradiction.
• On the post-change pass, start from the implementation diff and reuse the pre-change entity/source set. Expand only when the diff crosses another boundary or introduces new evidence.
• Do not read wiki/log.md until a durable wiki mutation requires a log entry or its history is specifically needed.
• Load wiki/_schema.md, wiki/_template.md, unrelated entities, and topology rules only when entity creation/topology is actually in play.

Whole-file reads are exceptional: use them only when relevant knowledge or behavior cannot be understood from targeted regions.

When This Runs

Invoke $wiki-sync:

1. before and after a substantive source-code change;
2. after substantive creation, editing, or reclassification involving docs/current/ or docs/proposed/;
3. after an ADR is created, substantively edited while proposed, or changes status through $to-adr-doc;
4. when entity topology or Boundary Rationale changes.

These triggers apply inside parent workflows such as $implement-ticket.