mcpField
T
tldr-router

tldr-router

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

About tldr-router

A code exploration skill that maps question intent to suitable tldr command layers. It covers structure, call relationships, complexity, data flow, and impact analysis, along with automatic routing hooks and manual overrides.

Key features

  1. 01Map questions to tldr commands
  2. 02Browse files and code structure
  3. 03Analyze calls and architecture
  4. 04Inspect complexity and data flow
  5. 05Assess change impact
  6. 06Override the selected analysis layer

Use cases

  1. 01Orient within an unfamiliar codebase
  2. 02Trace calls and entry points
  3. 03Investigate data origins or errors
  4. 04Assess the impact of a refactor

Install

Copy the command and run it in a terminal.

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

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

Details

From the project README

TLDR Smart Router

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

Question → Command Mapping

"What files/functions exist?"
tldr tree . --ext .py          # File overview
tldr structure src/ --lang python  # Function/class overview

Use: Starting exploration, orientation

"What does X call / who calls X?"
tldr context <function> --project . --depth 2
tldr calls src/

Use: Understanding architecture, finding entry points

"How complex is X?"
tldr cfg <file> <function>

Use: Identifying refactoring candidates, understanding difficulty

"Where does variable Y come from?"
tldr dfg <file> <function>

Use: Debugging, understanding data flow

"What affects line Z?"
tldr slice <file> <function> <line>

Use: Impact analysis, safe refactoring

"Search for pattern P"
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:

# Force specific analysis
tldr cfg path/to/file.py function_name
tldr dfg path/to/file.py function_name
tldr slice path/to/file.py function_name 42

Comments

Markdown supported