After ANY code change, sweep the diff for documentation that just went stale. Use when finishing an edit, before a commit/PR, or when the completion gate blocks — it turns "did I forget a doc?" into a mechanical checklist. Backed by `forge docs sync`.
Scanned 9/22/2026
Install to Claude Code
npx -y skills add CodeWithJuber/forgekit --skill sync-docs --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Sync Docs?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/codewithjuber-sync-docs)More formats (shields.io, HTML) on the badges page.
---
name: sync-docs
description: After ANY code change, sweep the diff for documentation that just went stale. Use when finishing an edit, before a commit/PR, or when the completion gate blocks — it turns "did I forget a doc?" into a mechanical checklist. Backed by `forge docs sync`.
---
# sync-docs — make every artifact true again
A code change isn't done while prose still describes the old behavior. The sweep is
mechanical: diff → identifiers (paths, definitions, called symbols — added AND removed)
→ every doc artifact is scanned and answers one of three ways.
## Do
1. Run the sweep:
```bash
forge docs sync # human report; --json for tooling; --base <ref> to widen
```
2. Read the verdicts:
- **STALE** — the doc mentions a changed identifier (each hit cited `file:line`).
Open it, update the mention to match reality — or say explicitly why it's fine.
- **UPDATED** — the doc already moved with this diff. Nothing owed.
- **VERIFIED-UNAFFECTED** — zero mentions; the reason is recorded. Checked, not assumed.
3. Re-run until STALE is empty (or every remaining hit is justified out loud).
4. CHANGELOG is exempt by design (append-only history) — add a NEW entry for
user-facing changes instead of editing old ones.
## Rules
- Never mark a doc unaffected by assumption — that's exactly what the sweep verifies.
- Big diff? Delegate this whole loop to the `doc-sync` agent to keep your context clean.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!