update-lib-docs
Update library documentation in .claude/docs/libraries/ with latest information from web search.
Best use case
update-lib-docs is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Update library documentation in .claude/docs/libraries/ with latest information from web search.
Teams using update-lib-docs should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/update-lib-docs/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How update-lib-docs Compares
| Feature / Agent | update-lib-docs | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Update library documentation in .claude/docs/libraries/ with latest information from web search.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Update Library Documentation
Update documentation in `.claude/docs/libraries/` with latest information.
## Steps
### 1. Check Existing Documents
List current library documentation:
```bash
ls .claude/docs/libraries/
```
### 2. Web Search for Latest Info
For each documented library, search for:
- Latest version
- Breaking changes
- Deprecated features
- New features
- Security updates
### 3. Update Documents
For each library with changes:
1. Update version information
2. Add new features/constraints
3. Mark deprecated APIs
4. Update code examples if needed
5. Record update date at the top
### 4. Check Impact on Code
After updating docs, verify:
- Using any deprecated APIs?
- Any breaking change impacts?
- Need to update project dependencies?
## Key Items to Check
| Category | What to Look For |
|----------|------------------|
| Security | CVEs, security patches |
| Breaking | API changes, removed features |
| Deprecated | APIs marked for removal |
| Performance | Optimization improvements |
| New Features | Useful additions |
## Update Format
Add update notice at top of file:
```markdown
# {Library Name}
> **Last Updated**: {Date}
> **Version Checked**: {version}
## Recent Changes
- {Change 1}
- {Change 2}
---
{Rest of documentation}
```
## Report
After updating, report to user (in Japanese):
- Which libraries were updated
- Significant changes found
- Any action items for the projectRelated Skills
update-design
Explicitly update DESIGN.md with decisions from the current conversation. Use when you want to force a design document update.
context-loader
ALWAYS activate this skill at the start of every task. Load project context from .claude/ directory including coding rules, design decisions, and documentation before executing any task.
troubleshoot
Diagnose and plan fixes for errors/bugs with Codex-first multi-agent collaboration (Codex + Opus 4.6 + Agent Teams). Codex CLI is consulted in EVERY phase for deep code reasoning, hypothesis evaluation, and fix validation. Phase 1: Error reproduction & context gathering (Opus subagent 1M context + Codex initial analysis + Claude user interaction). Phase 2: Parallel diagnosis (Agent Teams: Root Cause Analyst [Codex-driven] + Impact Investigator [Opus + Codex risk analysis]). Phase 3: Fix plan synthesis, Codex validation & user approval. Fix implementation is handled separately by /team-implement.
team-review
Parallel code review using Agent Teams. Spawns specialized reviewers (security, quality, test coverage) to review implementation from different perspectives simultaneously. Run after implementation.
team-implement
Parallel implementation using Agent Teams. Spawns teammates per module/layer, each owning separate files to avoid conflicts. Uses shared task list with dependencies for autonomous coordination. Run after /start-feature plan approval.
tdd
Implement features using Test-Driven Development (TDD) with Red-Green-Refactor cycle.
start-feature
Start a new feature with multi-agent collaboration (Opus 4.6 + Agent Teams). Phase 1: Codebase understanding (Opus subagent 1M context + Claude user interaction). Phase 2: Parallel research & design (Agent Teams: Researcher + Architect). Phase 3: Plan synthesis & user approval. Implementation is handled separately by /team-implement.
spike
Time-boxed technical investigation/feasibility study with Codex-first multi-agent collaboration (Codex + Opus 4.6 + Agent Teams). Codex CLI is consulted in EVERY phase for question framing, feasibility analysis, and final evaluation. Phase 1: Frame the investigation question & constraints (Claude user interaction + Codex question decomposition). Phase 2: Parallel investigation (Agent Teams: Researcher [Opus external research] + Feasibility Analyst [Codex deep analysis] + optional prototype). Phase 3: Codex synthesis into go/no-go recommendation & research report. Produces a DECISION DOCUMENT, NOT an implementation plan. Use /add-feature or /start-feature after a GO decision.
simplify
Simplify and refactor code while preserving functionality and library constraints.
research-lib
Research a library and create comprehensive documentation in .claude/docs/libraries/.
plan
Create a detailed implementation plan for a feature or task. Use when user wants to plan before coding.
init
Analyze project structure and populate the "Repository Identity" section of CLAUDE.md (Zone B) plus AGENTS.md.