mcpField
T
tldr-deep

tldr-deep

github.com/parcadeiDevelopment3.9k484 installsUpdated 39w ago
Repository

About tldr-deep

tldr-deep is a code-analysis skill for developers who need to debug or understand a function in depth. It examines structure, call graphs, control flow, data flow, and dependencies across five layers.

Key features

  1. 01Five-layer function analysis
  2. 02AST structure inspection
  3. 03Call graph navigation
  4. 04Control and data flow analysis
  5. 05Dependency slicing
  6. 06Python API access

Use cases

  1. 01Tracing paths through complex functions
  2. 02Checking dependencies before refactoring
  3. 03Reviewing complex code
  4. 04Finding high-complexity hotspots

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill tldr-deep

After installing, type/tldr-deepin Claude Code to confirm it loaded.

Details

From the project README

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)

Comments

Markdown supported