update-lib-docs

Update library documentation in .claude/docs/libraries with web-sourced version and security changes.

190|33|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/DeL-TaiseiOzaki/claude-code-orchestra --skill update-lib-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-lib-docs
Source: https://github.com/DeL-TaiseiOzaki/claude-code-orchestra/tree/main/.claude/skills/update-lib-docs
Command: npx skills add https://github.com/DeL-TaiseiOzaki/claude-code-orchestra --skill update-lib-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps keep library documentation up to date by automatically updating docs in .claude/docs/libraries/ with the latest information found via web search, reducing manual effort and inconsistencies.

Core Features & Use Cases

  • Automated Documentation Refresh: For each documented library, fetch latest version, breaking changes, deprecated features, new features, and security updates.
  • Version & Change Tracking: Update the top notice with the current version and date and annotate changes.
  • Impact Assessment: Evaluate potential impacts on dependent projects and dependencies to guide maintenance.
  • Use Case: When a new library version is released with security patches, run this skill to update docs and record CVE notes.

Quick Start

Run the update-lib-docs skill to refresh library docs using the latest search results and store the update notice at the top of each file.

Frequently Asked Questions about update-lib-docs

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

FAQPage Schema
How do I automatically update library documentation with the latest version changes?

Automatically update library documentation by running a web search to fetch the latest version, breaking changes, deprecations, and security updates, then apply these changes directly to your doc files.

What is the best way to track security patches and CVEs in my project's library docs?

Track security patches and CVEs by scanning documented libraries against recent web search results, then annotating the specific security updates and vulnerabilities directly within the documentation files.

How do I document breaking changes and deprecated features for updated dependencies?

Document breaking changes and deprecated features by analyzing each library for version updates, enforcing a top notice with the library name, last updated date, and checked version, and noting the changes internally.

Can I assess the impact of new library versions on my dependent projects automatically?

Assess impact on dependent projects by evaluating the fetched library updates, including new features and deprecations, to guide your ongoing project maintenance and dependency management decisions.

Do I need a specific folder structure to maintain library documentation?

You need to store your library documentation files in the .claude/docs/libraries directory, as the update process specifically targets and refreshes files within this path.

How does automated doc maintenance handle version tracking for multiple libraries?

Automated doc maintenance handles version tracking by iterating through each documented library, fetching its current version and changes via web search, and appending a standardized update notice to the top of each file.