AI coding

Static analysis and codebase mapping

• Using AI Coding Agents on a Legacy Codebase
• A Call Graph Diff an Agent Runs Before It Edits
• A Guard Test That Fails When a Refactor Adds an Indirect Caller
• Finding Callers a Static Graph Misses: Dispatch and Reflection
• How to Map a Codebase Before an Agent Touches It
• Mapping Call Sites Before an Agent Edits a Shared Function
• A Pre-Edit Checklist for Any Function with More Than Five Callers
• Auditing an Agent-Built Map: Finding Stale and Missing Edges
• Blast Radius: Listing the Systems a Change Touches
• Caching a Call Graph Across Commits: Keys, TTLs and Hit Rates
• Caching a Caller Inventory: Keys, TTLs and Hit Rates
• Dynamic Dispatch Targets: Tracing What the Static Graph Misses
• Freezing a Call Graph into a Test: Schema and Update Rules
• From Call Graph to Test List: Checks an Agent Must Run
• From Caller Inventory to a Test List an Agent Can Run
• Giving an Agent the Call Graph Without Giving It the Whole Repo
• Reading a Call Graph for Coupling Before a Refactor
• Recording Every Dynamic Dispatch Target a Test Session Touches
• Sorting New Indirect Callers: Which Ones Block the Edit
• Turning Entry Points into a Test List an Agent Must Satisfy
• When a Refactor Adds a Caller Indirectly: Watching the Inventory
• When a Static Caller List Misses Dynamic Dispatch