tldr-deep
Performs an in-depth 5-layer code analysis to help understand and debug complex functions.
Install
mkdir -p .claude/skills/tldr-deep && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7079" && unzip -o skill.zip -d .claude/skills/tldr-deep && rm skill.zipInstalls to .claude/skills/tldr-deep
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Full 5-layer analysis of a specific function. Use when debugging or deeply understanding code.Key capabilities
- →Extract AST structure from files
- →Generate call graphs with configurable depth
- →Analyze control flow complexity
- →Trace variable data flow
- →Identify program slice dependencies
How it works
The tool executes five distinct analysis layers including AST extraction, call graph navigation, control flow graph generation, data flow analysis, and program slicing.
Inputs & outputs
When to use tldr-deep
- →Debugging complex functions
- →Understanding unknown codebases
- →Analyzing code complexity
- →Tracing variable data flow
About this skill
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)
When not to use it
- →When the user is already familiar with the project
- →When working on a single file instead of a function
- →When analyzing test files
Limitations
- →Requires manual file search if the file path is unknown
- →Token savings depend on the size of the raw file
How it compares
Unlike manual code reading, this tool automates the extraction of structural and dependency data to provide a token-efficient summary.
Compared to similar skills
tldr-deep side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| tldr-deep (this skill) | 1 | 6mo | Review | Intermediate |
| python-testing-patterns | 77 | 2mo | Review | Intermediate |
| error-handling-patterns | 35 | 2mo | No flags | Intermediate |
| codex-claude-loop | 13 | 9mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by parcadei
View all by parcadei →You might also like
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
error-handling-patterns
wshobson
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
codex-claude-loop
bear2u
Orchestrates a dual-AI engineering loop where Claude Code plans and implements, while Codex validates and reviews, with continuous feedback for optimal code quality
serena
massgen
This skill provides symbol-level code understanding and navigation using Language Server Protocol (LSP). Enables IDE-like capabilities for finding symbols, tracking references, and making precise code edits at the symbol level.
javascript-mastery
davila7
Comprehensive JavaScript reference covering 33+ essential concepts every developer should know. From fundamentals like primitives and closures to advanced patterns like async/await and functional programming. Use when explaining JS concepts, debugging JavaScript issues, or teaching JavaScript fundamentals.
find-bugs
davila7
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.