investigating-repository-history

SKILLWorkflowcommunity
v0.0.0CodeAlive-AIMITUpdated 1d agoSource →

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, compatibil

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
123Repo stars
1Clients
1Formats
1d agoLast update
Skill
AuthorCodeAlive-AI
Version0.0.0
LicenseMIT
CategoryWorkflow
Formatsskill.md
PromptNot published
Compatibility
Claude✓ Supported
Cursor—
Copilot—
ChatGPT—
Gemini—
About

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.

Keywords
skillclaude