メニュー
Upgrade dependencies safely by auditing usage, researching breaking changes, and verifying after upgrade. Scales effort to version jump size — light check for patches, full audit for majors. Use when asked to upgrade, bump, or update a dependency or package.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Add new functionality by understanding existing patterns and dependencies before writing code. Locates where the feature belongs, studies conventions, implements following precedent, then verifies integration. Use when asked to add a feature, flag, endpoint, component, or module.
Thorough code review using token-efficient context gathering. Analyzes PRs, diffs, or staged changes by checking blast radius, complexity, and dependencies before reviewing the actual code. Use when asked to review a PR, review changes, or do a code review.
Systematically investigate and fix bugs using token-efficient context gathering. Reproduces the issue first, localizes with blame and history, traces the call path, then verifies the fix. Use when asked to fix a bug, investigate an error, or debug unexpected behavior.
Diagnose and fix performance issues by measuring before optimizing. Establishes baselines, identifies bottlenecks through call graphs and complexity analysis, then confirms improvements with numbers. Use when asked to optimize, speed up, reduce memory usage, or fix slowness.
Efficiently explore and understand an unfamiliar codebase using token-lean context gathering. Maps project structure, identifies key files, and builds understanding progressively without reading everything. Use when onboarding to a new project, asked to understand a codebase, or starting work in unfamiliar code.
Migrate frameworks, APIs, or language versions incrementally with verification at each step. Surveys the migration surface, batches work by dependency order, and commits after each verified batch. Use when asked to migrate between frameworks, upgrade major versions, or adapt to new API versions.
| name | upgrade-deps |
| description | Upgrade dependencies safely by auditing usage, researching breaking changes, and verifying after upgrade. Scales effort to version jump size — light check for patches, full audit for majors. Use when asked to upgrade, bump, or update a dependency or package. |
| compatibility | Requires tokenlean CLI tools (npm i -g tokenlean) and git |
Upgrade dependencies safely by understanding usage before changing versions.
Audit → Research → Upgrade → Verify → Clean up
Understand current usage before changing anything:
tl-npm <package> # Current vs latest version, changelog link, health
tl-search "<package-name>" # Every file that imports or uses the dependency
tl-deps <file> # Context around each file that imports it
Check what changed between versions:
tl-browse <changelog-url> # Read the changelog as markdown
tl-context7 <package> "migration guide" # Framework docs if available
Look for: removed APIs, renamed functions, changed defaults, new peer deps.
Apply the version bump:
# Update package.json and install
tl-diff --breaking # Detect signature mismatches in wrapper files
tl-snippet <symbol> <file> # Check each usage site against new API
tl-run "<test command>" # Full test suite
tl-test-map <file> # Find specific tests for targeted runs
tl-guard # Check for new issues
Remove old compatibility code:
tl-unused # Exports that only existed for the old version
tl-search "<old-version>" # Version-gated code or workarounds
Upgrade request → How big is the version jump?
├─ Patch (1.2.3 → 1.2.4) → Light check
│ → tl-npm to confirm, upgrade, tl-run tests
├─ Minor (1.2 → 1.3) → Standard check
│ → tl-search for usage, tl-browse changelog
│ → Upgrade, tl-run tests
└─ Major (1.x → 2.x) → Full audit
→ tl-search for all usage sites
→ tl-browse changelog + migration guide
→ tl-snippet on every consumer
→ Upgrade, tl-diff --breaking, tl-run tests
→ tl-unused to clean up compat code