القائمة
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.
التثبيت باستخدام 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 | debug-bug |
| description | 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. |
| compatibility | Requires tokenlean CLI tools (npm i -g tokenlean) and git |
Systematically find and fix bugs while reading as little code as possible.
Reproduce → Localize → Trace → Fix → Verify
tl run "<repro command>" # Capture the actual error output
No fix without reproduction. If no repro command is given, ask for one. If the bug is in tests, run the failing test. This step is non-negotiable.
Narrow down where the bug lives:
tl parallel \
"errors=tl errors" \
"blame=tl blame <file>" \
"history=tl history <file>"
If the error includes a stack trace, start with the top frame. If it's vague, use tl search "<error message>" to find where the error originates.
Understand the code path without reading entire files:
tl parallel \
"flow=tl flow <function> <file>" \
"deps=tl deps <file>" \
"snippet=tl snippet <function> <file>"
Apply the minimal fix. Then check for side effects:
tl parallel "guard=tl guard" "impact=tl impact <file>"
tl parallel "repro=tl run '<repro command>'" "tests=tl run '<test command>'"
Bug report → Can you reproduce it?
├─ Yes → What layer does the error come from?
│ ├─ Stack trace points to a file → tl blame + tl snippet on that file
│ ├─ Error is vague / no stack → tl errors + tl search for the error message
│ └─ Happening in dependency → tl deps to confirm, check dep version
├─ No → Ask for reproduction steps before proceeding
└─ Intermittent → tl history on suspect files, look for recent changes
tl parallel to run context-gathering commands simultaneouslytl search "<error message>" to find where errors are throwntl diff for recent regressions — the bug may be in the last few commitstl impact to ensure dependents aren't affected by the change