A documentation workflow for keeping a repository’s README files, guides, and code maps aligned with the code. It uses repository evidence and marks missing details instead of guessing.

Use it after code changes, to find gaps between code and documentation, or to prepare focused documentation patches for libraries, services, command-line tools, or monorepos.

It helps prevent documentation from becoming outdated or describing APIs, commands, or settings that do not exist.

update-doc — Skill for Claude Code by johnqtcg

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add johnqtcg/awesome-skills --skill update-doc

Clone the repo

git clone --depth 1 https://github.com/johnqtcg/awesome-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/update-doc/github.svg)](https://agentmods.dev/skills/johnqtcg/awesome-skills/update-doc)

Your own site

<a href="https://agentmods.dev/skills/johnqtcg/awesome-skills/update-doc"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/update-doc/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/johnqtcg/awesome-skills/update-doc"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/update-doc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,488 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00048	$0.04488
Opus 5	$0.00024	$0.02244
Sonnet 5	$0.00010	$0.00898
Haiku 4.5	$0.00005	$0.00449

Measured 9d ago against content hash 9b909fef0fa7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

update-doc scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

The scan reads SKILL.md. This mod also ships 9 executable files (scripts/discover_doc_scope.sh, scripts/grade_doc_update.py, scripts/run_live_eval.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/update-doc/SKILL.md · 450 lines

How it starts

The opening of the file, as written. The whole thing — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Update Docs

Synchronize documentation with repository evidence and avoid stale or speculative content.

Quick Reference

If you need to…	Go to
Update README/docs after a code change (default workflow)	§Pre-Update Gates → §Output Mode Routing → §Standard Workflow
Find what actually changed	§1) Scope Discovery
Decide which command belongs in the doc	§4) Command Source Resolution
Choose the right doc structure for project type	§Project-Type Guidance + Load `references/project-routing.md`
Get the per-language evidence commands	Load `references/evidence-commands.md`
Check docs-drift: find gaps between code and docs	§Quality Scorecard (12 Checks) + Load `references/update-doc.md`
Add CI checks to catch docs drift automatically	Load `references/ci-drift.md`
Understand what to mark vs. invent (`Not found in repo`)	§Hard Rules

Hard Rules

Use repository files as the only source of truth.
Mark missing information as Not found in repo.
Do not invent APIs, routes, env vars, ports, jobs, or dependencies.
Prefer minimal patches by default; preserve existing doc structure unless user requests restructure.
Use diff-scoped updates first; avoid unrelated bulk rewrites.
Keep output scannable: headings + concise bullets + short runnable command blocks.
Keep internal workflow markers out of user-facing docs by default. Verification labels, scorecards, and evidence tables belong in the assistant response unless the user explicitly wants them in the document.
Do not add self-explanatory audience labels or author commentary to top-level docs unless they materially help readers.

Pre-Update Gates (Mandatory)

1) Scope Discovery

Run the bundled discovery script before reading any document:

bash "${CLAUDE_SKILL_DIR}/scripts/discover_doc_scope.sh" --base <ref>

${CLAUDE_SKILL_DIR} expands to this skill's own directory. Two separate version gates apply, and they are not the same number:

Read the full file on GitHub · 450 lines

Files

What ships with it

27 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 450 lines · 48 tokens per session scan A 9b909fef0fa7

Subscribe to this mod's changes

update-doc is a skill published in the GitHub repository johnqtcg/awesome-skills (30 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 4,488 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Claude Code Writing and docs agents ai-assistant ai-skills anthropic developer-tools

security-compliance

Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.

sangrokjung/claude-forge · 56 tokens

stride-analysis-patterns

Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.

sangrokjung/claude-forge · 30 tokens

cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…

sangrokjung/claude-forge · 183 tokens

manage-skills

A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.

sangrokjung/claude-forge · 54 tokens

blind-spot-pass

Use before starting work in a domain you don't know well, to surface the "unknown unknowns" — the things you don't even know to ask about — and learn just enough to prompt and decide well. Implements the "blind spot pass" pattern from Anthropic's Fable "finding your unknowns" field guide. Triggers when you say "I'm…

sangrokjung/claude-forge · 221 tokens

skill-factory

A workflow that examines completed session work and turns reusable patterns into Claude Code skills.

sangrokjung/claude-forge · 122 tokens