ContextStrategies

Overview

I built ctx-flatten because “copy files into the prompt” doesn’t scale. It turns a repo into a token-budgeted Markdown context you can paste into an LLM, then goes further: AI-powered focusing, drift-safe AST-based patching, nine static analysis dimensions, duplicate detection, and git-history dashboards—delivered as one modular Python package with CLI, TUI, FastAPI, and Streamlit surfaces.

Problem

LLM context is expensive and easy to waste.

I kept watching good engineering time get wasted on context assembly: copy files by hand, miss an import, paste too much, then burn tokens on irrelevant code.

Even worse, AI-generated patches are brittle when the target changes between context capture and application. Without drift checks, you can end up editing the wrong symbol or applying a change to stale code.

Solution

One tool for context, scope, patching, and insight.

I built ctx-flatten to produce an optimized Markdown context that respects `.gitignore` and optional token budgets. Then—when you want it—it can use OpenRouter-backed AI to focus context to a task, propose changes, and apply them with drift-safe structural checks.

The goal is inspectable workflows: context files, reports, and history artifacts you can read and version, not a black-box “agent” that edits your repo blindly.