garden-docs

Validate documentation alignment with current code structure after changes.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/identity16/skills --skill garden-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: garden-docs
Source: https://github.com/identity16/skills/tree/main/plugins/just-useful-plugin/skills/garden-docs
Command: npx skills add https://github.com/identity16/skills --skill garden-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill ensures documentation stays aligned with code during changes and maintains the knowledge base as the system of record.

Core Features & Use Cases

  • Doc-code alignment checks to verify docs reflect current code structure after changes and refactors.
  • Knowledge base integrity to detect orphan references, broken links, and misplaced context in CLAUDE.md vs docs/.
  • Governance workflow to enforce triggers, references, and organization across the repository.

Quick Start

Run the garden-docs workflow to verify docs stay in sync with code after structural changes.

Frequently Asked Questions about garden-docs

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

FAQPage Schema
How do I check if my documentation is out of sync with my code structure?

Keep documentation in sync with code by running a validation workflow that checks for doc-code misalignments after structural changes. It verifies that references exist, detects orphaned files, and ensures all docs align with the repository's real structure.

What is the best way to detect orphaned references and broken links in a knowledge base?

Detect orphaned references and broken links by running a knowledge base integrity check that validates CLAUDE.md triggers against the docs/ organization. This governance workflow enforces that all references exist and no orphaned files remain across the repository.

How do I maintain documentation accuracy after refactoring my repository?

Maintain documentation accuracy after refactoring by applying a doc-code alignment check that verifies docs reflect the current code structure. This workflow covers references, CLAUDE.md triggers, and docs/ organization to enforce structural consistency during periodic maintenance.

Do I need a governance workflow to enforce documentation organization in my repository?

A governance workflow is needed to enforce triggers, references, and organization across your repository. It ensures CLAUDE.md and docs/ files align with the real code structure, preventing orphaned files and broken references during structural changes.

When should I run documentation validation checks during development?

Run documentation validation checks during structural changes, periodic maintenance, and knowledge base design. This ensures docs stay aligned with code after modifications and maintains the knowledge base as the system of record by catching misalignments early.