update-docs

Update docs pages and navigation to reflect public API changes across packages.

20|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/Eigenwise/tesseron --skill update-docs-eigenwise
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-docs
Source: https://github.com/Eigenwise/tesseron/tree/main/.claude/skills/update-docs
Command: npx skills add https://github.com/Eigenwise/tesseron --skill update-docs-eigenwise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the published documentation in sync with changes to the code surface across packages, preventing drift between code reality and user-facing docs.

Core Features & Use Cases

  • Detects public-surface changes across packages/** and updates docs/src/content/docs/ accordingly.
  • Maintains page ownership and navigation (overview/index.mdx, protocol docs, sdk pages, etc.) to reflect new symbols and surface changes.
  • Guards against drift by flagging missing docs trees and guiding remediation to ensure the Starlight site remains accurate.

Quick Start

Run the update-docs skill after making public-surface changes to packages/** to refresh docs.

Frequently Asked Questions about update-docs

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

FAQPage Schema
How do I keep documentation in sync with code changes across packages?▼

To keep documentation in sync with code changes, you can run a sync process that uses git diff to detect public-surface modifications across packages/** and automatically updates the corresponding docs pages.

What is documentation drift and how do I prevent it after updating public APIs?▼

Documentation drift happens when published docs no longer match the actual code surface. You prevent it by detecting public API changes via git diff and refreshing the navigation, cross-references, and content in your docs tree.

How to update Starlight docs after modifying package exports?▼

Update Starlight docs by targeting the docs/src/content/docs/ directory, detecting export changes in packages/**, and automatically updating overview pages, protocol definitions, and SDK references to reflect the new symbols.

Does documentation sync ignore internal refactors and test-only changes?▼

Yes, documentation sync specifically ignores test-only modifications and internal refactors. It targets changes that alter public APIs, protocol definitions, builder APIs, or exports to ensure only user-facing surface changes trigger docs updates.

What happens if my docs tree is missing when synchronizing docs with code?▼

If the docs tree at docs/src/content/docs/ is missing, the synchronization process will flag it and guide remediation. This ensures the Starlight site remains accurate and prevents undocumented public-surface changes.

When do I need to run a docs synchronization update for my packages?▼

You need to run a docs synchronization update after making public-surface changes to packages/**. This refreshes the docs tree to accurately reflect new symbols, updated protocol definitions, and modified builder APIs.