awesome-git-history-salvage SKILL.md skillA
awesome-git-history-salvage from khasky/awesome-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add khasky/awesome-agent-skills/awesome-git-history-salvage@git:20261020.58ea4e8Pins git:20261020.58ea4e8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- khasky/awesome-agent-skills
- Path
skills/awesome-git-history-salvage/SKILL.md- Versions recorded
- 15
- Latest version
- git:20261020.58ea4e8, committed Oct 20, 2026
- First version recorded
- Aug 30, 2026
- Size
- 22,319 bytes
- Repository stars
- 30
- License
- MIT
Read-only recovery of every commit a repository ever held, force-pushed history included, from refs, PR refs, backups and the host's activity log. Use when asked what a repo held before a rewrite.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Git History Salvage
Answer one question completely: what has this repository ever contained? Not what `git log` shows — that is only the current branch. The full set includes commits erased by every force-push the repository has taken, commits that live only on a merged pull request's ref, and commits on branches deleted years ago.
Why it is not just `git log --all`: a force-push replaces a ref, it does not delete objects. The objects stay on the host, unreachable, and the host keeps a public record of every ref state in its activity log. Those two facts together are what makes the old history recoverable — but only if you know that `git fetch origin <sha>` serves an unreachable commit while `GET /repos/{owner}/{repo}/commits/{sha}` answers `422 No commit found` for the same SHA. The git protocol succeeds where REST refuses, and that asymmetry is the whole technique.
## Core principle
…Read the whole file at its exact version.
How to install
mdr add khasky/awesome-agent-skills/awesome-git-history-salvage@sha256:46093b23a47710c1The line at the top of this page pins the label git:20261020.58ea4e8, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_pdzfoodar6ixqkrx)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 15 versions of this file, between Aug 30, 2026 and Oct 20, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.58ea4e8 latest | 2026-10-20 | 58ea4e8 | 22,319 B | A | view · diff |
| git:20261019.a19c2a5 | 2026-10-19 | a19c2a5 | 22,765 B | A | view · diff |
| git:20261018.a4259a5 | 2026-10-18 | a4259a5 | 22,733 B | A | view · diff |
| git:20261010.3b37a6b | 2026-10-10 | 3b37a6b | 22,639 B | A | view · diff |
| git:20260925.eca990b | 2026-09-25 | eca990b | 22,228 B | A | view · diff |
| git:20260925.d850440 | 2026-09-25 | d850440 | 22,336 B | A | view · diff |
| git:20260925.34d9fac | 2026-09-25 | 34d9fac | 22,683 B | A | view · diff |
| git:20260918.18278a0 | 2026-09-18 | 18278a0 | 22,450 B | A | view · diff |
| git:20260918.427dc55 | 2026-09-18 | 427dc55 | 22,351 B | A | view · diff |
| git:20260910.ad72ad4 | 2026-09-10 | ad72ad4 | 22,145 B | A | view · diff |
| git:20260905.8f890b1 | 2026-09-05 | 8f890b1 | 22,289 B | A | view · diff |
| git:20260830.a6035fb | 2026-08-30 | a6035fb | 22,739 B | A | view · diff |
| git:20260830.1286b5c | 2026-08-30 | 1286b5c | 22,272 B | A | view · diff |
| git:20260830.02993b4 | 2026-08-30 | 02993b4 | 16,399 B | A | view · diff |
| git:20260830.cc7dede | 2026-08-30 | cc7dede | 16,439 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (22319 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
khasky/awesome-agent-skills · 30 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pdzfoodar6ixqkrx GET https://markdownregistry.com/api/v1/resolve?ref=khasky/awesome-agent-skills/awesome-git-history-salvage GET https://markdownregistry.com/api/v1/blob/46093b23a47710c1395958f0fab4fe132f7241c6eda1f21c401f7d7d8573b2b3
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.