sync-api-docs

Compare server endpoints and SDK interfaces against OpenAPI and SDK docs.

84|7|Updated Feb 24, 2025
One-click install
npx skills add https://github.com/not-elm/desktop-homunculus --skill sync-api-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-api-docs
Source: https://github.com/not-elm/desktop-homunculus/tree/main/engine/.claude/skills/sync-api-docs
Command: npx skills add https://github.com/not-elm/desktop-homunculus --skill sync-api-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

API documentation often drifts from the actual server and SDK implementations as code evolves. This skill ensures OpenAPI and SDK manuals stay aligned with the current codebase, reducing drift and confusion for developers and integrators.

Core Features & Use Cases

  • Automated alignment: Compare server endpoints and SDK interfaces against docs and identify drift.
  • Change classification: Detect new, changed, unchanged, and removed items and report a clear summary.
  • Update workflow: Prompt for updates and apply changes to docs/api/open-api.yml and docs/mod-manual/src/sdk after confirmation.

Quick Start

Run the sync-api-docs skill to align OpenAPI and SDK documentation with the latest server and client code.

Frequently Asked Questions about sync-api-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep OpenAPI specs in sync with server and SDK code changes?

To keep OpenAPI specs in sync with code, you compare server endpoints and SDK interfaces against your documentation. This detects drift by classifying changes as new, changed, unchanged, or removed, and prompts for updates.

What causes API documentation to drift from server and SDK implementations?

API documentation drifts when server endpoints and SDK interfaces evolve through added or changed routes and schemas, but the OpenAPI specs and SDK manuals are not updated. Synchronizing docs detects this drift by comparing code against the documentation.

How do I detect removed or changed endpoints in my OpenAPI documentation?

To detect removed or changed endpoints in OpenAPI documentation, compare your current server endpoint definitions and SDK interfaces against the existing docs. The comparison classifies changes as new, changed, unchanged, or removed and reports a summary.

Can I update SDK manuals and OpenAPI specs automatically when routes change?

You can update SDK manuals and OpenAPI specs by running an automated alignment workflow that compares code against docs. After detecting and classifying changes, it prompts for confirmation before applying updates to the documentation.

Does this documentation sync tool work with TypeScript SDKs and Rust servers?

Yes, the documentation sync tool works with TypeScript SDKs and Rust servers by reading SDK interfaces from TypeScript source files and endpoint definitions from Rust HTTP server crates, comparing them against OpenAPI and SDK manual documentation.