groom-knowledge-base

Validate and fix broken links and structure in repository documentation.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ngareleo/xstream --skill groom-knowledge-base
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: groom-knowledge-base
Source: https://github.com/ngareleo/xstream/tree/main/.claude/skills/groom-knowledge-base
Command: npx skills add https://github.com/ngareleo/xstream --skill groom-knowledge-base

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It keeps the project documentation in sync with actual code and file structures, reducing manual oversight and preventing inconsistencies.

Core Features & Use Cases

  • Documentation Grooming: Checks and fixes stale file paths, missing README entries, and outdated links within the docs/ directory.
  • Structural Integrity: Validates folder and file presence, ensuring all referenced docs exist and are properly documented.
  • Proactive Reporting: Identifies broken links, orphaned files, and structural issues that require human review to maintain documentation accuracy.

Quick Start

Run /groom-knowledge-base to analyze and correct the docs structure, update links, and prepare reports for review.

Frequently Asked Questions about groom-knowledge-base

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

FAQPage Schema
How do I fix broken links and stale file paths in my project documentation?

To fix broken links and stale file paths in project documentation, you can automate repository grooming to validate folder structures, correct outdated references, and ensure documentation consistency with your actual codebase.

What is the best way to keep documentation in sync with actual code and file structures?

Keeping documentation in sync with code requires treating code as the source of truth. Automating documentation maintenance validates structural integrity and proactively identifies orphaned files or outdated links requiring human review.

Can I automatically validate the structural integrity of my docs folder?

Yes, you can validate the structural integrity of a docs folder by running an automated grooming process that checks for missing README entries, verifies file presence, and ensures all referenced documents actually exist.

Does documentation grooming update non-code coverage aspects automatically?

Documentation grooming does not update non-code coverage aspects automatically. It enforces code as the source of truth for structural validation, requiring external manual updates for any documentation content not directly tied to code paths.

How do I identify orphaned files and structural issues in my repository documentation?

To identify orphaned files and structural issues in repository documentation, run an automated analysis that proactively reports broken links, missing entries, and file structure inconsistencies for your review.

Do I need to manually review broken links found during documentation maintenance?

Yes, manual review is required for broken links found during documentation maintenance. The automated process identifies and reports structural issues and orphaned files, but human oversight ensures overall documentation accuracy.