docs-update

Guide documentation updates after code changes using llms.txt inventories.

48|4|Updated Dec 22, 2025

Search Tags:#documentation #consistency #docs #api-docs #llms #documentation-inventory

Ready to run

npx skills add https://github.com/OysteinAmundsen/toolbox --skill docs-update-oysteinamundsen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docs-update
Source: https://github.com/OysteinAmundsen/toolbox/tree/main/.github/skills/docs-update
Command: npx skills add https://github.com/OysteinAmundsen/toolbox --skill docs-update-oysteinamundsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps documentation up-to-date after code changes by providing a standardized process to identify and update affected docs, preventing drift and improving maintainability.

Core Features & Use Cases

Documentation inventory guidance (llms.txt, llms-full.txt) and cross-reference mapping to API and plugin docs.
Step-by-step checklist for after features, fixes, or refactors, including when to regenerate API docs.
Centralized guidelines and templates to streamline documentation updates for large codebases.

Quick Start

After any code change, run the Documentation Update Guide checklist to identify which documentation to update and then regenerate the API docs.

Frequently Asked Questions about docs-update

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

FAQPage Schema

How do I keep documentation in sync with code changes after a release?▼

To keep documentation in sync with code changes, use a standardized update checklist that identifies affected docs and specifies when to regenerate API references. This prevents documentation drift by guiding reviews after features, fixes, or refactors.

What is a documentation inventory and how does it help maintain API docs?▼

A documentation inventory, such as llms.txt or llms-full.txt, is a centralized file that maps cross-references to API and plugin docs. It helps maintain API docs by providing a clear structure to identify which documentation needs review after code modifications.

How do I know which docs to update after a code refactor?▼

To know which docs to update after a code refactor, follow a step-by-step documentation update checklist that cross-references the centralized llms.txt inventory. This process identifies affected documentation surfaces and outlines when to regenerate API references.

Do I need a centralized documentation inventory to maintain consistency across large codebases?▼

Yes, you need a centralized documentation inventory like llms.txt to maintain consistency across large codebases. It provides the necessary cross-reference mapping and centralized guidelines required to streamline documentation updates after code changes.

When should I regenerate API references during the documentation update process?▼

You should regenerate API references during the documentation update process when code changes affect API surfaces. The update checklist guides this step, ensuring that API docs remain accurate and aligned with the latest codebase modifications.