Skip to content
Skills Library
Programming · Review & audit

update-docs

/update-docs

Use to keep docs in sync with code. Detects doc-vs-code drift, surfaces stale claims, applies updates. "Update the docs", "docs are out of date", "sync docs to code".

Repository
sift-coder ↗
Licence
MIT
Last repository change
03.06.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 03.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use to keep docs in sync with code. Detects doc-vs-code drift, surfaces stale claims, applies updates. "Update the docs", "docs are out of date", "sync docs to code".

Triggers from the description

Update the docsdocs are out of datesync docs to code
Original author description

Use to keep docs in sync with code. Detects doc-vs-code drift, surfaces stale claims, applies updates. "Update the docs", "docs are out of date", "sync docs to code".

How it works

  1. Method
  2. Output shape
  3. Rules
  4. Anti-patterns
  5. When NOT to use
  6. Subagent dispatch
  7. Value over native CC
Original SKILL.md headings · 74 lines, 351 words
SKILL.md preview
---
name: update-docs
description: Use to keep docs in sync with code. Detects doc-vs-code drift, surfaces stale claims, applies updates. "Update the docs", "docs are out of date", "sync docs to code".
---

# update-docs

Doc-sync workflow. Doc rot is invisible until someone reads. Mine the rot; fix it.

## Method

1. **Inventory docs.** README, ARCHITECTURE, docs/, CHANGELOG, comments-on-public-API. Skip generated.
2. **Per doc, mine claims:**
   - File paths mentioned → check existence
   - Symbol names mentioned → grep repo
   - Commands mentioned → verify they exist (in package.json scripts, in commands/, in code)
   - Version numbers → match current
   - Configuration keys → match settings.json schema
3. **Find drift.** Each broken claim = stale.
4. **For each stale claim:**
   - Verify it's stale (don't just trust regex)
   - Find current truth
   - Propose update
5. **Apply** approved updates. **Don't blanket-update.** Per-claim review.

## Output shape

```
Docs reviewed:    <count files>
Claims checked:   <count>

Drift found:

  README.md:42      "Run `npm run sync`"
                    Reality: package.json has no `sync` script
                    Suggested: drop the line | OR add the script
                    
  docs/MEMORY.md:15 "src/memory/v2/...""
                    Reality: path doesn't exist; current is src/memory/
                    Suggested: update path

  ARCHITECTURE.md:88 "uses Redis for caching"
                    Reality: code uses in-memory Map; no Redis dep
                    Suggested: remove the line OR add Redis

Approve which to apply: 1, 2, both...
```

## Rules

- **Each finding is reviewed.** Doc updates have human gate.
- **Verify before claiming stale.** False positives erode trust.
- **Suggest, don't assume.** "Update path" might mean "move the code", not "change the doc".
- **Capture findings to memory** so re-runs don't reprobe known good areas.

## Anti-patterns

- Bulk find-replace across all docs without per-claim review
- Removing claims without checking if the underlying code should exist
- Updating docs that are actively being rewritten by someone
- Treating wishlist items in docs as drift

## When NOT to use

- Generated docs (typedoc, swagger-ui) — regen, don't manual-update
- Active doc-write in progress — wait until landed
- One-line README typo — direct edit

## Subagent dispatch

- `Explore` for the source verification
- `Grep` heavily for symbol/path checks
- Memory MCP to skip already-verified areas

## Value over native CC

CC will update a doc on request. CC won't naturally inventory all claims and verify each. The systematic claim-by-claim check IS the value.

Versions

RepositoryScoreLicence
This page · ialameh/sift-coder100MIT
iuliandita/skills100MIT
benweese/playwright-ai-qa-agents100MIT
thefrederiksen/devthrottle100MIT
vercel/next.js100MIT
RubenGlez/rubstack100MIT
peteonrails/voxtype100MIT
tesseron-dev/tesseron100Apache-2.0
tmj-90/gaffer100Apache-2.0

Database snapshot: 13.11.2026 · package version 003ba6ff39bd (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100doc-update
    Use when code has changed and documentation may be out of date — identifies stale docs, finds gaps between implementation and docs, and applies targeted updates.
  • 100plan-docs-sync
    Plan-only audit of documentation against actual code behavior. Use when "docs drift", "sync docs with code", "audit documentation", "stale README", "onboarding docs broken", "phantom docs", or "docs out of date". Decisions/ADRs → docs-adr.
  • 100docs-sync
    Audit and update Argus user-facing docs (README, docs/**/*.md, site/*.html) against the code truth. Detects version drift, command-count drift, i18n parity violations, and stale CLI examples. Use before a release, or any time the user asks to "sync docs", "update docs", "fix…
  • 95doc-sync
    Audit docs against actual code and find drift (wrong / stale / missing claims), report-only. Use when: "do the docs match the code", "check for doc drift", "audit docs vs code", "did this change make docs stale", "doc-sync", "文件跟 code 同步嗎", "查文件有沒有過時", "對照文件與實作", post-merge doc…
  • 100sync-docs
    Use when a behavioral diff may have left docs or CHANGELOG stale, or when tidy targets stale code comments. Applies only safe fixes. Not for roadmap drift: use drift-detect.
  • 100docs-update
    Audit project documentation against the current state of the codebase and produce a revision plan. Reads README and all docs, launches parallel Explore agents to verify claims, diffs documentation vs reality, and applies approved fixes. Use when user says "quality-docs-update",…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.