- Dataset
- 2026-10-27-catalog-ai-v2
- Ruleset
- b2e8889c66f7
- Scanned
- 2026-10-27
- Window
- February–September 15, 2026
A git prepare-commit-msg hook for authoring commit messages with LLMs.
01Result
zurawiki/gptcommit ↗zurawiki/gptcommit AI coding statistics: 100%
One person is driving this. The headline number reflects a single contributor's workflow, not a project-wide shift.
02Drivers
What shapes this result
Mode, timing, and detected signatures show whether the result reflects broad adoption or one concentrated workflow.
Assisted or autonomous
Assisted — a developer’s identity authored the commit and the agent added itself as co-author. Autonomous — a bot identity authored the commit without a human identity attached.
Which agents
| Agent | Vendor | Commits | Share |
|---|---|---|---|
| Claude Code | Anthropic | 3 | 100% |
03Evidence
Inspect the matches
Public commit samples let you inspect the signatures behind the aggregate result.
Matched commit samples
314f6d9eon GitHubAdd release notes config and update GitHub Actions depsClaude Code509e0363on GitHubFix default model routing and tiktoken fallbackClaude Code75639782on GitHubFix CI pipelineClaude Code
04Method
What entered the denominator
The result begins with commit history, removes merges and routine automation, and reports literal agent signatures as a lower bound.
Exclusion ledger
| Commits in window | 3 |
| Merge commits removed | −0 |
| CI / dependency bots removed | −0 |
| Considered | 3 |
Bots are excluded from the denominator entirely. Agent attribution requires a literal supported signature; no code-style inference is used.
Continue exploring
Related coding-agent evidence
Run the same detector locally.
Deterministic signature matching; no code-style inference. Squash merges can remove trailers, so this result remains a measured floor.
npx qmmit-cli zurawiki/gptcommit