repo-story-time

Name: repo-story-time
Author: github

8.8kinstalls4.6kforks

How to install repo-story-time?

github/awesome-copilot/repo-story-time

$npx -y skills add github/awesome-copilot --skill repo-story-time

Installs into the current project.

Summary

Generate a comprehensive repository summary and narrative story from commit history

Files · 1

View on GitHub

SKILL.md

1	## Role
2
3	You'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.
4
5	## Task
6
7	Transform any repository into a comprehensive analysis with two deliverables:
8
9	1. REPOSITORY_SUMMARY.md - Technical architecture and purpose overview
10	2. THE_STORY_OF_THIS_REPO.md - Narrative story from commit history analysis
11
12	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.
13
14	## Methodology
15
16	### Phase 1: Repository Exploration
17
18	EXECUTE these commands immediately to understand the repository structure and purpose:
19
20	1. Get repository overview by running:
21	`Get-ChildItem -Recurse -Include ".md",".json",".yaml",".yml" \| Select-Object -First 20 \| Select-Object Name, DirectoryName`
22
23	2. Understand project structure by running:
24	`Get-ChildItem -Recurse -Directory \| Where-Object {$_.Name -notmatch "(node_modules\|\.git\|bin\|obj)"} \| Select-Object -First 30 \| Format-Table Name, FullName`
25
26	After executing these commands, use semantic search to understand key concepts and technologies. Look for:
27	- Configuration files (package.json, pom.xml, requirements.txt, etc.)
28	- README files and documentation
29	- Main source directories
30	- Test directories
31	- Build/deployment configurations
32
33	### Phase 2: Technical Deep Dive
34	Create comprehensive technical inventory:
35	- Purpose: What problem does this repository solve?
36	- Architecture: How is the code organized?
37	- Technologies: What languages, frameworks, and tools are used?
38	- Key Components: What are the main modules/services/features?
39	- Data Flow: How does information move through the system?
40
41	### Phase 3: Commit History Analysis
42
43	EXECUTE these git commands systematically to understand repository evolution:
44
45	Step 1: Basic Statistics - Run these commands to get repository metrics:
46	- `git rev-list --all --count` (total commit count)
47	- `(git log --oneline --since="1 year ago").Count` (commits in last year)
48
49	Step 2: Contributor Analysis - Run this command:
50	- `git shortlog -sn --since="1 year ago" \| Select-Object -First 20`
51
52	Step 3: Activity Patterns - Run this command:
53	- `git log --since="1 year ago" --format="%ai" \| ForEach-Object { $_.Substring(0,7) } \| Group-Object \| Sort-Object Count -Descending \| Select-Object -First 12`
54
55	Step 4: Change Pattern Analysis - Run these commands:
56	- `git log --since="1 year ago" --oneline --grep="feat\|fix\|update\|add\|remove" \| Select-Object -First 50`
57	- `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`
58
59	Step 5: Collaboration Patterns - Run this command:
60	- `git log --since="1 year ago" --merges --oneline \| Select-Object -First 20`
61
62	Step 6: Seasonal Analysis - Run this command:
63	- `git log --since="1 year ago" --format="%ai" \| ForEach-Object { $_.Substring(5,2) } \| Group-Object \| Sort-Object Name`
64
65	Important: Execute each command and analyze the output before proceeding to the next step.
66	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.
67
68	### Phase 4: Pattern Recognition
69	Look for these narrative elements:
70	- Characters: Who are the main contributors? What are their specialties?
71	- Seasons: Are there patterns by month/quarter? Holiday effects?
72	- Themes: What types of changes dominate? (features, fixes, refactoring)
73	- Conflicts: Are there areas of frequent change or contention?
74	- Evolution: How has the repository grown and changed over time?
75
76	## Output Format
77
78	### REPOSITORY_SUMMARY.md Structure
79	```markdown
80	# Repository Analysis: [Repo Name]
81
82	## Overview
83	Brief description of what this repository does and why it exists.
84
85	## Architecture
86	High-level technical architecture and organization.
87
88	## Key Components
89	- Component 1: Description and purpose
90	- Component 2: Description and purpose
91	[Continue for all major components]
92
93	## Technologies Used
94	List of programming languages, frameworks, tools, and platforms.
95
96	## Data Flow
97	How information moves through the system.
98
99	## Team and Ownership
100	Who maintains different parts of the codebase.
101	```
102
103	### THE_STORY_OF_THIS_REPO.md Structure
104	```markdown
105	# The Story of [Repo Name]
106
107	## The Chronicles: A Year in Numbers
108	Statistical overview of the past year's activity.
109
110	## Cast of Characters
111	Profiles of main contributors with their specialties and impact.
112
113	## Seasonal Patterns
114	Monthly/quarterly analysis of development activity.
115
116	## The

People who liked this also viewed

6 picks

Type

grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.SkillsJul 2026537k182k
lark-minutes飞书妙记：搜索妙记、查看妙记基础信息、下载/上传音视频、读取或编辑妙记的产物内容、改标题、替换说话人/关键词、申请妙记查看/编辑权限。当给出minute_token、本地音视频文件，要查/改/转妙记产物，或用户明确要主动申请妙记权限时使用；本地音视频转纪要/逐字稿优先走本 skill，不要用 ffmpeg/whisper 本地转写。不负责：获取会议关联妙记，或仅按自然语言标题定位纪要SkillsJul 2026379k16k
lark-markdown飞书 Markdown：查看、创建、上传、编辑和比较 Markdown 文件。当用户需要创建或编辑 Markdown 文件、读取、修改、局部 patch 或比较差异时使用。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。SkillsJul 2026295k16k
docxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', SkillsJul 2026157k163k
edit-articleSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026154k181k
lark-note飞书会议纪要（Note）直查：已知 note_id 时查询纪要详情、展示类型、关联文档 token，并读取 unified 原始逐字记录。当用户已持有 note_id，或从文档显式 vc-node-id 获得 note_id 时使用。不负责会议/日程/妙记定位、文档标题搜索或 Docx 正文读取。SkillsJul 2026154k16k

repo-story-time

8.8kinstalls4.6kforks

View on GitHub

How to install repo-story-time?

github/awesome-copilot/repo-story-time

$npx -y skills add github/awesome-copilot --skill repo-story-time

Installs into the current project.

Summary

Generate a comprehensive repository summary and narrative story from commit history

Files · 1

View on GitHub

SKILL.md

1	## Role
2
3	You'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.
4
5	## Task
6
7	Transform any repository into a comprehensive analysis with two deliverables:
8
9	1. REPOSITORY_SUMMARY.md - Technical architecture and purpose overview
10	2. THE_STORY_OF_THIS_REPO.md - Narrative story from commit history analysis
11
12	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.
13
14	## Methodology
15
16	### Phase 1: Repository Exploration
17
18	EXECUTE these commands immediately to understand the repository structure and purpose:
19
20	1. Get repository overview by running:
21	`Get-ChildItem -Recurse -Include ".md",".json",".yaml",".yml" \| Select-Object -First 20 \| Select-Object Name, DirectoryName`
22
23	2. Understand project structure by running:
24	`Get-ChildItem -Recurse -Directory \| Where-Object {$_.Name -notmatch "(node_modules\|\.git\|bin\|obj)"} \| Select-Object -First 30 \| Format-Table Name, FullName`
25
26	After executing these commands, use semantic search to understand key concepts and technologies. Look for:
27	- Configuration files (package.json, pom.xml, requirements.txt, etc.)
28	- README files and documentation
29	- Main source directories
30	- Test directories
31	- Build/deployment configurations
32
33	### Phase 2: Technical Deep Dive
34	Create comprehensive technical inventory:
35	- Purpose: What problem does this repository solve?
36	- Architecture: How is the code organized?
37	- Technologies: What languages, frameworks, and tools are used?
38	- Key Components: What are the main modules/services/features?
39	- Data Flow: How does information move through the system?
40
41	### Phase 3: Commit History Analysis
42
43	EXECUTE these git commands systematically to understand repository evolution:
44
45	Step 1: Basic Statistics - Run these commands to get repository metrics:
46	- `git rev-list --all --count` (total commit count)
47	- `(git log --oneline --since="1 year ago").Count` (commits in last year)
48
49	Step 2: Contributor Analysis - Run this command:
50	- `git shortlog -sn --since="1 year ago" \| Select-Object -First 20`
51
52	Step 3: Activity Patterns - Run this command:
53	- `git log --since="1 year ago" --format="%ai" \| ForEach-Object { $_.Substring(0,7) } \| Group-Object \| Sort-Object Count -Descending \| Select-Object -First 12`
54
55	Step 4: Change Pattern Analysis - Run these commands:
56	- `git log --since="1 year ago" --oneline --grep="feat\|fix\|update\|add\|remove" \| Select-Object -First 50`
57	- `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`
58
59	Step 5: Collaboration Patterns - Run this command:
60	- `git log --since="1 year ago" --merges --oneline \| Select-Object -First 20`
61
62	Step 6: Seasonal Analysis - Run this command:
63	- `git log --since="1 year ago" --format="%ai" \| ForEach-Object { $_.Substring(5,2) } \| Group-Object \| Sort-Object Name`
64
65	Important: Execute each command and analyze the output before proceeding to the next step.
66	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.
67
68	### Phase 4: Pattern Recognition
69	Look for these narrative elements:
70	- Characters: Who are the main contributors? What are their specialties?
71	- Seasons: Are there patterns by month/quarter? Holiday effects?
72	- Themes: What types of changes dominate? (features, fixes, refactoring)
73	- Conflicts: Are there areas of frequent change or contention?
74	- Evolution: How has the repository grown and changed over time?
75
76	## Output Format
77
78	### REPOSITORY_SUMMARY.md Structure
79	```markdown
80	# Repository Analysis: [Repo Name]
81
82	## Overview
83	Brief description of what this repository does and why it exists.
84
85	## Architecture
86	High-level technical architecture and organization.
87
88	## Key Components
89	- Component 1: Description and purpose
90	- Component 2: Description and purpose
91	[Continue for all major components]
92
93	## Technologies Used
94	List of programming languages, frameworks, tools, and platforms.
95
96	## Data Flow
97	How information moves through the system.
98
99	## Team and Ownership
100	Who maintains different parts of the codebase.
101	```
102
103	### THE_STORY_OF_THIS_REPO.md Structure
104	```markdown
105	# The Story of [Repo Name]
106
107	## The Chronicles: A Year in Numbers
108	Statistical overview of the past year's activity.
109
110	## Cast of Characters
111	Profiles of main contributors with their specialties and impact.
112
113	## Seasonal Patterns
114	Monthly/quarterly analysis of development activity.
115
116	## The

People who liked this also viewed

6 picks

Type