pdd-doc-gardener

Scan the docs/ directory to detect outdated documentation and code mismatches.

13|3|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill pdd-doc-gardener
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pdd-doc-gardener
Source: https://github.com/wonderslife/pdd-skills-v3/tree/main/skills/core/pdd-doc-gardener
Command: npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill pdd-doc-gardener

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation often drifts out of sync with code and product decisions. The Document Gardener regularly scans the docs/ directory to identify outdated or deprecated documents and triggers maintenance workflows to keep knowledge bases fresh.

Core Features & Use Cases

  • Detect code-doc inconsistencies by cross-referencing documentation references with actual code.
  • Identify outdated comments, broken references, and API doc mismatches to surface actionable cleanup tasks.
  • Integrate with other skills (e.g., pdd-entropy-reduction, pdd-doc-change) to generate PRs or changes that prune or update docs.

Quick Start

Run the scan against the docs/ directory to surface stale documents and propose minimal, evidence-backed edits.

Frequently Asked Questions about pdd-doc-gardener

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

FAQPage Schema
How do I detect documentation inconsistencies with my codebase?

You detect documentation inconsistencies by scanning the docs/ directory and cross-validating content against the codebase to identify outdated comments, broken references, and API mismatches.

What is doc pruning and when do I need to audit my docs?

Doc pruning is the process of identifying and removing outdated or deprecated documentation. You need to audit docs when knowledge bases drift out of sync with code and product decisions across repositories.

How do I automate fixing broken references and outdated API documentation?

Automate remediation by integrating with skills like pdd-entropy-reduction and pdd-doc-change to generate PRs that prune or update docs based on evidence-backed edits surfaced during the scan.

Do I need external tooling to scan for code-document mismatches across repositories?

Minimal external tooling is required to scan for code-document mismatches across repositories. The process natively identifies inconsistencies and surfaces actionable maintenance tasks.

What's the best way to keep documentation fresh and aligned with code changes?

The best way to keep documentation fresh is regularly scanning the docs/ directory to find stale documents and proposing minimal, evidence-backed edits to prune or update the content.