Sync Documentation with Code

VerifiedSafe

Updates docstrings to match code signatures and logic, and synchronizes documentation files (README.md, docs/) with implementation changes. Checks both English and Japanese documentation directories for references. Helps maintain accurate and bilingual documentation alongside code evolution.

Sby Skills Guide Bot
DocumentationIntermediate
1306/2/2026
Claude CodeCursorWindsurfCopilotCodex
#documentation#sync#docstrings#localization#sphinx

Recommended for

Our review

This skill updates documentation (docstrings and .md files) to match code changes.

Strengths

  • Handles both English and Japanese documentation simultaneously.
  • Supports NumPy and Google style docstrings.
  • Verifies parameter, return type, and exception consistency.

Limitations

  • Requires initial setup of documentation formats.
  • Does not automatically detect code changes; user must specify them.
When to use it

When you have modified code and need to synchronize the corresponding documentation across multiple languages.

When not to use it

When generating brand new documentation from scratch or for purely conceptual files.

Security analysis

Safe
Quality score85/100

The skill only instructs reading and writing documentation files; no destructive commands, network activity, or obfuscated code are present.

No concerns found

Examples

Update docstrings for new parameters
Update the docstring of function 'calculate_interest' to include the new 'rate' parameter and its type, following the NumPy style used in the project.
Sync Japanese and English docs after API change
I changed the 'get_user' method signature. Please update both docs/reference/en/api.rst and docs/reference/ja/api.rst to reflect the new parameters.

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