wiki-review

Lint finds what code can check. Deep review sends readers for what it cannot. This skill writes nothing; each finding names the skill that fixes it. The one exception is the repair path: the palette in Obsidian starts a repair work document, and this skill proposes the repairs into it.

Tools: lint, vault, change (progress, propose, on the repair path). Agents: wiki-audit.

Procedure

1. Quick: call lint, with tags when the user names a part of the wiki (a document must hold every tag). Group the findings by check, most severe first, each group with its count and its fix.
2. Deep, on request: send one wiki-audit per tag with more than about 30 topics (waves of eight), each with the tag and the lint findings for it. Take the top-level tags first, from the tag list in vault; split a large tag into its child tags. Merge what the agents return with the lint findings.
3. Tags: read the tag-near findings. Each names two tags that differ only by a plural or a separator, or that hold the same documents. Say which pairs look like one tag.
4. Recommend the next step for each group:
   • knowledge findings (dead-link, uncited, stale, orphan, and the audit's findings) → wiki-edit;
   • schema and duplicate-title → the skill the finding's fix names, which depends on the document's type;
   • tag-near → wiki-edit, with a retag that merges the two, when they mean one thing;
   • repository-behind → repo-ingest;
   • repository-path → repo-link with the new path, repo-unlink, or wiki-edit, as the finding's fix says;
   • up (a self link, a cycle, a source that holds up) → wiki-edit;
   • crowded → wiki-map on the tag of that page, which groups the topics below it under hubs;
   • pending → wiki-sync;
   • untyped → wiki-ingest;

Repair

The palette's "Repair with an agent" message names a repair work document: "Your work document is [[…]] (<id>)".

1. Call lint. Report the counts with change action: progress ("lint: 2 errors, 5 warnings; 6 findings a change repairs").
2. Take every finding a change repairs (the knowledge findings and tag-near of step 4), and build one plan with the procedure of wiki-edit, with a why on every write. Do not stop to ask which findings to repair. List in the plan's notes the findings that need another skill or the user, each with its fix. Report "drafted N writes".
3. Propose with change action: propose and id set to the work document.
4. When no finding is one a change repairs, end the work document with change action: reject and the reason ("lint found nothing a change repairs").

When progress or propose refuses with "the user cancelled …; stop the work", stop at once and say in one line that the user cancelled the repair.

Gate

None, except on the repair path: the gate of wiki-edit. End each task with one or two lines; on the repair path, name the work document.

Hand off

The skills in step 4.