Detecting Doc Bloat

Use when auditing documentation for low-value content — redundant, verbose, duplicated, or past its useful form — proposing pruning/condensing/distillation, and whenever bloat analysis runs programmatically (nightly sweep, PR gate, or a chunk-executor invocation handed its chunk slice) and must emit a structured, parseable proposal. Read-only — it proposes, a human approves, fixing-docs applies.

aj604 Updated
Workbench — five Claude Code skills for shipping with agents

File contents

aj604/toolshed commit 3b3bd18dc3

Frequently asked questions

npx get-skill add aj604/detecting-doc-bloat