tldr-swinton

Semantic code search - find code by meaning, not just text patterns

Get token-efficient context for recent changes (diff-first workflow)

Get LLM-ready context for a specific function or class

Structural code search using ast-grep tree-sitter patterns

Show the tldr-swinton quick reference guide for agents

Extract file analysis (functions, classes, imports) as structured output

```

All internal imports MUST use relative imports:

**FunctionInfo** (`modules/core/ast_extractor.py`):

The MCP server is the primary agent interface. 24 tools organized by category.

| Command | Description |

| Project | What | Path |

| Backend | Model | Dimensions | Install | Quality |

Use when starting any coding task: fix bugs, debug, implement features, refactor, write tests, review code, migrate, port, or explore a codebase. Also use when resuming a previous session, onboarding to a repo, or before reading code files in a new conversation. Provides diff-focused context that saves 48-73% tokens.

Use when asked to understand a codebase's architecture, explore an unfamiliar project, onboard to a new repo, identify which modules exist, find entry points, or get a bird's-eye view before diving into code. Also use when the user says 'what does this project do' or 'show me the structure'. Provides structural overview without reading individual files.

Sync interbench eval coverage with tldrs capabilities. Run when tldrs gains new formats, flags, or commands. Reads the tldrs manifest as ground truth and generates minimal targeted edits to 4 interbench files.

Use when auditing a codebase for semantic duplication - functions that do the same thing but have different names or implementations. Especially useful for LLM-generated codebases where new functions are often created rather than reusing existing ones.