Sync Documentation with Code

VerifiedSafe

Keeps documentation (docstrings, .md files) synchronized with source code implementation. Handles multilingual updates and ensures consistency.

Sby Skills Guide Bot
DocumentationIntermediate
206/2/2026
Claude CodeCursorWindsurfCopilotCodex
#documentation-sync#docstrings#api-reference#code-quality#localization

Recommended for

Our review

This skill updates documentation (docstrings and .md files) to reflect changes in the source code.

Strengths

  • Ensures documentation accuracy
  • Supports bilingual documentation (English and Japanese)
  • Checks both docstrings and external documentation
  • Integrates with build step for verification

Limitations

  • Requires existing documentation format
  • May not handle large-scale refactoring
  • Relies on manual trigger or integration
When to use it

Use this skill when modifying code that has corresponding documentation to keep them synchronized.

When not to use it

Do not use it for initial documentation creation or when the documentation format is non-standard.

Security analysis

Safe
Quality score85/100

The skill instructs reading source code and updating docstrings/documentation files. It does not invoke any executable tools, network calls, or destructive commands. There is no risk of code execution, data exfiltration, or safety bypass.

No concerns found

Examples

Update docstrings after function signature change
Update the docstrings in src/utils.py to match the new function signatures and parameters.
Synchronize README with API changes
Synchronize the README.md with the latest API changes in the codebase, including both English and Japanese versions.
Check and update bilingual docs for new feature
Check and update both English and Japanese documentation files under docs/reference/ for the new feature added in main.py.

name: sync_docs description: ソースコードの実装に合わせてドキュメント (docstring, *.md) を更新する

Sync Documentation

This skill ensures that the documentation is in sync with the actual code implementation.

Instructions

  1. Update Docstrings:

    • Read the target source code.
    • Check if parameters, return types, and exceptions in the docstring match the signature and logic.
    • Update the docstring using the standard format (NumPy or Google style, matching the project).
  2. Update Documentation Files:

    • Check docs/ or README.md for references to the changed code.
    • Crucial: Check both English (docs/reference/en/) and Japanese (docs/reference/ja/) documentation directories.
    • Update tutorials or API references if the usage has changed.
    • If a new feature was added, ensure it is mentioned in the appropriate section in both languages.
  3. Verify:

    • If possible, run the build_docs skill to ensure no syntax errors were introduced in ReStructuredText or Markdown.
Related skills