What problem does it solve? When modifying existing code, developers often lack context about why it was built a certain way, when it changed, or which commit introduced a regression. This Skill answers those historical questions by searching git history and project memory files before any code is touched. ## Core Features & Use Cases - Guided Git Archaeology: Runs scoped git log --follow, git blame, and date-filtered history queries to trace when and why code changed. - Project Memory Search: Greps .ai/LOG.md and .ai/DECISIONS.md to surface recorded decisions and the E-## task that produced a file. - Regression Investigation: Locates the commit that introduced a failing test or bug using targeted history queries. - Use Case: Before refactoring a legacy module, ask why it was implemented a certain way and receive the originating commit hash, date, and decision context. ## Quick Start Ask why a specific file or function works the way it does and request the commit and decision history behind it.