gardening-skills-wiki

Health checking automates validation of your documentation structure by detecting broken links, naming inconsistencies, missing fields, and cross-reference errors. Run periodic scans to catch issues before they degrade your knowledge base and reduce searchability across your skill library.

Wiki maintenance requires validating frontmatter fields (name, description, when_to_use, version), ensuring active-voice naming conventions, verifying all cross-references resolve correctly, and confirming the INDEX stays synchronized. Automation catches these issues systematically during skill additions, removals, or reorganizations.

Broken link detection scans your entire documentation structure to find dangling references and isolated skill entries that lack inbound links. This reveals coverage gaps and orphaned content that degrades discoverability, helping you consolidate or improve documentation before users encounter dead ends.

Yes, automation enforces naming consistency and validates required fields through bash-based scripts and frontmatter checks. Consistent naming, descriptions, and metadata improve search relevance and reduce confusion when teams access the skills library.

Run health checks whenever you add, remove, or reorganize skills, or on a regular maintenance schedule to detect drift over time. Proactive scanning prevents knowledge rot and keeps your documentation a reliable resource as your skill library grows.