Do an analysis of the number of lines of code added and removed per day since forking, also add numbers of PR, and other interesting stats

[japertechnology]

[github-actions]

Here's the full analysis of the gitclaw repository since forking:

---

📊 Repository Analysis: japer-technology/gitclaw

Forked from: Sawyer Hood's original repo
Fork date: 2026-02-04 (Initial commit)
Analysis date: 2026-02-20
Repo age: 17 days
Current codebase: 92 files, ~14,157 lines of code (excl. binary/lock files)

---

📈 Lines Added / Removed Per Day

Date	Lines Added	Lines Removed	Net Change
2026-02-04	5,892	0	+5,892 (initial commit)
2026-02-05	19	17	+2
2026-02-19	4,247	1,837	+2,410
2026-02-20	7,302	868	+6,434
2026-02-21	4	3	+1
Total	17,464	2,725	+14,739

Feb 20 was the most explosive day — over 7,300 lines added in a single day.

---

🔀 Pull Request Stats

Metric	Count
Total PRs merged	45
Highest PR number referenced	#110
Unique issues referenced	60

PRs by source agent:

Agent	PRs
copilot-swe-agent	37
gitclaw[bot] (Pi)	14*
codex	8

*Some PRs reference both copilot and codex branches

---

👥 Contributors & Commits

Author	Total Commits (non-merge)
JAPER (human)	136
copilot-swe-agent[bot]	80
gitclaw[bot]	41
Sawyer Hood (upstream)	3
Total	260 (+ 45 merge commits = 305 total)

Commits per day:

Date	JAPER	copilot	gitclaw[bot]	Sawyer Hood
Feb 04	—	—	—	1
Feb 05	—	—	—	2
Feb 19	1	35	2	—
Feb 20	130	45	39	—
Feb 21	5	—	—	—

---

🤖 Human vs. Bot Ratio

• Human commits: 139 (53.5%) — JAPER + Sawyer Hood
• Bot commits: 121 (46.5%) — copilot-swe-agent + gitclaw[bot]
• Bot-authored PRs: ~100% of the 45 PRs were created by bots (copilot/codex branches), reviewed/merged by JAPER

---

📁 File Types in Repo

Extension	Count
.md (Markdown docs)	39
.json (state/config)	19
.jsonl (session logs)	15
.yml (workflows)	4
.ts (TypeScript)	4
.py (Python)	3
Other (.txt, .png, .lock, .js, .gitignore, .gitattributes)	8

---

🔥 Interesting Stats

• Busiest day: Feb 20 — 214 commits from 3 authors, 7,302 lines added
• Most renamed files: The project went through extensive reorganization — at least 12 rename-focused commits restructuring from .pi/ → .GITCLAW/ naming conventions
• Largest single additions:
  • GITCLAW-Communication-Channels.md: 1,493 lines in one commit
  • GITCLAW-The-GitHub-Possibilities.md: 970 lines
  • GITCLAW-Interactive-Possibilities.md: 767 lines
  • GITCLAW-Roadmap.md: 512 lines
  • GITCLAW-Delivery-Methods.md: 504 lines
• Dormant period: 14 days of silence between Feb 5 and Feb 19
• Velocity post-activation: Once gitclaw went live on Feb 19, the repo went from 3 commits to 305 in just 2 days
• Issue churn: 60 unique GitHub issues referenced, with issue numbers jumping from Codex-generated pull request #1 to Is it possible to have .GITCLAW/state/** files not be copied when a template is created from the repo? #110 (indicating ~50 issues were opened but not directly committed against)
• Commit message style: 41 commits follow the gitclaw: work on issue #N pattern (all from gitclaw[bot]), showing the Pi agent's autonomous work loop