Audit wiki documentation for stale pages, broken links, and structural violations.
npx skills add https://github.com/zoraxl/team-brain --skill wiki-lint-zoraxl
Please help me install this Agent Skill. Skill: wiki-lint Source: https://github.com/zoraxl/team-brain/tree/main/.cursor/skills/wiki-lint Command: npx skills add https://github.com/zoraxl/team-brain --skill wiki-lint-zoraxl
This skill addresses the common issue of wiki rot, where documentation becomes stale, disorganized, or disconnected from the actual implementation, making it difficult for teams to find authoritative information.
Run the wiki-lint skill to audit the current repository wiki and report any structural inconsistencies or stale documentation.
High-intent search queries and answers about installing and using this skill.
To audit wiki documentation for stale pages and broken links, you can run a maintenance validation tool that scans your repository to detect outdated review dates, missing references, and structural violations. This ensures your team wiki remains aligned with implementation reality.
Identifying orphan pages and missing backlinks in a team wiki requires structural auditing across defined namespace zones. This process checks file organization against repository conventions to find disconnected pages and categorize engineering runbooks correctly.
A wiki health monitor detects unsourced claims and open questions by scanning documentation content for unresolved markers and stale information. It flags these areas for human review, ensuring product knowledge remains accurate and authoritative.
Yes, you can check for improper file organization in engineering runbooks and ADRs by validating file placements against established repository conventions. This ensures documents are correctly categorized within the wiki-zone model.
You should run a documentation maintenance audit on your repository wiki after major infrastructure migrations or system architecture updates. This ensures all product knowledge and implementation runbooks are correctly linked and categorized.
Yes, wiki linting works by operating across defined namespace zones to validate structural consistency. It checks alignment between product knowledge and implementation reality, reporting broken links and outdated content within those specific boundaries.
zoraxlRetrieves and synthesizes documentation, architecture decisions, and runbooks from a Markdown wiki repository.
mrfeltonRun six Python scripts to diagnose broken links, orphans, and frontmatter in Ideaverse vaults.
GrassHopper42Automates documentation updates after release using Git diff analysis and Markdown files.
zenobi-usAutomate API documentation creation and maintenance with OpenAPI integration.
