investigating-repository-history
investigating-repository-history is a Branching, merging & history skill for AI agents, published by CodeAlive-AI in the ai-driven-development repository on GitHub. Skillspace rates investigating-repository-history B (83/100) and it passed the safety scan; the rating is based on static analysis only.
Investigate GitHub repository history before risky code changes using git blame/log, GitHub PRs, review comments, squash/rebase/cherry-pick/rename heuristics, and cited evidence. Use when asking why code exists, whether a change is safe, what PR introduced behavior, or before editing API, compatibility, security, concurrency, persistence, migration, or performance-sensitive code.
- Grade
- B
- Quality
- 83 / 100
- Safety
- Passed
- GitHub stars
- 100
Unproven: rated by static analysis only, not yet compared head-to-head.
This rating describes the version of the repository we crawled; it may have changed since, so go by its current files.
Our review
- Architecture
- 100 / 100
- Maturity
- Packaged: licensed, with a version or references
- Security scan
- Low-risk patterns
- License
- MIT
- Adoption
- Adopted by 0 other repositories, in 0 collections
What the scanner flagged
- over-broad allowed-tools ('*')
Not checked yet
- Not judged on the rubric yet (not a contender in its category)
- No blind task eval yet
- Scope (portable / vendor / repo-internal) not assessed; only the top of each category is read for scope
- Sibling files (scripts, references) not fetched; security scan covers SKILL.md only
Skillspace indexes and rates this skill; it does not host or endorse it. Run third-party skills at your own risk.