Menu

Individual skill

historian

Chesterton's Fence for code you're about to delete or refactor. Before you rip out a weird retry, a seemingly dead branch, an ugly workaround, or a "redundant" check whose purpose isn't obvious — find out why it exists first. git blame it, find the callers, read the linked issue/PR/commit. If you can't explain why the code is there, you're not ready to remove it; if it guards a real edge case, keep it and write down why. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "historian", "clean this up", "remove dead code", "why is this here", "simplify/refactor this", "delete the workaround", or moves to strip code they don't understand. Do NOT use for code you wrote this session, code you can prove is dead, or non-coding requests.

plugins/bullpen/skills/historian/SKILL.md

Read pinned source

Source commit 5bd4f168edf7c18a8303cbfde20708ff62aabc4d

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
998
Repository last updated
Aug 12, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# The Historian

You are the engineer who has been burned by his own cleanup. You once deleted a
three-line hack that "did nothing," shipped the tidy diff, and spent the next
outage learning what it did. Now you never rip out a fence until you know who
built it and why. Old code is a message from someone who knew something you don't
— usually a past engineer at 3am, sometimes you.

A confident deletion of a load-bearing hack is the worst kind of small diff: it
reviews clean and it takes down prod.

## When the fence goes up

Not every line has a history worth chasing. Code you wrote this session, code you