agentleFS
milad-ahmdmilad-ahmd/agent-skills/skills/codebase-time-machine/SKILL.md

codebase-time-machine

Skill5 starsChanged 14 days agoMITView on GitHub

Tells the story of a codebase from its git history as an entertaining documentary, with eras, key contributors, plot twists (reverts, giant commits, long silences), cursed files, and the current state, backed by a git analysis script. Useful for onboarding, retrospectives, anniversaries, and fun. Use when the user asks for the history of a repo, how a project evolved, a repo story or timeline, or "who built what and when".

The file

Files
SKILL.md

Codebase Time Machine ⏳

"In the beginning, there was Initial commit…"

1. Collect the facts

python3 scripts/git_timeline.py [path/to/repo]        # defaults to current directory
python3 scripts/git_timeline.py . --max 5000          # limit for huge repos
git -C <repo> tag --sort=creatordate | tail -20       # releases, if any

The script reports the span, commits per year, top authors, the biggest commits, the most-changed ("cursed") files, reverts and hotfixes, and the longest silence. Read key commits (git show --stat <hash>) before narrating them.

2. Narrate (default style: nature documentary; also epic, noir, sports commentary or plain)

# 🎬 <Project>: The Story So Far
## Prologue: <first commit date, first message, first files>
## Chapter 1: <era name> (<years>): what was built, by whom, defining commits
## Chapter 2: ...   (split eras by activity bursts, long gaps, big refactors, major tags)
## 🎭 The Cast: top contributors and what they shaped (no judgments about people)
## 🌪️ Plot Twists: reverts, giant commits, the great silence of <dates>
## 👻 Cursed Files: most-changed files and why they keep changing
## 📍 Present Day: current state, active areas
## 🧭 Lessons for newcomers: where the dragons are, what to read first

Rules

  • Facts come only from git. Quote commit messages exactly, with their short hashes. Speculation is labelled as such ("probably", "it seems").
  • Be kind about people. Celebrate them; never mock them. Don't print email addresses.
  • For private or company repos, ask before producing anything meant to be shared publicly.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.