What is repo-timeline?

A repository-history tool that turns commits, changelogs, pull requests, and Linear tickets into a grouped timeline explaining what changed and why.

Use it to study a branch or repository, investigate when changes happened, and connect code changes with pull requests or tickets.

It makes a raw version-control history easier to understand by organizing related changes into meaningful engineering work.

repo-timeline — Skill for Claude Code by mostafa-drz

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add mostafa-drz/claude-skills --skill repo-timeline

Clone the repo

git clone --depth 1 https://github.com/mostafa-drz/claude-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/repo-timeline/github.svg)](https://agentmods.dev/skills/mostafa-drz/claude-skills/repo-timeline)

Your own site

<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/repo-timeline"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/repo-timeline/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/repo-timeline"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/repo-timeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,768 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00067	$0.02768
Opus 5	$0.00034	$0.01384
Sonnet 5	$0.00013	$0.00554
Haiku 4.5	$0.00007	$0.00277

Measured today against content hash 645d4de197c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

repo-timeline scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

code/repo-timeline/SKILL.md · 292 lines

How it starts

The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repo Timeline

Visualize the history of a repository or branch as a meaningful, grouped timeline — not raw git log, but an engineer-friendly narrative of what changed, when, and why.

Preferences

On startup, use the Read tool to load ~/.claude/skills/repo-timeline/preferences.md. If it doesn't exist, use defaults.

Context

On startup, use Bash to detect: current git branch, repo root (git rev-parse --show-toplevel), repo name (basename $(git rev-parse --show-toplevel)), remote URL (git remote get-url origin), and GitHub repo name (gh repo view --json nameWithOwner -q .nameWithOwner). Skip any that fail.

Command routing

Check $ARGUMENTS:

help → display help then stop
config → interactive setup then stop
reset → delete ~/.claude/skills/repo-timeline/preferences.md, confirm, stop
branch name — if argument looks like a branch name (no -- prefix), use it as the target branch
flags — parse --since, --until, --focus, --depth, --sources
empty — use current branch with defaults

Flags

Parse from $ARGUMENTS:

--since <time> — start of time range (e.g., "2 weeks ago", "2026-01-01", "last tag")
--until <time> — end of time range (defaults to now)
--focus <areas> — comma-separated paths or areas to emphasize (e.g., "api,auth,frontend")
--depth brief|detailed — "brief" for one-liners, "detailed" for full descriptions (default from preferences)
--sources <list> — comma-separated sources: git, github, linear, changelog (default: all available)

Help

Repo Timeline — Engineer-friendly timeline of repository changes

Usage:
  /repo-timeline                              Current branch, full history
  /repo-timeline feature/auth                 Specific branch
  /repo-timeline --since "2 weeks ago"        Time-bounded timeline
  /repo-timeline --focus "api,auth"           Focus on specific areas
  /repo-timeline --depth brief                One-liners only
  /repo-timeline --depth detailed             Full descriptions with context
  /repo-timeline --sources git,github         Only specific sources
  /repo-timeline config                       Set preferences
  /repo-timeline reset                        Clear preferences
  /repo-timeline help                         This help

Flags:
  --since <time>          Start of time range (e.g., "1 month ago", "v2.0.0")
  --until <time>          End of time range (default: now)
  --focus <areas>         Comma-separated paths/areas to emphasize
  --depth brief|detailed  Level of detail (default: from preferences)
  --sources <list>        Sources to use: git, github, linear, changelog

Examples:
  /repo-timeline                              Full timeline of current branch
  /repo-timeline main --since "last month"    Main branch, last month
  /repo-timeline --focus "src/api" --depth detailed
  /repo-timeline --since "v1.0.0" --until "v2.0.0"   Between releases
  /repo-timeline develop --sources git,github

Current preferences:
  (read from preferences.md)

Read the full file on GitHub · 292 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

today Changed · +2 lines 645d4de197c3
12d ago First seen · 290 lines · 67 tokens per session scan A f465c233436c

Subscribe to this mod's changes

repo-timeline is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 2,768 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Git and workflow Research ai-tools automation claude claude-skills developer-tools

git-pushing

Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.

mhattingpete/claude-skills-marketplace · 70 tokens

iterate

Diverge-converge workflow: spin up N agents on isolated worktrees, each exploring a different approach to the same problem. Compare results side-by-side (with optional preview ports), pick a winner, merge it back. Use when the user says /iterate, 'try multiple approaches', 'explore different directions', or wants to…

SZoloth/skill-pack · 73 tokens

repo-timeline