review-wiki-lint

Audit review wiki registry and pattern files for drift and orphan registrations.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/SeoJaeWan/try-claude-code --skill review-wiki-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-wiki-lint
Source: https://github.com/SeoJaeWan/try-claude-code/tree/main/.codex/skills/review-wiki-lint
Command: npx skills add https://github.com/SeoJaeWan/try-claude-code --skill review-wiki-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audits the review wiki for registry drift, broken backlinks, orphan registrations, and stale guidance, then prepares a non-destructive cleanup plan.

Core Features & Use Cases

  • Registry and content validation: verifies wiki/core docs are registered and up-to-date, ensuring reliable navigation and governance.
  • Pattern and backlink checks: inspects raw_sources, backlinks, and taxonomy to highlight inconsistencies without applying changes.
  • Proposed cleanup drafting: generates a structured lint report at wiki/_meta/lint-report.md and waits for explicit user approval before applying any changes.

Quick Start

Run the lint skill to generate a proposed cleanup report for the review wiki, then wait for your approval to apply fixes.

Frequently Asked Questions about review-wiki-lint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect registry drift and orphan registrations in a wiki?

To detect registry drift, audit the wiki registry and core documents to identify orphan registrations and broken backlinks. This process inspects promoted pattern files and stops whenever it encounters unresolved links or content inconsistencies.

What is a non-destructive wiki cleanup plan?

A non-destructive wiki cleanup plan proposes fixes for stale guidance and broken backlinks without applying changes. It generates a structured lint report and waits for explicit user approval before modifying any registry files or promoted patterns.

How do I validate backlinks and taxonomy in wiki documentation?

Validate backlinks and taxonomy by inspecting raw sources and registry references to highlight inconsistencies. The validation enforces guardrails by stopping on unresolved links and requiring a written lint report before proceeding with fixes.

Can I automatically apply fixes after a wiki lint report is generated?

No, you cannot automatically apply fixes after a wiki lint report is generated. The process enforces guardrails by writing the report to a meta directory and waiting for explicit user approval prior to applying any changes to the registry.

Why does wiki validation stop on unresolved links?

Wiki validation stops on unresolved links to enforce strict governance guardrails and prevent silent data loss. Halting the audit ensures all registry drift and broken backlinks are documented in a lint report before cleanup occurs.