AgentStack
SKILL verified Apache-2.0 Self-run

Docs Sync

skill-ravisingh11-agent-safe-engineering-docs-sync · by ravisingh11

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, or improve onboarding docs.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-ravisingh11-agent-safe-engineering-docs-sync

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Docs Sync? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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. Report only concrete documentation drift using the shared finding format; persist it only when requested.
  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/references/finding-format.md
  • Verification template: ../_shared/references/verification-template.md

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.