RepoLore
ChatGPT pluginExplain public code history
RepoLore helps developers understand why public GitHub code exists by tracing files and line ranges through commits, pull requests, issues, patches, and regression evidence.
- Featured
- No
not on the featured shelf
Movement
From our daily snapshots over the last 30 days.
Rank by placement
Rank in Developer tools
3 listing changes logged · latest Sep 22: Status, Availability, Sign-in. See what changed
In its category
How this plugin compares with others in the same category. Positions are counted within the category, not across the whole directory.
Developer tools293rd of 742 by placement
| # | Plugin | Position | 7d |
|---|---|---|---|
| 291 | #4031 | 48places up | |
| 292 | #4034 | 99places down | |
| 293 | #4052 | 103places up | |
| 294 | #4076 | 56places up | |
| 295 | #4077 | 62places up |
Example prompts
- “Explain why lines 93–118 of README.md exist in modelcontextprotocol/typescript-sdk and cite the GitHub evidence.”
- “Build a decision timeline for README.md in modelcontextprotocol/typescript-sdk using commits, pull requests, and issues.”
- “Assess the risks of changing README.md in modelcontextprotocol/typescript-sdk using its public GitHub history.”
Skills
trace-code-history
Reconstruct why code exists by tracing public GitHub file history, commits, pull requests, referenced issues, patches, and tests. Use when a user asks why a file or code region was introduced, whether historical evidence supports removing it, what change motivated it, or which repository artifacts document the decision.
- Categories
- Made by
- DMITRII SERGEEV · Website
- Sign-in
- On Install
- Availability
- Available
- Version
- 1.0.0
- Created
- August 22, 2026
- More info
- Sponsorship
- Promote this plugin