Update Documentation

VerifiedCaution

One-click command to update all project documentation after code changes. Synchronizes KNOWLEDGE_BASE.md, README.md and README_ZH.md.

Sby Skills Guide Bot
DocumentationIntermediate
306/2/2026
Claude Code
#documentation#update#sync#code-changes

Recommended for

Our review

Updates all project documentation after code changes in one command.

Strengths

  • Automates updates across multiple documentation files
  • Verifies documented commands work via tests
  • Syncs English and Chinese README versions
  • Leverages git to detect changes accurately

Limitations

  • Requires existence of KNOWLEDGE_BASE.md, README.md, and README_ZH.md
  • Relies on git analysis which may miss subtle changes
  • Only syncs Chinese translation, not other languages
When to use it

After any user-facing change like new adapters, CLI commands, or config format modifications.

When not to use it

For purely internal changes or when documentation maintenance is not a priority.

Security analysis

Caution
Quality score80/100

The skill runs `npm test`, which executes code from the project's test suite. While this is a common development practice, it could inadvertently cause harm if the test suite contains destructive commands. No other risky operations are present, and the purpose is legitimate (documentation update).

Findings
  • Executes `npm test` which runs arbitrary test code from the repository; could potentially have unintended side effects if the test suite is malicious or buggy.

Examples

Add OpenCode support
Update all docs after adding OpenCode support
Change CLI command flags
I've modified the CLI command flags for the build command. Please update all project documentation accordingly.
Update config format
The configuration format has changed to include a new 'timeout' field. Update all relevant documentation files.

name: update-docs description: Update all project documentation after code changes.

Update Documentation

Instructions

One-click command to update all project documentation after code changes.

Steps

  1. Analyze Changes

    • Check git status for modified files
    • Review recent commits if no uncommitted changes
    • Identify what documentation needs updating
  2. Update KNOWLEDGE_BASE.md

    • Run the update-knowledge-base skill
    • Document any architectural or feature changes
  3. Update README.md

    • Add new features or commands
    • Update examples if API changed
    • Ensure accuracy of all documented commands
  4. Sync README_ZH.md

    • Run the sync-readme skill
    • Ensure Chinese documentation matches English
  5. Verify

    • Run tests to ensure nothing broken: npm test
    • Check that all documented commands work
    • Review diff before committing

When to Use

  • After adding a new adapter
  • After adding or modifying CLI commands
  • After changing the configuration format
  • After any user-facing changes

Output

All documentation files updated and in sync:

  • KNOWLEDGE_BASE.md (if exists)
  • README.md
  • README_ZH.md

Examples

Request: Update all docs after adding OpenCode support Result: KNOWLEDGE_BASE.md, README.md, and README_ZH.md all updated

Related skills