القائمة
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 المهني
Find duplicate functions and eliminate them so they stay gone. Triage tl dupes output by tier, apply the right consolidation pattern, and lock the win with a duplication-ratchet test. Use when asked to dedupe, remove duplication, consolidate copy-paste, clean up repeated helpers, or act on tl dupes output.
Find duplicate functions in Codex and remove them so they stay gone — triage tl dupes by tier, consolidate the second home (not both copies), and add a duplication-ratchet test to block regressions. Use when deduping, removing copy-paste, consolidating repeated helpers, or acting on tl dupes output.
Git commits, pushes, and GitHub operations using tokenlean. Covers tl push (with multi-file safety guard), tl commit-prep, tl gh (bulk issue/PR/release operations), and when to use tl gh vs gh CLI vs GitHub MCP. Use when committing, pushing, creating/closing/viewing issues, managing PRs, creating releases, or any git/GitHub workflow.
Git commits, pushes, and GitHub operations using tokenlean. Covers tl push (with multi-file safety guard), tl commit-prep, tl gh (bulk issue/PR/release operations). Use when committing, pushing, creating/closing/viewing issues, managing PRs, creating releases, or any git/GitHub workflow.
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.
| 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 parallel \
"npm=tl npm <package>" \
"search=tl search '<package-name>'" \
"deps=tl deps <file>"
Check what changed between versions:
tl parallel "browse=tl browse <changelog-url>" "docs=tl context7 <package> 'migration guide'"
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 parallel \
"test=tl run '<test command>'" \
"testmap=tl test-map <file>" \
"guard=tl guard"
Remove old compatibility code:
tl parallel "unused=tl unused" "search=tl search '<old-version>'"
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