Agent skill

Doc Sync for Agent Manuals

by onevcat in onevcat/Prowl

Keeps an agent-facing documentation set accurate against the implementation through small, diff-driven edits since a committed baseline.

Custom licenceAuto-check passedDevelopment

Install Doc Sync for Agent Manuals

skills CLI
$ npx skills add onevcat/Prowl --skill sync-docs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install onevcat/Prowl sync-docs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/onevcat/Prowl.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/sync-docs .claude/skills/sync-docs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sync-docs
GitHub stars
631
Token cost
~2k tokens
SKILL.md length
774 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
Custom licence

At a glance

Keeps an agent-facing documentation set accurate against the implementation through small, diff-driven edits since a committed baseline.

  • Works in 7 steps: Read the baseline. Open… → Diff the implementation since the… → Map changed source → docs to re-check.… → …
  • Checking whether agent-facing docs still match the implementation
  • SKILL.md covers Guiding principle: be…, Steps and Committing
  • Calls git

What it does

A committed baseline commit hash, read from a sync-meta file, anchors a git diff against the current source tree, and when nothing relevant changed the whole run just reports the docs as up to date and bumps the baseline. Internal refactors, renames, and wording differences are deliberately tolerated, and an edit is only made when a documented fact is now demonstrably wrong, a feature was removed, or a genuinely significant new feature appeared, always as the smallest possible fix to the exact wrong line or cell rather than a reflow or restyle.

When your agent uses it

  • Checking whether agent-facing docs still match the implementation
  • Running a conservative doc sync as part of release prep
  • Updating one wrong fact in a doc without restyling the rest

Example prompts

  • “Check whether the docs are still accurate since the last sync baseline.”
  • “Sync the docs for this release without rewriting anything else.”
  • “Fix the one wrong setting description in the docs and stop there.”

Requirements

  • A git repository with a committed sync baseline (docs/.sync-meta.json)

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Read the baseline. Open docs/.sync-meta.json and read the
  2. Diff the implementation since the baseline. List source files that changed
  3. Map changed source → docs to re-check. Use this table; only open the docs
  4. Verify against the source of truth. For each doc identified, check its
  5. Check internal links if files moved. If you renamed/added/removed any doc
  6. Bump the baseline. Set last_synced_commit (and last_synced_date, note)
  7. Report. Output a short summary

What it can do on your machine

Read from SKILL.md and the folder at commit 386b8d0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Doc Sync for Agent Manuals loads about 2k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 774 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 774 words (~1,964 tokens).

