docs-sync

Compare repository behavior and structure against README, AGENTS, architecture docs, setup docs, and operational docs to find and repair documentation drift.

Skill by ravisingh11

IndexedMIT★ 5

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/ravisingh11-docs-sync

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Compare repository behavior and structure against README, AGENTS, architecture docs, setup docs, and operational docs to find and repair documentation drift. Use when a user asks to update docs, audit docs against code, improve onboarding docs, or as part of $full-test-suite.

Use cases: testing, security

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/docs-sync

What's inside

Skill name: docs-sync
Description: Compare repository behavior and structure against README, AGENTS, architecture docs, setup docs, and operational docs to find and repair documentation drift. Use when a user asks to update docs, audit docs against code, improve onboarding docs, or as part of $full-test-suite.
License: MIT
Instructions: 31 lines in SKILL.md · view on GitHub

Files (2)

SKILL.md
openai.yaml · agents/

SKILL.md (first lines)

# Docs Sync

Find documentation drift by comparing actual code and workflows against the repo's written guidance.

## Workflow

1. Identify the source-of-truth docs: README, AGENTS, architecture docs, setup guides, env samples, and operations notes.
2. Compare current code paths, commands, config names, and flows against those docs.
3. Promote only concrete doc drift into `project-audit-findings.md`.
4. When the correct wording is clear from repo evidence, patch docs directly if fixing is in scope.
5. Record verification as explicit reasoning when no automated test applies.

## Focus Areas

- wrong setup or build commands
- missing environment variables or permissions
- stale architecture or ownership descriptions
- outdated flow descriptions after product or API changes
- docs that tell operators to do unsafe or incomplete steps

## Rules

- Prefer exact patches over vague doc recommendations.
- Do not invent product intent; derive it from code or mark `needs-context`.

## References

- Finding format: `../_shared-project-ops/references/finding-format.md`
- Verification template: `../_shared-project-ops/references/verification-template.md`

From ravisingh11/ai-software-toolkit, MIT.

Signals

Stars: 5
Forks: 10
Open issues: 0
Last commit (this folder): Aug 27, 2026 (2 months ago)
Last release: Oct 23, 2026 (5 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/ravisingh11/ai-software-toolkit
Website: ravisingh11.github.io/ai-software-toolkit/
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from ravisingh11

Cite this page

docs-sync skill. Agent Mart. https://agentmart.dev/skills/ravisingh11-docs-sync (last updated 2026-10-24)