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.zip

Installs 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.
94 chars✓ has a “when” trigger
Intermediate

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

You give it
Function name and target line number
You get back
Deep analysis report covering AST, call graph, CFG, DFG, and slice

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

LayerPurposeCommand
L1: ASTStructuretldr extract <file>
L2: Call GraphNavigationtldr context <func> --depth 2
L3: CFGComplexitytldr cfg <file> <func>
L4: DFGData flowtldr dfg <file> <func>
L5: SliceDependenciestldr 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

  1. Debugging - Need to understand all paths through a function
  2. Refactoring - Need to know what depends on what
  3. Code review - Analyzing complex functions
  4. 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.

SkillInstallsUpdatedSafetyDifficulty
tldr-deep (this skill)16moReviewIntermediate
python-testing-patterns772moReviewIntermediate
error-handling-patterns352moNo flagsIntermediate
codex-claude-loop139moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

Search skills

Search the agent skills registry