メニュー
Refactor code safely by analyzing blast radius and dependencies before making changes. Covers renaming, moving, extracting, and restructuring code with verification at each step. Use when refactoring, renaming symbols, extracting functions, moving files, or restructuring code.
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 | safe-refactor |
| description | Refactor code safely by analyzing blast radius and dependencies before making changes. Covers renaming, moving, extracting, and restructuring code with verification at each step. Use when refactoring, renaming symbols, extracting functions, moving files, or restructuring code. |
| compatibility | Requires tokenlean CLI tools (npm i -g tokenlean) and git |
Change code structure without breaking dependents.
Analyze → Plan → Change → Verify
tl parallel \
"impact=tl impact <file>" \
"exports=tl exports <file>" \
"symbols=tl symbols <file>"
These three commands tell you:
If tl impact shows 10+ dependents, consider whether this refactor is worth the risk. Discuss with the user.
For each file that imports from the target:
tl snippet <imported-symbol> <consumer-file>
This shows how the symbol is actually used without reading the entire consumer file.
Apply the refactor. Then immediately check:
tl guard # Circular deps, unused exports, other issues
tl parallel "test=tl run '<test-command>'" "impact=tl impact <file>"
If tests fail, tl run output shows only the failures. Fix and re-run.
What are you changing?
├─ Renaming a symbol
│ → tl impact to find all importers
│ → Update all import sites
│ → tl guard to verify no broken imports
│
├─ Moving a file
│ → tl impact for full dependent list
│ → Move file, update all import paths
│ → tl guard for circular deps
│
├─ Extracting a function/module
│ → tl symbols + tl deps on source file
│ → Extract, add exports
│ → tl impact on original to update importers
│ → tl guard + tl run tests
│
└─ Changing a function signature
→ tl impact + tl flow to find all callers
→ tl snippet on each caller to see usage
→ Update signature + all call sites
→ tl run tests
tl unused after refactoring catches exports you forgot to clean up