Wiki Update

Refresh the existing openwiki/ documentation so it stays accurate after recent repository changes. Update runs must be surgical: touch only what the source changes made stale.

First, read references/core.md in this skill's directory — it defines the quality rules, structure requirements, security rules, and the AGENTS.md/CLAUDE.md reference template that all output must follow.

If openwiki/quickstart.md does not exist, stop and tell the user to run /wiki-init first. If the user gave additional instructions with the invocation, skip the no-op check and treat their instruction as the driver of the update.

Workflow

1. No-op check. Read openwiki/.last-update.json. Skip the entire run — report that no repository changes were detected since the last update and stop without editing anything — when ALL of the following hold:

   • the metadata records a gitHead;
   • git status --short --untracked-files=all is empty (ignoring openwiki/.last-update.json itself);
   • either git rev-parse HEAD equals the recorded gitHead, or every path in git diff --name-only <gitHead>..HEAD is inside openwiki/ (and that list is non-empty).

2. Gather git evidence. Run git status --short, git rev-parse HEAD, and git diff --name-status HEAD. Inspect commits added since the previous successful run: prefer git log <lastGitHead>..HEAD --name-status --oneline; fall back to git log --since <updatedAt> if no gitHead was recorded, or the last 20 commits if there is no metadata at all. Use git show on high-signal commits to understand what actually changed.

3. Build a docs impact plan from the changed source files: source change → docs affected → edit needed → why. Read the affected openwiki/ pages before editing. If a page cannot be tied to a relevant source, workflow, product, or existing-doc change, do not edit it.