update-lib-docs

Update library documentation with web-sourced version, deprecation, and security changes.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/treejh/ai-agent-skills --skill update-lib-docs-treejh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-lib-docs
Source: https://github.com/treejh/ai-agent-skills/tree/main/skills/claude-orchestrator/.claude/skills/update-lib-docs
Command: npx skills add https://github.com/treejh/ai-agent-skills --skill update-lib-docs-treejh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the effort of keeping library documentation in .claude/docs/libraries/ current by finding recent version, feature, deprecation, and security information from web sources and consolidating updates so developers do not miss breaking changes or important patches.

Core Features & Use Cases

  • Change Detection: Identify new versions, breaking API changes, deprecations, and security advisories for libraries documented in the repo.
  • Documentation Update: Inject standardized "Last Updated" metadata, update version and feature notes, and refresh example snippets when relevant.
  • Impact Analysis: Flag potential code impacts, deprecated usages, or dependency updates that require developer attention.
  • Use Case: Maintainers of a mono-repo can run the skill periodically to ensure library docs and dependency notes remain accurate after upstream releases.

Quick Start

Update the library documentation in .claude/docs/libraries/ by searching for the latest versions, breaking changes, deprecations, and security updates and apply structured updates with a summary of actions.

Frequently Asked Questions about update-lib-docs

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

FAQPage Schema
How do I keep library documentation updated with new versions and security advisories?

You can keep library documentation updated by running targeted web searches for recent versions, breaking changes, and security advisories, then injecting standardized 'Last Updated' metadata into your docs to ensure tracking accuracy.

What is the best way to track deprecations and breaking changes across multiple libraries?

Tracking deprecations and breaking changes across multiple libraries is done by performing change detection against web sources and consolidating the updates so developers do not miss important patches.

How do I perform a dependency analysis for deprecated usages in a mono-repo?

Performing dependency analysis for deprecated usages involves scanning documented libraries to flag potential code impacts and dependency updates that require developer attention after upstream releases.

Can I automate adding last-updated metadata to documentation files?

Yes, automating last-updated metadata involves injecting standardized timestamps and refreshing example snippets directly into documentation files when relevant updates are found.

Does this documentation update process work for tracking security advisories?

Yes, this documentation update process works for tracking security advisories by searching web sources for recent patches and surfacing the dependency or security impacts for developer review.