Git history context for drafter (#95)

Author: derekmisler

review-pr/action.yml

@@ -182,6 +182,24 @@ runs:
           fi
         fi
 
+    - name: Generate file history
+      if: hashFiles('changed_files.txt') != ''
+      shell: bash
+      run: |
+        > /tmp/file_history.txt
+        while IFS= read -r file; do
+          # Skip new files (no git history)
+          HISTORY=$(git log --oneline -5 -- "$file" 2>/dev/null || true)
+          if [ -n "$HISTORY" ]; then
+            echo "## $file" >> /tmp/file_history.txt
+            echo "$HISTORY" >> /tmp/file_history.txt
+            echo "" >> /tmp/file_history.txt
+          fi
+        done < changed_files.txt
+
+        ENTRIES=$(grep -c '^## ' /tmp/file_history.txt 2>/dev/null || echo "0")
+        echo "✅ Generated history for $ENTRIES file(s)"
+
     - name: Resolve stale review threads
       continue-on-error: true
       shell: bash

review-pr/agents/pr-review.yaml

@@ -114,11 +114,19 @@ agents:
          Project context (from AGENTS.md):
          <contents of AGENTS.md, or "No AGENTS.md found" if absent>
 
+         File history (recent commits):
+         <contents of /tmp/file_history.txt, or "No file history available" if absent>
+
          Learned patterns: <any relevant memories>
          ```
 
          The drafter has `read_file` access and will read the chunk from disk. Keep the
-         delegation message short — just the file path, chunk number, project context, and any learned patterns.
+         delegation message short — just the file path, chunk number, project context,
+         file history, and any learned patterns.
+
+         If `/tmp/file_history.txt` exists, read it and include relevant entries for the
+         files in the current chunk. This helps the drafter understand what kinds of bugs
+         this code has had before.
 
          **Include a file listing** so the drafter knows what files exist on disk. Before
          delegating, run:
@@ -293,6 +301,10 @@ agents:
       You also have `read_file` access for reading full source files when analyzing findings
       (e.g., to check imports, surrounding code, or related functions).
 
+      The orchestrator may provide recent git commit history for changed files. Use this to
+      understand what kinds of bugs this code has had before and what areas are actively
+      being fixed.
+
       ## REQUIRED: Verify Before Reporting
 
       Before reporting a finding, you MUST use `read_file` to read the full source file