菜单
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 职业分类
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 | 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-impact <file> # Who depends on this file?
tl-exports <file> # What's the public API surface?
tl-symbols <file> # Full signature map
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-run "<test-command>" # Run tests — tl-run filters to just errors
tl-impact <file> # Re-check: are all dependents still importing correctly?
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