tldr-cli
TLDR CLI komut referansi. tree, structure, search, extract, context, cfg, dfg, slice, calls, impact, dead, arch, imports, importers, diagnostics, change-impact komutlari.
npx skills add vibeeval/vibecosystem --skill tldr-cli --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# TLDR CLI - Code Analysis Tool You have `tldr` available on PATH for token-efficient code analysis. ## Commands ```bash # 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 ``` ## When to Use - **Before reading files**: Run `tldr structure .` to see what exists - **Finding code**: Use `tldr search "pattern"` instead of grep for struc
- Commands
- When to Use
- Languages
- Example Workflow
- Codebase Analysis Commands
- Impact Analysis
- Dead Code Detection
- Architecture Detection
- Import Analysis
- Reverse Import Lookup
- Diagnostics (Type Check + Lint)
- Change Impact (Selective Testing)
- Output
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
What does the tldr-cli skill do?
TLDR CLI komut referansi. tree, structure, search, extract, context, cfg, dfg, slice, calls, impact, dead, arch, imports, importers, diagnostics, change-impact komutlari.
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill tldr-cli --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.