Skill v1.0.0
currentAutomated scan100/100version: "1.0.0"
name: tldr-cli description: TLDR CLI komut referansi. tree, structure, search, extract, context, cfg, dfg, slice, calls, impact, dead, arch, imports, importers, diagnostics, change-impact komutlari.
TLDR CLI - Code Analysis Tool
You have tldr available on PATH for token-efficient code analysis.
Commands
# Core analysistldr tree [path] # File treetldr structure [path] --lang <lang> # Code structure (codemaps)tldr search <pattern> [path] # Search filestldr extract <file> # Full file infotldr context <entry> --project . # LLM-ready context# Flow analysistldr cfg <file> <function> # Control flow graphtldr dfg <file> <function> # Data flow graphtldr slice <file> <func> <line> # Program slicetldr calls [path] # Cross-file call graph# Codebase analysistldr impact <func> [path] # Who calls this function? (reverse call graph)tldr dead [path] # Find unreachable/dead codetldr arch [path] # Detect architectural layers# Import analysistldr imports <file> # Parse imports from a filetldr importers <module> [path] # Find all files that import a module# Quality & testing (NEW)tldr diagnostics <file|path> # Type check + lint (pyright/ruff)tldr change-impact [files...] # Find tests affected by changes
When to Use
- Before reading files: Run
tldr structure .to see what exists - Finding code: Use
tldr search "pattern"instead of grep for structured results - Understanding functions: Use
tldr cfgfor complexity,tldr dfgfor data flow - Debugging: Use
tldr slice file.py func 42to find what affects line 42 - Context for tasks: Use
tldr context entry_pointto get relevant code - Impact analysis: Use
tldr impact func_namebefore refactoring to see what would break - Dead code: Use
tldr dead src/to find unused functions for cleanup - Architecture: Use
tldr arch src/to understand layer structure - Import tracking: Use
tldr imports file.pyto see what a file imports - Reverse imports: Use
tldr importers module_name src/to find who imports a module - Before tests: Use
tldr diagnostics .to catch type errors before running tests - Selective testing: Use
tldr change-impactto run only affected tests
Languages
Supports: python, typescript, go, rust
Example Workflow
# 1. See project structuretldr tree src/ --ext .py# 2. Find relevant codetldr search "process_data" src/# 3. Get context for a functiontldr context process_data --project src/ --depth 2# 4. Understand control flowtldr cfg src/processor.py process_data# 5. Before refactoring - check impacttldr impact process_data src/ --depth 3# 6. Find dead code to clean uptldr dead src/ --entry main cli
Codebase Analysis Commands
Impact Analysis
tldr impact <function> [path] --depth N --file <filter>
Shows reverse call graph - all functions that call the target. Useful before refactoring.
Dead Code Detection
tldr dead [path] --entry <patterns>
Finds functions never called (excluding entry points like main, test_, etc.)
Architecture Detection
tldr arch [path]
Analyzes call patterns to detect:
- Entry layer (controllers/handlers)
- Middle layer (services)
- Leaf layer (utilities)
- Circular dependencies
Import Analysis
tldr imports <file> [--lang python]
Parses all import statements from a file. Returns JSON with module names, imported names, aliases.
Reverse Import Lookup
tldr importers <module> [path] [--lang python]
Finds all files that import a given module. Complements tldr impact which tracks function calls - this tracks imports.
Diagnostics (Type Check + Lint)
tldr diagnostics <file> # Single filetldr diagnostics . --project # Whole projecttldr diagnostics src/ --format text # Human-readable outputtldr diagnostics src/ --no-lint # Type check only
Runs pyright (types) + ruff (lint) and returns structured errors. Use before tests to catch type errors early.
Change Impact (Selective Testing)
tldr change-impact # Auto-detect (session/git)tldr change-impact src/foo.py # Explicit filestldr change-impact --session # Session-modified filestldr change-impact --git # Git diff filestldr change-impact --run # Actually run affected tests
Finds which tests to run based on changed code. Uses call graph + import analysis.
Output
All commands output JSON (except context which outputs LLM-ready text, diagnostics --format text for human output).