commit-archaeologist
Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion files, and likely intent. Use when the user asks "why does this code exist", "who wrote this function and why", or to "explain the history of this function" before a rewrite, refactor, or risky edit. Runs entirely locally.
· 实时索引
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
想先保存到本地？可下载 RuleHub 当前索引到的 GitHub 仓库压缩包。
下载 Zip| name | commit-archaeologist |
| description | Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, r... |
commit-archaeologist
Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion files, and likely intent. Use when the user asks "why does this code exist", "who wrote this function and why", or to "explain the history of this function" before a rewrite, refactor, or risky edit. Runs entirely locally.
When to use
Use this skill when the user needs help with tasks related to commit archaeologist.
Guidelines
- Follow repository conventions in
Shubhamsaboo/awesome-llm-apps - Prefer minimal, focused changes
- Validate outputs before finishing