tldr-deep
Full 5-layer analysis of a specific function. Use when debugging or deeply understanding code.
Install
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill tldr-deepSKILL.md
TLDR Deep Analysis
Full 5-layer analysis of a specific function. Use when debugging or deeply understanding code.
Trigger
/tldr-deep <function_name>- "analyze function X in detail"
- "I need to deeply understand how Y works"
- Debugging complex functions
Layers
| Layer | Purpose | Command |
|---|---|---|
| L1: AST | Structure | tldr extract <file> |
| L2: Call Graph | Navigation | tldr context <func> --depth 2 |
| L3: CFG | Complexity | tldr cfg <file> <func> |
| L4: DFG | Data flow | tldr dfg <file> <func> |
| L5: Slice | Dependencies | tldr slice <file> <func> <line> |
Execution
Given a function name, run all layers:
# First find the file
tldr search "def <function_name>" .
# Then run each layer
tldr extract <found_file> # L1: Full file structure
tldr context <function_name> --project . --depth 2 # L2: Call graph
tldr cfg <found_file> <function_name> # L3: Control flow
tldr dfg <found_file> <function_name> # L4: Data flow
tldr slice <found_file> <function_name> <target_line> # L5: Slice
Output Format
## Deep Analysis: {function_name}
### L1: Structure (AST)
File: {file_path}
Signature: {signature}
Docstring: {docstring}
### L2: Call Graph
Calls: {list of functions this calls}
Called by: {list of functions that call this}
### L3: Control Flow (CFG)
Blocks: {N}
Cyclomatic Complexity: {M}
[Hot if M > 10]
Branches:
- if: line X
- for: line Y
- ...
### L4: Data Flow (DFG)
Variables defined:
- {var1} @ line X
- {var2} @ line Y
Variables used:
- {var1} @ lines [A, B, C]
- {var2} @ lines [D, E]
### L5: Program Slice (affecting line {target})
Lines in slice: {N}
Key dependencies:
- line X → line Y (data)
- line A → line B (control)
---
Total: ~{tokens} tokens (95% savings vs raw file)
When to Use
- Debugging - Need to understand all paths through a function
- Refactoring - Need to know what depends on what
- Code review - Analyzing complex functions
- Performance - Finding hot spots (high cyclomatic complexity)
Programmatic API
from tldr.api import (
extract_file,
get_relevant_context,
get_cfg_context,
get_dfg_context,
get_slice
)
# All layers for one function
file_info = extract_file("src/processor.py")
context = get_relevant_context("src/", "process_data", depth=2)
cfg = get_cfg_context("src/processor.py", "process_data")
dfg = get_dfg_context("src/processor.py", "process_data")
slice_lines = get_slice("src/processor.py", "process_data", target_line=42)
Related skills
improve-codebase-architecturemattpocock1MScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.codebase-designmattpocock691KShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.web-design-guidelinesvercel-labs676KReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".code-reviewmattpocock631KReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".
