History Reviewer — Development agent for Claude Code
Git history-aware reviewer.
How to install History Reviewer
Installs to ~/.claude/agents/stuartshields-claude-setup-history-reviewer.md
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/stuartshields/claude-setup/HEAD/agents/history-reviewer.md -o ~/.claude/agents/stuartshields-claude-setup-history-reviewer.md Restart Claude Code, or start a new session, for it to be picked up.
What History Reviewer does
name: history-reviewer description: Git history-aware reviewer. Use when changes touch code with non-trivial history, or to check whether a fix accidentally reverts a prior fix or breaks an established pattern. Uses git blame and log to surface why existing code looks the way it does. Read-only. Reports regressions, reverted fixes, and ignored context with commit + file:line references. tools: Read, Grep, Glob, Bash permissionMode: plan model: sonnet maxTurns: 20
You are a senior engine
Alternatives in Development
- Svelte Recurrence Sweep — Given a defect just found or fixed in a SvelteKit app (apps/moderator, apps/auth, apps/creator-studio), finds 7.2k ★
- Shep Tsp Field Adder — Adds ONE new field (property, enum value, or base-type extension) to a TypeSpec model in tsp/, re-runs codegen 247 ★
- Agent365 Anti Pattern Detector — Use this agent when reviewing code changes in the Agent365-Samples repository to identify violations of establ 104 ★
Full documentation available on GitHub
View Source RepositoryRelated Agents
Review Outcomes
Periodic post-ship outcome review — grade shipped merges against the fixes and reverts that followed, and agai
Reviso Finder History
Reviso finder — reads git blame and history of the modified code to find bugs in light of historical context.
Review History
Check git blame and historical context of modified code
Git Archaeologist
Explains why code is the way it is by tracing it through git history, blame, pickaxe searches, and linked PRs.
Expert
Implementation specialist with pattern compliance. Use for implementing features from PRDs following establish
Fearmap
Analyse git repo history and produce FEARMAP.md — a map of dangerous, load-bearing, risky, and dead files. Use
Related Skills
Research Before Build
Research before build — a research-first meta-skill for AI agents: check prior art & community solutions befor
Last Pass
Stage 4 last pass - fresh-eyes regression against ALL prior milestones (_firstinitial through _finalinitial),
Does This Clash
Analyze whether code fits with established codebase patterns and conventions