Tldr Router

by parcadeid07ff4b06b62No license3.9K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 8 months ago

Maps questions to the optimal tldr command. Use this to pick the right layer

AI-generated overview

Maps code questions to the right tldr analysis command, such as tree, context, cfg, dfg or slice.

What it does
This skill is a routing guide that matches a developer's question about a codebase to the appropriate tldr command. It provides question-to-command mappings, a decision tree, and an intent keyword table covering navigation, architecture, complexity, data flow, impact and debugging. It also notes that tldr-read-enforcer and tldr-context-inject hooks can detect intent and route automatically, and lists manual override commands.
When to use it
Use it when you need to choose which tldr analysis layer fits a question about an unfamiliar codebase. It suits orientation, call-graph exploration, complexity checks, data-flow tracing, impact analysis and debugging investigations.
Requirements
Requires the tldr command-line tool to be installed and available; the skill itself ships no scripts and only provides instructions. The described hooks tldr-read-enforcer and tldr-context-inject are referenced as optional automatic routing.

TLDR Smart Router

Maps questions to the optimal tldr command. Use this to pick the right layer.

Question → Command Mapping

"What files/functions exist?"

bash
tldr tree . --ext .py          # File overviewtldr structure src/ --lang python  # Function/class overview

Use: Starting exploration, orientation

"What does X call / who calls X?"

bash
tldr context <function> --project . --depth 2tldr calls src/

Use: Understanding architecture, finding entry points

"How complex is X?"

bash
tldr cfg <file> <function>

Use: Identifying refactoring candidates, understanding difficulty

"Where does variable Y come from?"

bash
tldr dfg <file> <function>

Use: Debugging, understanding data flow

"What affects line Z?"

bash
tldr slice <file> <function> <line>

Use: Impact analysis, safe refactoring

"Search for pattern P"

bash
tldr search "pattern" src/

Use: Finding code, structural search

Decision Tree

START  │  ├─► "What exists?" ──► tree / structure  │  ├─► "How does X connect?" ──► context / calls  │  ├─► "Why is X complex?" ──► cfg  │  ├─► "Where does Y flow?" ──► dfg  │  ├─► "What depends on Z?" ──► slice  │  └─► "Find something" ──► search

Intent Detection Keywords

IntentKeywordsLayer
Navigation"what", "where", "find", "exists"tree, structure, search
Architecture"calls", "uses", "connects", "depends"context, calls
Complexity"complex", "refactor", "branches", "paths"cfg
Data Flow"variable", "value", "assigned", "comes from"dfg
Impact"affects", "changes", "slice", "dependencies"slice/pdg
Debug"bug", "error", "investigate", "broken"cfg + dfg + context

Automatic Hook Integration

The tldr-read-enforcer and tldr-context-inject hooks automatically:

  1. Detect intent from your messages
  2. Route to appropriate layers
  3. Inject context into tool calls

You don't need to manually run these commands - the hooks do it for you.

Manual Override

If you need a specific layer the hooks didn't provide:

bash
# Force specific analysistldr cfg path/to/file.py function_nametldr dfg path/to/file.py function_nametldr slice path/to/file.py function_name 42

Source and attribution

Source:parcadei/continuous-claude-v3in.claude/skills/tldr-routerat commitd07ff4b

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Tldr Router Agent Skill | SourceWeft