garden-docs

Name: garden-docs
Availability: InStock
Author: concordance-co

Audit repository Markdown files against current code and produce citation-backed punch lists.

4|1|Updated May 20, 2026

Search Tags:#documentation #audit #docs #drift #grep #punch-list

Ready to run

npx skills add https://github.com/concordance-co/xenon --skill garden-docs-concordance-co

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: garden-docs
Source: https://github.com/concordance-co/xenon/tree/main/.agents/skills/garden-docs
Command: npx skills add https://github.com/concordance-co/xenon --skill garden-docs-concordance-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Force a focused pass over repo documentation to catch drift, bloat, and stale claims by cross-checking against current code, producing a structured punch list grounded in evidence.

Core Features & Use Cases

Thorough inventory of in-scope Markdown files to surface gaps, redundancies, and outdated claims.
Per-file checks for dead references, layout-claim drift, cross-document contradictions, and documentation bloat.
Generated, citation-backed punch list with actionable remediation steps and suggested owners.

Quick Start

Run the garden-docs audit to inventory in-scope Markdown files, identify dead references and layout drift, and produce a prioritized punch list with citations.

Frequently Asked Questions about garden-docs

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

FAQPage Schema

How do I audit markdown documentation for drift against current code?▼

A documentation drift audit cross-checks in-scope markdown files like AGENTS.md against current code to surface dead references, layout-claim drift, and contradictions. It generates a citation-backed punch list with actionable remediation steps and suggested owners for each file.

What is documentation drift and how do I identify stale repo docs?▼

Documentation drift happens when markdown claims become outdated relative to current code. An audit identifies stale repo docs by inventorying in-scope markdown files, cross-checking them against the codebase, and surfacing dead references, layout-claim drift, and cross-document contradictions.

Can I automatically generate a punch list for fixing documentation bloat?▼

Yes, you can generate a punch list for documentation bloat by running a focused audit across in-scope markdown files. The audit evaluates files for redundancies and outdated claims, producing a citation-backed punch list with actionable remediation steps and suggested owners.

Does the documentation audit work with specific repository layouts and markdown structures?▼

The documentation audit works with specific repository layouts by applying checks across in-scope markdown files including AGENTS.md, methodology, operations, platform, and workspace docs. It identifies layout-claim drift, dead references, and contradictions while honoring documented procedures and anti-patterns.

What is the best way to find dead references in repository markdown files?▼

The best way to find dead references in repository markdown files is to run a documentation audit that cross-checks in-scope markdown against current code. The audit surfaces dead references and cross-document contradictions, producing a citation-backed punch list with actionable remediation steps.