A production CLI tool that gives AI coding agents semantic understanding of C# codebases.
Instead of reading 10,000 lines manually, ask "What calls this method?" and get answers in seconds.
Every command is designed for one thing: helping AI agents understand and modify C# code without breaking things.
Find classes, methods, and patterns across the entire solution. Semantic search, not text matching.
Catch bugs before they reach production. Detect async issues, race conditions, and architectural violations.
Precision code modification. Inject code, clone patterns, refactor safely—all at the AST level.
Understand complexity and predict impact. Know what breaks before you change anything.
Trace execution paths, find all callers, reconstruct what happens at runtime.
Long-running workflows, saga coordination, and multi-step operations with proper state management.
The CLI is designed for orchestration. Each agent knows exactly which commands to use for its mission.
Discovery specialist. Finds reusable code before you build something that already exists.
Quality inspector. Validates implementations are correct, safe, and complete.
Precision modifier. Safe code injection, refactoring, and AST-level manipulation.
Risk analyst. Complexity analysis, impact assessment, and strategic guidance.
Root cause analyst. Reconstructs execution flows, traces call chains, solves bugs.
Strategic planner. Decides which agents to invoke and in what order.
How AI agents use these commands to save hours of manual work.
Agent reads file after file. Opens 50+ files trying to understand the architecture. Burns through context window. Takes 20+ iterations just to map the system.
index-query "payment processing" → Finds all relevant classes in 0.3s.
trace-flow → Maps the complete execution path.
Agent understands the system in 2 iterations.
Agent changes UserService. Doesn't know 38 files depend on it. Breaks the build. Spends 10 iterations fixing cascading failures.
blast-radius --symbol UserService → Shows all 38 dependents.
simulate-architecture → Tests change impact before coding.
Agent knows exactly what will break and plans accordingly.
Agent needs RefundStrategy like PaymentStrategy. Manually copies files, renames classes, updates namespaces, fixes tests. 2-4 hours of tedious work.
replicate --from PaymentStrategy --to RefundStrategy
Creates interface, implementation, DTOs, and test stubs—all with proper naming. Done in seconds.
Production-grade tooling on top of Microsoft's compiler platform.