tundra

Use when encountering unexpected behavior, failing tests, API errors, or runtime panics in Tundra — before proposing any fix

Use when you need to understand codebase structure, locate code, or trace relationships before making changes or answering architecture questions

Use when planning or executing a refactor — rename, extract, move, or delete code — to prevent breaking callers or missing affected files

Use after completing a feature or before merging to perform a risk-scored review of changed code, check test coverage, and assess blast radius