Docs Sync

VerifiedSafe

Check and update repository documentation when behavior, commands, or validation evidence changes.

Sby Skills Guide Bot
DocumentationIntermediate
107/23/2026
Claude CodeCursorWindsurf
#docs-sync#readme#decision-records#code-documentation-sync

Recommended for

Our review

Updates project documentation in sync with code changes, including README, DECISIONS.md, and ADRs.

Strengths

  • Ensures code and documentation stay consistent
  • Prevents burying decisions only in chat
  • Provides clear rules for what and when to update

Limitations

  • Does not rewrite unrelated documentation
  • May require human review for tone and clarity
  • Focuses on operational docs, not user-facing manuals
When to use it

When changing public behavior, commands, validation, or making durable decisions that affect the codebase.

When not to use it

For cosmetic or unrelated documentation improvements not tied to recent code changes.

Security analysis

Safe
Quality score90/100

The skill only provides documentation update guidelines with no executable commands, network activity, or file system modifications beyond editing docs, presenting no security risk.

No concerns found

Examples

Update README after adding a new command
I added a new CLI command `analyze` that takes a file path and outputs statistics. Update README.md and any relevant docs under docs/ to document this command, including usage example and output format.
Record a decision in DECISIONS.md
We decided to switch from using SQLite to PostgreSQL for the data store. Add a new decision record in docs/DECISIONS.md explaining the rationale, date, and what remains out of scope.

name: docs-sync description: Use when behavior, setup, validation, public wording, data provenance, or workflow commands change and repository documentation may need to be updated.

Docs Sync

  • Check README.md, docs/DECISIONS.md, relevant docs under docs/, and any ADRs.
  • Update docs in the same change as code when public behavior, commands, assumptions, or validation evidence changes.
  • Record durable decisions in docs/DECISIONS.md or a new ADR; do not bury decisions only in chat.
  • Keep docs concise and operational: what changed, why, how to run it, and what remains out of scope.
  • Avoid rewriting unrelated docs or changing historical decisions except to add a dated superseding note.
Related skills