Context Map

Before you start coding, this generates a structured map of every file that might be affected by your changes. It searches for direct dependencies, related tests, similar patterns you can reference, and flags potential breaking changes or required migrations. Think of it as mandatory reconnaissance before touching anything important. The output is a markdown table that forces you to actually understand the blast radius of your changes instead of diving in blind. Honestly saves more time than it costs, especially on unfamiliar codebases where you'd otherwise spend hours tracking down mysterious test failures.