원클릭으로
update-lib-docs
Update library documentation in .claude/docs/libraries/ with latest information from web search.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Update library documentation in .claude/docs/libraries/ with latest information from web search.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Comprehensive onboarding for new or returning contributors. Scans repository artifacts (git history, CLAUDE.md / AGENTS.md, project rules, skill catalog, DESIGN.md, research & library notes, checkpoints, agent-team logs) and synthesizes a GUIDE.md at the repository root summarizing what has been worked on, why, and how to resume work.
Save full session context: git history, CLI consultations, Agent Teams activity, and discover reusable skill patterns — all in one run. No flags needed. Maintains a rolling PROGRESS.md (latest 5 checkpoint summaries) and ends with a compact phase that prunes stale CLAUDE.md Zone C work blocks and compacts the conversation (also available standalone via --compact-only, replacing the old /context-refresh skill). Run at session end, after major milestones, or when you want to capture learnings.
Codex CLI handles planning, design, and complex code implementation. Use for: architecture design, implementation planning, complex algorithms, debugging (root cause analysis), trade-off evaluation, code review. External research is NOT Codex's job — use general-purpose-opus instead. Explicit triggers: "plan", "design", "architecture", "think deeper", "analyze", "debug", "complex", "optimize".
Unified feature planning & implementation skill — replaces the old /add-feature and /start-feature skills (both trigger phrases still apply here). MODE=existing (formerly /add-feature): add a feature to an established codebase with Codex-first collaboration — Codex is consulted in every phase for scope analysis, architecture design, implementation planning, and validation. MODE=greenfield (formerly /start-feature): start a large or new feature that requires external research — Agent Teams (Researcher + Architect) do parallel research & design. Both modes share Phase 3 complexity routing (SIMPLE: Codex direct, MODERATE: Codex + /team-execute --review-only, COMPLEX: /team-execute).
Analyze project structure, write the thick requirements doc (.claude/docs/DESIGN.md), and populate the thin "Repository Identity" pointer in CLAUDE.md (Zone B).
Research a library and create comprehensive documentation in .claude/docs/libraries/.
| name | update-lib-docs |
| description | Update library documentation in .claude/docs/libraries/ with latest information from web search. |
| disable-model-invocation | true |
Update documentation in .claude/docs/libraries/ with latest information.
List current library documentation:
ls .claude/docs/libraries/
For each documented library, search for:
For each library with changes:
After updating docs, verify:
| 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 |
Add update notice at top of file:
# {Library Name}
> **Last Updated**: {Date}
> **Version Checked**: {version}
## Recent Changes
- {Change 1}
- {Change 2}
---
{Rest of documentation}
After updating, report to user (in Japanese):