加载中…
Investigate and recover from Git history problems with hypothesis-driven, read-only-first methods: find when/where a bug or change was introduced (bisect, pickaxe, line-history blame), recover lost commits, branches, stashes and dropped work (reflog, fsck), and reason about what gc and expiry will delete. Use when someone asks "who/when/why did this change", "I lost my commits after reset/rebase/force-push", "find the commit that broke X", "recover a deleted branch or dropped stash", or "did this secret ever enter history". Not for everyday branching or merging (use git-workflow, git-merge-conflicts), and history rewriting or secret purges are out of scope until the user explicitly authorizes them.
git-history-forensics 是 ChatHome Skills 收录的 技能 条目，来源为 GitHub Skill Search，质量分 58/100。 # Git History Forensics Git almost never destroys data immediately. Commits that look "lost" are usually unreachable, not deleted, and they stay recoverable unt. 作为 agent 技能，它把一组可复用的任务指令打包成 Codex 和 Claude Code 等 AI 编程 agent 可直接加载的格式，无需为该任务手写胶水代码。 该条目由 ChatHome Skills 的每日抓取从官方 registry 和 GitHub 发现查询中收录，每次运行都会重新核验仓库事实、新鲜度信号和安装元数据。 质量分综合了官方 registry 收录情况、可用安装命令、许可证完整性、仓库活跃度和 GitHub star 趋势，完整算法说明见来源页。安装命令已列于上方，可直接复制使用。 在将 git-history-forensics 加入生产 agent 工作流前，请核对上方的最近更新日期和仓库状态——下方事实快照是最近一次抓取的时点值。
codex skill install MichaelWeissDEV/owl-registry运行此命令前，请先核对上游源码。
扫描范围: 安装元数据与已收录的文档正文。
基于安装元数据和有界技能正文的自动风险信号，不是完整代码安全审计，也不会递归审查源码或依赖。
# Git History Forensics Git almost never destroys data immediately. Commits that look "lost" are usually unreachable, not deleted, and they stay recoverable until reflog expiry and