“Keep the agent-facing documentation under docs/ accurate as the implementation evolves. This skill is diff-driven (it only looks at source that changed since a committed baseline) and deliberately conservative (it makes the smallest edits needed to restore accuracy — it…”

— opening of SKILL.md by onevcat, Custom licence
name
sync-docs

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/sync-docs of onevcat/Prowl.

Open the folder on GitHubat commit 386b8d0

Compare with similar skills

Doc Sync for Agent Manuals next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Doc Sync for Agent Manuals compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Doc Sync for Agent Manuals this skillonevcat/Prowl631—~2kAutomated safety check: PassCustom licence
Doc SyncJetBrains/ideavim10k2 repos~2.6kAutomated safety check: PassMIT
Mermaid Diagramsjjmartres/opencode1336 repos~1.9kAutomated safety check: PassMIT
Acquire Codebase Knowledgegithub/awesome-copilot40k1 repos~2.3kAutomated safety check: PassMIT
NeMo Curator Docs MaintenanceNVIDIA-NeMo/Curator1.8k—~4.3kAutomated safety check: PassApache-2.0
Releasejrswab/axe895—~1.4kAutomated safety check: PassApache-2.0

Similar skills

  • Doc Sync

    JetBrains/ideavim

    Official

    Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.

    10k GitHub starsUsed in 2 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Mermaid Diagrams

    jjmartres/opencode

    Helps an agent pick the right Mermaid diagram type and write the syntax for class, sequence, flow, ER, C4, state and other software diagrams.

    133 GitHub starsUsed in 6 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    DevelopmentAuto-check passed
  • Adds, updates, moves and removes pages on the NeMo Curator Fern documentation site, keeping navigation entries, links and redirects in step.

    1.8k GitHub stars~4.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Release

    jrswab/axe

    Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.

    895 GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Compares code changes since the last Git tag with the multilingual docs and CLAUDE.md, then updates them or only reports mismatches with --check-only.

    6.1k GitHub stars~4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from onevcat/Prowl

All 10 skills in this repo
  • Drives and verifies the native macOS Prowl Debug UI through accessibility automation, proving behavior with before-and-after evidence instead of reasoning from code.

    631 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed
  • Prowl Self-Verify

    onevcat/Prowl

    Runs an opt-in end-to-end verification of Prowl changes in a separate debug instance, writing a verification contract first and reporting pass, fail, skipped or inconclusive for every scenario.

    631 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Authors, validates, runs and participates in Prowl Agent Workflows, bundles that orchestrate several live coding agents inside the Prowl macOS app.

    631 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed
  • Runs Prowl's benchmark layers for a branch or release against recorded baselines, only when explicitly asked and the machine is quiet.

    631 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Catches an app's string catalog up with the code once per release: translating new text, pruning unused entries, and flagging unlocalized strings.

    631 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Write AI Doc

    onevcat/Prowl

    Create and maintain curated docs-ai/ records for substantial features and non-trivial, decision-shaping fixes (numbered entries with 000-plan.md before implementation and 001-action.md after).

    631 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Doc Sync for Agent Manuals

What does Doc Sync for Agent Manuals do?

Keeps an agent-facing documentation set accurate against the implementation through small, diff-driven edits since a committed baseline. A committed baseline commit hash, read from a sync-meta file, anchors a git diff against the current source tree, and when nothing relevant changed the whole run just reports the docs as up to date and bumps the baseline. Internal refactors, renames, and wording differences are deliberately tolerated, and an edit is only made when a documented fact is now demonstrably wrong, a feature was removed, or a genuinely significant new feature appeared, always as the smallest possible fix to the exact wrong line or cell rather than a reflow or restyle.

When should I use Doc Sync for Agent Manuals?

Doc Sync for Agent Manuals fits situations like: checking whether agent-facing docs still match the implementation; running a conservative doc sync as part of release prep; updating one wrong fact in a doc without restyling the rest.

How do I install Doc Sync for Agent Manuals in Claude Code?

Run `npx skills add onevcat/Prowl --skill sync-docs -a claude-code`. Or copy the skill folder (.claude/skills/sync-docs in onevcat/Prowl) into .claude/skills/sync-docs in your project. Claude Code loads it when a task matches its description.

How do I install Doc Sync for Agent Manuals in Codex?

Run `npx skills add onevcat/Prowl --skill sync-docs -a codex`. Or copy the skill folder (.claude/skills/sync-docs in onevcat/Prowl) into .agents/skills/sync-docs in your project. Codex loads it when a task matches its description.

Can I use Doc Sync for Agent Manuals in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add onevcat/Prowl --skill sync-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sync-docs, .gemini/skills/sync-docs, .github/skills/sync-docs and .opencode/skills/sync-docs in your project.

What does Doc Sync for Agent Manuals need to run?

Going by SKILL.md and its folder, Doc Sync for Agent Manuals needs the command-line tools its instructions call (git). Our summary lists: A git repository with a committed sync baseline (docs/.sync-meta.json).

Does Doc Sync for Agent Manuals access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Doc Sync for Agent Manuals safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Doc Sync for Agent Manuals use?

Doc Sync for Agent Manuals has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Doc Sync for Agent Manuals use?

About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Doc Sync for Agent Manuals?

Skills that share tags, products or a category with Doc Sync for Agent Manuals: Doc Sync (JetBrains/ideavim, 10k stars), Mermaid Diagrams (jjmartres/opencode, 133 stars), Acquire Codebase Knowledge (github/awesome-copilot, 40k stars) and NeMo Curator Docs Maintenance (NVIDIA-NeMo/Curator, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Doc Sync for Agent Manuals?

onevcat (a GitHub user) maintains it in onevcat/Prowl, which has 631 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 6, 2026.

Source: onevcat/Prowl on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.