tldr-deep
Full 5-layer analysis of a specific function. Use when debugging or deeply understanding code.
pinned to #d07ff4bupdated last month
Ask your AI client: “install skills/tldr-deep”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/tldr-deepmetahub onboarded this repo on the author's behalf.
If you own github.com/parcadei/Continuous-Claude-v3 on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
3,883
Last commit
last month
Latest release
published
- #agents
- #claude-code
- #claude-code-cli
- #claude-code-hooks
- #claude-code-mcp
- #claude-code-skills
- #claude-code-subagents
- #claude-skills
- #mcp
About this skill
Pulled from SKILL.md at publish time.
Full 5-layer analysis of a specific function. Use when debugging or deeply understanding code.
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.d07ff4b· last month
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
7 passed2 warningsDescription qualitywarn
14 words · 94 chars — skills use the description as their trigger; aim higher
Aim for 15+ words and include trigger phrases like “use this skill when …”.
Homepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
README is present and substantial
45,577 chars · 22 sections · 38 code blocks
Tags / topics declared
9 total — agents, claude-code, claude-code-cli, claude-code-hooks, claude-code-mcp, claude-code-skills (+3)
README has usage / example sections
found: Quick Start · Installation · Installation (+1)
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Description is substantive
Description is 14 words.
Documentation present and substantive
Documentation present (SKILL.md, 412 words).
Documentation shows usage
Documentation includes 3 code examples.
Release history
1- releasecurrentd07ff4bwarnlast month
Contents
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)
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/tldr-deep