A documentation review process that compares the project’s documentation with its source code and creates missing README files, API documentation, or guides.

Use it to find documentation gaps, verify claims against the code, and generate the missing material.

It helps prevent documentation from becoming inaccurate or incomplete as the code changes.

ds-docs — Skill for Claude Code and Codex by sungurerdim/dev-skills

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 sungurerdim/dev-skills --skill ds-docs

Clone the repo

git clone --depth 1 https://github.com/sungurerdim/dev-skills

Made for: Claude Code, Codex.

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/sungurerdim/dev-skills/ds-docs/github.svg)](https://agentmods.dev/skills/sungurerdim/dev-skills/ds-docs)

Your own site

<a href="https://agentmods.dev/skills/sungurerdim/dev-skills/ds-docs"><img src="https://agentmods.dev/badge/skills/sungurerdim/dev-skills/ds-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sungurerdim/dev-skills/ds-docs"><img src="https://agentmods.dev/badge/skills/sungurerdim/dev-skills/ds-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 5,262 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.

Model	Per session	Once invoked
Fable 5.1	$0.00064	$0.05262
Opus 5.5	$0.00026	$0.02105
Sonnet 5.5	$0.00013	$0.01052
Haiku 4.5	$0.00006	$0.00526

Measured 1mo ago against content hash aeb56325c896, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ds-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 1mo 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.

ds-docs/SKILL.md · 228 lines

How it starts

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

/ds-docs

Documentation drifts from code the moment it's written, decisions evaporate with no paper trail, and AI-harness context files silently bloat past the point they help. This skill detects the gaps, verifies claims against source code, tracks architecture decisions, and keeps harness context files signal-dense.

Documentation & Decision Integrity — doc-drift verification, gap generation, ADR tracking, harness-context-file curation.

Completion Evidence — applies to every phase: Report done/OK only with the machine-checkable evidence the gates name — the exact command run and its observed output (or file:line diff). Missing evidence → report INCOMPLETE plus what is missing. Self-assessment is never evidence. (This band repeats at file end by design — both copies are normative.)

Triggers

User runs /ds-docs, asks to check, generate, or improve documentation, asks "what docs are missing" / "is the README up to date", or asks to verify documentation accuracy against source code

Triggers — INVOKE / DON'T INVOKE

INVOKE	DON'T INVOKE
"audit documentation gaps", "is README up to date"	"audit code quality" (→ ds-review)
"generate API docs from source"	"write marketing copy / landing page" (→ external / manual)
"verify docs against code (no drift)"	"test the documented examples" (→ ds-test)
"write ADR for this decision"	"research industry best practices" (→ ds-research)
"audit/trim my CLAUDE.md or AGENTS.md", "optimize my agent instructions file"	"configure harness permissions or install tools" (→ ds-rig)

Contract

Dimensions: B5 (getting-started), B6, C3 (templates), C5 (deprecation), A10 (API doc completeness), D10 (support docs)

Every generated sentence must earn its place — no filler, marketing language, or obvious statements.
Only generates/modifies documentation files — never touches source code.
Verifies claims against actual source code before writing.
Standalone. Uses blueprint profile when available; ds/audit/findings.md only when fresh (git_hash == HEAD AND current run-cycle); own analysis otherwise.
Full accounting enforced: every finding and planned check ends in an explicit disposition (fixed / skipped + reason / only you can do); summary totals balance.
Pre-existing / out-of-scope errors detected during work are NOT skipped — fixed inline or escalated with concrete blocker.
State-exempt: generated docs on disk are the progress record; re-running naturally resumes.

Read the full file on GitHub · 228 lines

Files

What ships with it

10 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.

1mo ago Changed · -94 lines · +25 tokens per session aeb56325c896
1mo ago First seen · 322 lines · 39 tokens per session scan A a61438d2b2bd

Subscribe to this mod's changes

ds-docs is a skill published in the GitHub repository sungurerdim/dev-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 5,262 once invoked, about $0.0003 per session on Opus 5.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-31.

Claude Code ai-agent ai-coding ai-skills code-quality developer-tools

ring:migrating-to-lib-observability

Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…

LerianStudio/ring · 104 tokens

ring:exploring-codebases

Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…

LerianStudio/ring · 91 tokens

ring:searching-code

Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…

LerianStudio/ring · 74 tokens

ring:mapping-streaming-events

Mapping the eventable points in a Lerian Go service where lib-streaming should emit past-tense, durable, tenant-scoped business events, producing a PM-validated event catalog and instrumentation-map.json for ring:instrumenting-streaming-events. Three-pass discovery (Survey, Slice, Mark) with a scope fence and delivery…

LerianStudio/ring · 95 tokens

ring:instrumenting-streaming-events

Instrumenting streaming events: wires lib-streaming event emission end-to-end into a Lerian Go service via a 13-gate cycle (catalog, Builder bootstrap, Emit sites, outbox, HTTP manifest, NoopEmitter fallback, integration and chaos tests), dispatching ring:backend-go under TDD. Consumes the validated…

LerianStudio/ring · 102 tokens

ring:planning-codebase-simplification

Planning a whole-codebase simplification: audits a Go/TS codebase for needless abstraction and emits a KILL/REVIEW/KEEP plan plus a ring:running-dev-cycle task array. Plans only — no edits. Detects single-impl interfaces, pass-through shims, translation-free adapters, and dead-code cascade chains under an inverted…

LerianStudio/ring · 105 tokens