skill-doc-sync

skill-doc-sync is a skill for Claude Code from nyldn/claude-octopus. It costs 28 tokens per session (2,243 once invoked), scanned A, original, MIT.

A post-release process for keeping project documentation accurate after code changes. It scans Markdown files, compares them with the code diff, and checks for contradictions.

In plain words
What is it for?
Use it after code is committed and a pull request is created to update factual documentation, check consistency, append changelog information, and update the pull request description.
Why use it?
It reduces the chance that documentation describes old behavior or conflicts with other project documents.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions CLAUDE.md.

Part of the octo plugin — 69 skills, 106 commands, 10 agents, 18 hooks shipped together

Good fit Use it after code is committed and a pull request is created…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nyldn/claude-octopus/skill-doc-sync
About the project

Claude Octopus is an orchestration project that sends research, design, and coding tasks to Claude Code and other AI model providers so their results can be compared. Developers use it for multi-model work, disagreement detection, reviews, persistent context, and an optional workflow that moves from discovery through delivery. The catalogue entries are its commands, skills, agents, instructions, hooks, plugins, and settings.

nyldn/claude-octopus · 4,050 stars · on GitHub · reddit.com

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 nyldn/claude-octopus --skill skill-doc-sync
Clone the repo
git clone --depth 1 https://github.com/nyldn/claude-octopus

Made for: Claude Code.

Or install octo, the plugin that ships this one along with the rest of its 69 skills, 106 commands, 10 agents, 18 hooks.

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 skill-doc-sync

README.md
[![agentmods](https://agentmods.dev/badge/skills/nyldn/claude-octopus/skill-doc-sync.svg)](https://agentmods.dev/skills/nyldn/claude-octopus/skill-doc-sync)
Your own site
<a href="https://agentmods.dev/skills/nyldn/claude-octopus/skill-doc-sync"><img src="https://agentmods.dev/badge/skills/nyldn/claude-octopus/skill-doc-sync.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,243 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.00028 $0.02243
Opus 5 $0.00014 $0.01122
Sonnet 5 $0.00006 $0.00449
Haiku 4.5 $0.00003 $0.00224

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

Security

Grade A, and why

skill-doc-sync 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.

.claude/skills/skill-doc-sync/SKILL.md · 260 lines

How it starts

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

Post-Ship Documentation Synchronization

Automated documentation synchronization for the Deliver phase. After code is committed and a PR is created, this skill reads all .md files in the project, cross-references the diff, auto-updates factual content, checks cross-doc consistency, and updates the PR body.


Caps

  • Max 30 doc files scanned — skip files beyond the cap, warn the user
  • Never clobber CHANGELOG — append only, never delete existing entries
  • Ask user before changing narrative/philosophy sections — risky changes require confirmation

Step 1: Discover Docs

Find all .md files in the project root (max depth 2), skipping node_modules/ and .git/.

# Discover all markdown files (max depth 2, skip noise directories)
DOC_FILES=$(find . -maxdepth 2 -name '*.md' \
  -not -path './node_modules/*' \
  -not -path './.git/*' \
  -not -path './vendor/*' \
  -not -path './.claude/*' \
  2>/dev/null | head -30)

DOC_COUNT=$(echo "$DOC_FILES" | wc -l | tr -d ' ')
echo "Found $DOC_COUNT doc files to scan (cap: 30)"

if [[ "$DOC_COUNT" -ge 30 ]]; then
  echo "WARNING: Doc file cap reached (30). Some files may be skipped."
fi

Read each discovered doc file so you have their current content in context.


Step 2: Cross-Reference Diff

Run git diff --stat HEAD~1 (or diff against the base branch if on a feature branch) to identify which files changed and what content may now be stale in each doc.

# Get the diff stat to identify changed files
BRANCH=$(git rev-parse --abbrev-ref HEAD)
if [[ "$BRANCH" == "main" || "$BRANCH" == "master" ]]; then
  DIFF_STAT=$(git diff --stat HEAD~1)
  DIFF_FULL=$(git diff HEAD~1)
else
  BASE_BRANCH=$(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null)
  DIFF_STAT=$(git diff --stat "$BASE_BRANCH"..HEAD)
  DIFF_FULL=$(git diff "$BASE_BRANCH"..HEAD)
fi

echo "$DIFF_STAT"

For each doc file, check whether any paths, function names, counts, or version numbers mentioned in the doc were affected by the diff.

Read the full file on GitHub · 260 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 · 260 lines · 28 tokens per session scan A 45e433ffc37e

Subscribe to this mod's changes

skill-doc-sync is a skill published in the GitHub repository nyldn/claude-octopus (4,050 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 2,243 once invoked, about $0.0001 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-08-30.

Related

Other skills, from other repositories

ai-context

Generates, updates, and audits AGENTS-first AI IDE context files. Builds canonical AGENTS.md plus thin bridges for Claude Code, Cursor (modern .cursor/rules/.mdc), Copilot, Cline (.clinerules/ directory), Windsurf, Gemini CLI, Codex CLI, and OpenCode. Use for creating, regenerating, fixing, or promoting context files…

littlebearapps/contextdocs · 86 tokens

architecture

This skill should be used when managing Architecture Decision Records or C4 diagrams.

jikig-ai/soleur · 17 tokens

linear-fetch

This skill should be used when a user input contains a Linear issue reference (e.g., SOL-39 or linear.app/.../issue/ ) and the downstream agent needs the screenshots embedded in the issue as visual context.

jikig-ai/soleur · 48 tokens

legal-generate

This skill should be used when generating draft legal documents for a project or company. It gathers company context interactively, invokes the legal-document-generator agent, and writes markdown output.

jikig-ai/soleur · 39 tokens

kb-search

This skill should be used when searching the knowledge base for files matching keywords or YAML frontmatter facets (tag, category) across domains.

jikig-ai/soleur · 30 tokens

growth-strategist

Use this agent when you need content strategy analysis including keyword research, content auditing for search intent alignment, content gap analysis, and GEO/AEO auditing at the content level. Use seo-aeo-analyst for technical SEO audits; use competitive-intelligence for strategic competitor monitoring; use…

jikig-ai/soleur · 78 tokens