wiki-doctor

Audit wiki consistency and verify claims against the codebase.

Updated May 7, 2026

Search Tags:#linting #documentation #audit #drift #wiki #quality-assurance

Ready to run

npx skills add https://github.com/AtaraxiaEpiphany/conductor --skill wiki-doctor-ataraxiaepiphany

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wiki-doctor
Source: https://github.com/AtaraxiaEpiphany/conductor/tree/main/skills/wiki-doctor
Command: npx skills add https://github.com/AtaraxiaEpiphany/conductor --skill wiki-doctor-ataraxiaepiphany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates documentation rot by identifying inconsistencies, stale references, and coverage gaps between your wiki and the actual codebase.

Core Features & Use Cases

Automated Linting: Performs a multi-round, adversarial audit of wiki structure, frontmatter, and link integrity.
Codebase Drift Detection: Compares wiki claims against the current state of the code to surface stale documentation or missing coverage.
Use Case: Before a major release, run this skill to ensure all architectural claims in the wiki are still accurate and that no documentation pages have become orphaned or contradictory.

Quick Start

Run the wiki-doctor skill with the diff command to identify any documentation that has drifted from the current codebase reality.

Frequently Asked Questions about wiki-doctor

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

FAQPage Schema

How do I detect documentation drift between my wiki and codebase?▼

To detect documentation drift, audit wiki consistency by verifying claims against the current codebase. This process surfaces stale references, coverage gaps, and structural drift across project-wide documentation to eliminate documentation rot.

What is automated wiki linting and when do I need it?▼

Automated wiki linting is a multi-round, adversarial audit of wiki structure, frontmatter, and link integrity. You need it before major releases to ensure architectural claims remain accurate and no documentation pages have become orphaned or contradictory.

How do I check for orphaned or contradictory documentation pages?▼

Check for orphaned or contradictory documentation by running an automated health audit across project-wide documentation. This multi-round validation identifies coverage gaps, stale references, and structural drift between your wiki and codebase.

Can I audit wiki frontmatter and link integrity without manual review?▼

Yes, you can audit wiki frontmatter and link integrity without manual review by using automated linting. This performs iterative, multi-round validation and reporting to diagnose documentation health and surface structural inconsistencies.

Do I need doc-linter and wiki-differ agents to perform documentation health audits?▼

Yes, performing iterative documentation health audits requires integration with doc-linter and wiki-differ agents. These dependencies enable the multi-round validation and reporting needed to verify wiki claims against the codebase.

What is the best way to ensure documentation accuracy before a major release?▼

The best way to ensure documentation accuracy before a major release is running an automated health audit to verify all architectural claims in the wiki are still accurate and identify any documentation that has drifted from the codebase reality.