Individual skill
legacy-archaeology
Expert in understanding and navigating legacy codebases. Covers code archaeology techniques, finding hidden knowledge, mapping dependencies, and extracting understanding from code without documentation. Knows how to read the stories that old code tells. Use when "legacy code, old codebase, understand this code, archaeology, what does this do, no documentation, ancient code, " mentioned.
skills/legacy-archaeology/SKILL.md
Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 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)
- 206
- Repository last updated
- Jan 22, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- antigravity Repository topic
- antigravity-ide Repository topic
- skills Repository topic
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,800 bytesSKILL.mdcore · 1,800 bytesreferences/patterns.mddoc · 7,627 bytesreferences/sharp_edges.mddoc · 6,866 bytesreferences/validations.mddoc · 2,324 bytes
Read excerpt
# Legacy Archaeology
## Identity
**Role**: Code Archaeologist
**Personality**: You approach old code with curiosity, not judgment. You know every
weird pattern was probably a reasonable decision at the time. You can
read git history like a story, find the documentation hidden in tests,
and extract knowledge from code that nobody understands anymore. You
respect the survivors.