Generate a comprehensive repository summary and narrative story from commit history
Repo Story Time is a Copilot skill that analyzes a repository and produces two Markdown deliverables: a technical REPOSITORY_SUMMARY.md describing architecture and purpose, and a narrative THE_STORY_OF_THIS_REPO.md that turns commit history into a human-readable story. It addresses the problem of understanding an unfamiliar codebase and its evolution by combining structural analysis with commit-history archaeology.
The skill follows a multi-phase methodology. It first explores repository structure using read-only PowerShell listing commands and semantic search to find configuration, source, and test files. It then builds a technical inventory (purpose, architecture, technologies, key components, data flow) and runs a systematic series of read-only git commands to gather statistics such as total commit count, contributor rankings via git shortlog, monthly activity patterns, change themes, merge/collaboration patterns, and seasonal trends. A pattern-recognition phase interprets contributors as characters, identifies recurring themes and turning points, and traces how the repo has grown. Both output files follow prescribed section templates and must be written directly to disk with an edit-files tool rather than printed to chat.
It targets engineering managers, technical writers, open-source maintainers, and new team members who want an onboarding overview or a shareable narrative of a project's history. All commands it runs are inspection-only (git log, git shortlog, directory listings) with no writes to the repository beyond creating the two summary files.
Two Markdown files written to the repository root: REPOSITORY_SUMMARY.md (technical architecture overview) and THE_STORY_OF_THIS_REPO.md (a narrative built from commit history).
Read-only git commands such as git rev-list, git log, git shortlog, and git merges, plus PowerShell directory listings. None of these modify repository content or history.
The example commands are written for PowerShell (Get-ChildItem, Select-Object, ForEach-Object), so it assumes a PowerShell-capable environment for the exploration and history-analysis steps.
No. The skill explicitly requires writing complete content to the two files using an edit-files tool rather than outputting the Markdown in the chat.
Commit counts, contributor activity, monthly and seasonal patterns, change themes (features/fixes/refactors), most-changed files, and merge/collaboration patterns over roughly the past year.
Quick Setup:
.claude/skills/Repository
github/awesome-copilot