Skill: Code Archaeology

Load this when you must understand existing code before changing it — legacy systems, unfamiliar repos, or mysterious code whose intent isn't obvious.

Core Principle

Code that looks wrong is often right for a reason you can't see yet. Before "fixing" or refactoring unfamiliar code, excavate its history and intent. Chesterton's Fence: don't remove a fence until you know why it was built.

1. Orientation (First Contact with a Repo)

Before touching anything, build a map.