TLDR CLI komut referansi. tree, structure, search, extract, context, cfg, dfg, slice, calls, impact, dead, arch, imports, importers, diagnostics, change-impact komutlari.
You have tldr available on PATH for token-efficient code analysis.
# Core analysis
tldr tree [path] # File tree
tldr structure [path] --lang <lang> # Code structure (codemaps)
tldr search <pattern> [path] # Search files
tldr extract <file> # Full file info
tldr context <entry> --project . # LLM-ready context
# Flow analysis
tldr cfg <file> <function> # Control flow graph
tldr dfg <file> <function> # Data flow graph
tldr slice <file> <func> <line> # Program slice
tldr calls [path] # Cross-file call graph
# Codebase analysis
tldr impact <func> [path] # Who calls this function? (reverse call graph)
tldr dead [path] # Find unreachable/dead code
tldr arch [path] # Detect architectural layers
# Import analysis
tldr imports <file> # Parse imports from a file
tldr 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
tldr structure . to see what existstldr search "pattern" instead of grep for structured resultstldr cfg for complexity, tldr dfg for data flowtldr slice file.py func 42 to find what affects line 42tldr context entry_point to get relevant codetldr impact func_name before refactoring to see what would breaktldr dead src/ to find unused functions for cleanuptldr arch src/ to understand layer structuretldr imports file.py to see what a file importstldr importers module_name src/ to find who imports a moduletldr diagnostics . to catch type errors before running teststldr change-impact to run only affected testsSupports: python, typescript, go, rust
# 1. See project structure
tldr tree src/ --ext .py
# 2. Find relevant code
tldr search "process_data" src/
# 3. Get context for a function
tldr context process_data --project src/ --depth 2
# 4. Understand control flow
tldr cfg src/processor.py process_data
# 5. Before refactoring - check impact
tldr impact process_data src/ --depth 3
# 6. Find dead code to clean up
tldr dead src/ --entry main cli
tldr impact <function> [path] --depth N --file <filter>
Shows reverse call graph - all functions that call the target. Useful before refactoring.
tldr dead [path] --entry <patterns>
Finds functions never called (excluding entry points like main, test_, etc.)
tldr arch [path]
Analyzes call patterns to detect:
tldr imports <file> [--lang python]
Parses all import statements from a file. Returns JSON with module names, imported names, aliases.
tldr importers <module> [path] [--lang python]
Finds all files that import a given module. Complements tldr impact which tracks function calls - this tracks imports.
tldr diagnostics <file> # Single file
tldr diagnostics . --project # Whole project
tldr diagnostics src/ --format text # Human-readable output
tldr diagnostics src/ --no-lint # Type check only
Runs pyright (types) + ruff (lint) and returns structured errors. Use before tests to catch type errors early.
tldr change-impact # Auto-detect (session/git)
tldr change-impact src/foo.py # Explicit files
tldr change-impact --session # Session-modified files
tldr change-impact --git # Git diff files
tldr change-impact --run # Actually run affected tests
Finds which tests to run based on changed code. Uses call graph + import analysis.
All commands output JSON (except context which outputs LLM-ready text, diagnostics --format text for human output).