docs-change-impactlisted

Checks whether a documentation change that already shipped actually helped — comparing how visits went on the edited pages against the pages nobody touched, before and after the commit. Answers "did that rewrite work", "was the restructure worth it", "should we do more of this", and closes the loop that every other docs audit leaves open by recommending edits and never looking back. Use before repeating a kind of change you have made before, after acting on an audit's recommendation, and in a retro on a docs push. Reports what the evidence supports; it edits nothing.
Docsbook-io/docs-skills · ★ 1 · Data & Documents · score 75

Install: claude install-skill Docsbook-io/docs-skills

# docs-change-impact Every other skill in this catalog runs in one direction. It finds something wrong, recommends a change, and stops. Nothing goes back afterwards to ask whether the change helped — so the same recommendation can be made twice, with the same confidence, on the same page, and nobody is any wiser the second time. That open loop has a specific cost. Teams keep doing the kind of edit that feels productive — splitting long pages, adding "next steps" blocks, rewriting intros — with no idea which of those ever moved anything. And a change that made things *worse* is indistinguishable from one that did nothing, because both look like "we shipped it and moved on". This skill closes the loop. It takes a change that already shipped and asks a narrow, checkable question: **did visits to the pages you edited go better than visits to the pages you did not?** **Mode: audit.** It produces a verdict and evidence. It changes no content — the decision about what to do with the answer is the human's, and the most valuable finding this skill produces ("that did nothing, stop doing it") is not an edit at all. ## When to run - **Before repeating a kind of change.** The highest-value moment. You are about to restructure six more pages the way you restructured one last month — check what the first one did first. - **After acting on an audit's recommendation.** Any skill here can tell you a page has a dead-end problem. Only this one tells you whether your fix worked. - **