health

Scan CAIDE src/ and wiki/ for drift, orphans, broken links, and stale docs.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/ImLp/claude-caide --skill health-imlp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/ImLp/claude-caide/tree/main/.claude/skills/health
Command: npx skills add https://github.com/ImLp/claude-caide --skill health-imlp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The health check identifies drift between the source and wiki, orphaned code files, broken wiki links, undocumented changes, dead code candidates, and stale documentation to keep the CAIDE wiki aligned with the codebase and reduce maintenance overhead.

Core Features & Use Cases

  • Drift detection between src/ and wiki/ to surface inconsistencies.
  • Orphan detection of source files without corresponding wiki pages.
  • Link integrity checks across wiki pages to catch broken references.
  • Documentation freshness verification for updated code vs wiki exports.
  • Actionable reporting appended to wiki/log.md for weekly or post-merge reviews.

Quick Start

Run this health check after major merges or weekly to produce and append a health report to wiki/log.md.

Frequently Asked Questions about health

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

FAQPage Schema
How do I detect drift between my source code and wiki documentation?

To detect source and wiki documentation drift, you can run a health check that scans src/ and wiki/ directories to surface inconsistencies, undocumented changes, and stale documentation. It compares timestamps and link validity to identify misalignments.

What is the best way to find orphaned source files and broken wiki links?

Finding orphaned source files and broken wiki links requires scanning the codebase for source files without corresponding wiki pages and validating internal references. A wiki health check identifies these dead code candidates and broken links across dependencies.

How do I generate an actionable documentation health report for codebase reviews?

Generating an actionable documentation health report involves scanning src/, wiki/, and dependencies to append findings to wiki/log.md. This provides a periodic review of documentation freshness, drift, and link integrity after major merges.

Can I use this wiki health check to verify documentation freshness after a major merge?

Yes, you can use this wiki health check to verify documentation freshness after a major merge. It operates across src/ and wiki/ to check updated timestamps, ensuring code changes are properly reflected in documentation exports.

Does the health check automatically fix broken wiki links and stale documentation?

No, the health check does not automatically fix broken wiki links or rewrite stale documentation. It reads src/ and wiki/ to assess consistency and reports findings to wiki/log.md without writing or modifying any wiki pages.