git-history-forensics

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.

What does this entry provide?

git-history-forensics is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 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. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding git-history-forensics to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.

Snapshot facts

Source: GitHub Skill Search
Quality: 58/100
Install method: codex
Repo: MichaelWeissDEV/owl-registry
Repo updated: Oct 27, 2026

Install command

codex skill install MichaelWeissDEV/owl-registry

Install method: codex

Review the upstream source before running this command.

GitHub project

Quality

Repo stars

Repo updated

Unknown

How is this score calculated?

Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.

Security signals

Scan coverage: Install metadata and the indexed document body.

Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.

Discovery note

# 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

Report an issue with this listing