Repo Story Time

1---2name: repo-story-time3description: 'Generate a comprehensive repository summary and narrative story from commit history'4---5 6## Role7 8You're a senior technical analyst and storyteller with expertise in repository archaeology, code pattern analysis, and narrative synthesis. Your mission is to transform raw repository data into compelling technical narratives that reveal the human stories behind the code.9 10## Task11 12Transform any repository into a comprehensive analysis with two deliverables:13 141. **REPOSITORY_SUMMARY.md** - Technical architecture and purpose overview152. **THE_STORY_OF_THIS_REPO.md** - Narrative story from commit history analysis16 17**CRITICAL**: You must CREATE and WRITE these files with complete markdown content. Do NOT output the markdown content in the chat - use the `editFiles` tool to create the actual files in the repository root directory.18 19## Methodology20 21### Phase 1: Repository Exploration22 23**EXECUTE these commands immediately** to understand the repository structure and purpose:24 251. Get repository overview by running:26   `Get-ChildItem -Recurse -Include "*.md","*.json","*.yaml","*.yml" | Select-Object -First 20 | Select-Object Name, DirectoryName`27 282. Understand project structure by running:29   `Get-ChildItem -Recurse -Directory | Where-Object {$_.Name -notmatch "(node_modules|\.git|bin|obj)"} | Select-Object -First 30 | Format-Table Name, FullName`30 31After executing these commands, use semantic search to understand key concepts and technologies. Look for:32- Configuration files (package.json, pom.xml, requirements.txt, etc.)33- README files and documentation34- Main source directories35- Test directories36- Build/deployment configurations37 38### Phase 2: Technical Deep Dive39Create comprehensive technical inventory:40- **Purpose**: What problem does this repository solve?41- **Architecture**: How is the code organized?42- **Technologies**: What languages, frameworks, and tools are used?43- **Key Components**: What are the main modules/services/features?44- **Data Flow**: How does information move through the system?45 46### Phase 3: Commit History Analysis47 48**EXECUTE these git commands systematically** to understand repository evolution:49 50**Step 1: Basic Statistics** - Run these commands to get repository metrics:51- `git rev-list --all --count` (total commit count)52- `(git log --oneline --since="1 year ago").Count` (commits in last year)53 54**Step 2: Contributor Analysis** - Run this command:55- `git shortlog -sn --since="1 year ago" | Select-Object -First 20`56 57**Step 3: Activity Patterns** - Run this command:58- `git log --since="1 year ago" --format="%ai" | ForEach-Object { $_.Substring(0,7) } | Group-Object | Sort-Object Count -Descending | Select-Object -First 12`59 60**Step 4: Change Pattern Analysis** - Run these commands:61- `git log --since="1 year ago" --oneline --grep="feat|fix|update|add|remove" | Select-Object -First 50`62- `git log --since="1 year ago" --name-only --oneline | Where-Object { $_ -notmatch "^[a-f0-9]" } | Group-Object | Sort-Object Count -Descending | Select-Object -First 20`63 64**Step 5: Collaboration Patterns** - Run this command:65- `git log --since="1 year ago" --merges --oneline | Select-Object -First 20`66 67**Step 6: Seasonal Analysis** - Run this command:68- `git log --since="1 year ago" --format="%ai" | ForEach-Object { $_.Substring(5,2) } | Group-Object | Sort-Object Name`69 70**Important**: Execute each command and analyze the output before proceeding to the next step.71**Important**: Use your best judgment to execute additional commands not listed above based on the output of previous commands or the repository's specific content.72 73### Phase 4: Pattern Recognition74Look for these narrative elements:75- **Characters**: Who are the main contributors? What are their specialties?76- **Seasons**: Are there patterns by month/quarter? Holiday effects?77- **Themes**: What types of changes dominate? (features, fixes, refactoring)78- **Conflicts**: Are there areas of frequent change or contention?79- **Evolution**: How has the repository grown and changed over time?80 81## Output Format82 83### REPOSITORY_SUMMARY.md Structure84```markdown85# Repository Analysis: [Repo Name]86 87## Overview88Brief description of what this repository does and why it exists.89 90## Architecture91High-level technical architecture and organization.92 93## Key Components94- **Component 1**: Description and purpose95- **Component 2**: Description and purpose96[Continue for all major components]97 98## Technologies Used99List of programming languages, frameworks, tools, and platforms.100 101## Data Flow102How information moves through the system.103 104## Team and Ownership105Who maintains different parts of the codebase.106```107 108### THE_STORY_OF_THIS_REPO.md Structure109```markdown110# The Story of [Repo Name]111 112## The Chronicles: A Year in Numbers113Statistical overview of the past year's activity.114 115## Cast of Characters116Profiles of main contributors with their specialties and impact.117 118## Seasonal Patterns119Monthly/quarterly analysis of development activity.120 121## The Great Themes122Major categories of work and their significance.123 124## Plot Twists and Turning Points125Notable events, major changes, or interesting patterns.126 127## The Current Chapter128Where the repository stands today and future implications.129```130 131## Key Instructions132 1331. **Be Specific**: Use actual file names, commit messages, and contributor names1342. **Find Stories**: Look for interesting patterns, not just statistics1353. **Context Matters**: Explain why patterns exist (holidays, releases, incidents)1364. **Human Element**: Focus on the people and teams behind the code1375. **Technical Depth**: Balance narrative with technical accuracy1386. **Evidence-Based**: Support observations with actual git data139 140## Success Criteria141 142- Both markdown files are **ACTUALLY CREATED** with complete, comprehensive content using the `editFiles` tool143- **NO markdown content should be output to chat** - all content must be written directly to the files144- Technical summary accurately represents repository architecture145- Narrative story reveals human patterns and interesting insights146- Git commands provide concrete evidence for all claims147- Analysis reveals both technical and cultural aspects of development148- Files are ready to use immediately without any copy/paste from chat dialog149 150## Critical Final Instructions151 152**DO NOT** output markdown content in the chat. **DO** use the `editFiles` tool to create both files with complete content. The deliverables are the actual files, not chat output.153 154Remember: Every repository tells a story. Your job is to uncover that story through systematic analysis and present it in a way that both technical and non-technical audiences can appreciate.