update-docs

update-docs is a skill for Claude Code from navapbc/digital-service-orchestra. It costs 108 tokens per session (1,184 once invoked), scanned A, original, Apache-2.0.

A documentation update skill that reviews recent code changes and refreshes project documentation such as a README.

In plain words
What is it for?
It is for updating documentation after an epic, merge, or selected range of commits.
Why use it?
It helps keep written project instructions aligned with substantive code changes or completed work.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the dso plugin — 37 skills, 4 commands, 53 agents shipped together

Good fit It is for updating documentation after an epic, merge, or selected range of commits.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add navapbc/digital-service-orchestra
Claude Code
/plugin install dso

Made for: Claude Code.

Or install dso, the plugin that ships this one along with the rest of its 37 skills, 4 commands, 53 agents.

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.

agentmods badge for update-docs

README.md
[![agentmods](https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/update-docs/github.svg)](https://agentmods.dev/skills/navapbc/digital-service-orchestra/update-docs)
Your own site
<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/update-docs"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/update-docs/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.

agentmods 80×15 button for update-docs

Your own site · 80×15
<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/update-docs"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,184 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.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00108 $0.01184
Opus 5 $0.00054 $0.00592
Sonnet 5 $0.00022 $0.00237
Haiku 4.5 $0.00011 $0.00118

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

Security

Grade A, and why

update-docs 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 7d ago.

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.

plugins/dso/skills/update-docs/SKILL.md · 153 lines

How it starts

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

Update Documentation

Invoke the dso:doc-writer agent to review and update project documentation based on recent changes. Accepts an optional commit range to scope the git diff.

Usage

/dso:update-docs                      # Diff scoped to main...HEAD (default)
/dso:update-docs <commit-range>       # Diff scoped to the specified commit range

Examples:

  • /dso:update-docs — updates docs for all commits since main
  • /dso:update-docs HEAD~5..HEAD — updates docs for the last 5 commits
  • /dso:update-docs abc123..def456 — updates docs for a specific range

Step 1: Resolve the Commit Range

Determine the commit range to use:

  • If a <commit-range> argument was provided, use it as-is.
  • Otherwise, default to main...HEAD.
REPO_ROOT=$(git rev-parse --show-toplevel)
COMMIT_RANGE="${1:-main...HEAD}"

Step 2: Gather Context

Collect the inputs the doc-writer agent requires:

# Git diff scoped to the commit range
git diff "$COMMIT_RANGE"

# Recent git log for the range (context for the agent)
git log --oneline "$COMMIT_RANGE"

# Project context
cat "$REPO_ROOT/CLAUDE.md" 2>/dev/null | head -200

If git diff "$COMMIT_RANGE" returns empty output, inform the user:

"No changes found in commit range <commit-range>. Nothing to document."

And stop — do not dispatch the agent.

Step 3: Dispatch dso:doc-writer

Inline dispatch is required — dso:doc-writer is an agent file identifier, NOT a valid subagent_type value. The Agent tool only accepts built-in types (general-purpose, Explore, Plan, etc.).

Read agents/doc-writer.md inline and dispatch as subagent_type: "general-purpose" with model: "sonnet". Pass the agent file content verbatim as the prompt, appending the context below.

Agent tool:
  subagent_type: "general-purpose"
  model: "sonnet"
  prompt: |
    {verbatim content of ${CLAUDE_PLUGIN_ROOT}/agents/doc-writer.md}

    --- PER-RUN CONTEXT ---
context:
  epic_context: |
    ## Commit Range
    <commit-range>

    ## Recent Commits
    <output of git log --oneline for the range>

    ## Project Context (from CLAUDE.md)
    <first 200 lines of CLAUDE.md, or "Not available">

  git_diff: |
    <full output of git diff for the commit range>

Read the full file on GitHub · 153 lines

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.

  1. 7d ago First seen · 153 lines · 108 tokens per session scan A f1d71d5706d9

Subscribe to this mod's changes

update-docs is a skill published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 108 tokens to every session and 1,184 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens