review-historylisted

<!-- Generated from https://github.com/nielsmadan/agentic-coding — edits here are overwritten. --> # Review History Investigate how code evolved over time to understand current behavior or find regressions. ## Usage ``` /review-history src/auth/login.ts /review-history the authentication flow /review-history UserProfile component ``` ## Gotchas - `git log -S` finds commits where the string was added OR removed. A commit that deleted a function surfaces as equally relevant to the one that added it — verify the direction of change. - Squash merges erase commit-level traceability. `git reflog` only works locally and expires — if another contributor squashed and force-pushed, the original commits are unrecoverable. ## Workflow ### Step 1: Identify Target Files From the provided topic, identify the relevant files: - If a file path is given, use it directly - If a feature/function name, locate relevant files using this strategy: 1. Grep for the exact function/class name to find where it is defined and used 2. Glob for files with the feature name in the path (e.g., `**/*payment*`) 3. Prioritize source files over test files; include tests only if investigating test behavior 4. Limit to the 5 most relevant files to keep the analysis focused ### Step 2: Git History Analysis Run these in parallel: **Recent commits touching the area:** ```bash git log --oneline -20 -- <file_or_directory> ``` **Detailed blame for key sections:** ```bash # For files > 200 lines: target