awesome-git-history-reset SKILL.md skillA
awesome-git-history-reset 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-reset@git:20261019.a19c2a5Pins git:20261019.a19c2a5 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-reset/SKILL.md- Versions recorded
- 14
- Latest version
- git:20261019.a19c2a5, committed Oct 19, 2026
- First version recorded
- Aug 1, 2026
- Size
- 22,051 bytes
- Repository stars
- 30
- License
- MIT
Erases a repository's entire history into one fresh commit and force-pushes, after access checks, a mirror backup, a secret scan and a confirmation gate. Use when asked to wipe history.
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 Reset Collapse a repository's entire history into one fresh `Initial commit` and force-push it, so the published commit log starts clean. The file tree is preserved byte-for-byte; only the history leading to it is discarded. Why the ceremony: this is an irreversible, outward-facing rewrite of a shared remote. Once you force-push, every old commit on the default branch is gone from the tip, open pull requests break, and anyone who cloned or forked keeps the old history anyway. The steps below are not bureaucracy — each one closes a specific way this goes wrong: pushing without write access, discovering too late that the branch was protected, losing content in the squash, or force-pushing over a teammate's commit you never saw. ## Core principle NOTHING IRREVERSIBLE UNTIL FOUR THINGS HOLD: write access is confirmed, a mirror backup exists and is verified, the history is scanned for secrets, and the user has explicitly confirmed the wipe. If any one is missing, stop at that gate. Four invariants hold throughout: …
Read the whole file at its exact version.
How to install
mdr add khasky/awesome-agent-skills/awesome-git-history-reset@sha256:bcdf4869ac5f00baThe line at the top of this page pins the label git:20261019.a19c2a5, 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_wu53woh44kofsoss)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 14 versions of this file, between Aug 1, 2026 and Oct 19, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.a19c2a5 latest | 2026-10-19 | a19c2a5 | 22,051 B | A | view · diff |
| git:20261010.3b37a6b | 2026-10-10 | 3b37a6b | 21,993 B | A | view · diff |
| git:20260925.eca990b | 2026-09-25 | eca990b | 18,752 B | A | view · diff |
| git:20260925.d850440 | 2026-09-25 | d850440 | 18,876 B | A | view · diff |
| git:20260925.34d9fac | 2026-09-25 | 34d9fac | 19,077 B | A | view · diff |
| git:20260918.18278a0 | 2026-09-18 | 18278a0 | 18,885 B | A | view · diff |
| git:20260918.427dc55 | 2026-09-18 | 427dc55 | 18,774 B | A | view · diff |
| git:20260912.33abc13 | 2026-09-12 | 33abc13 | 18,400 B | A | view · diff |
| git:20260910.ad72ad4 | 2026-09-10 | ad72ad4 | 18,403 B | A | view · diff |
| git:20260905.a1251e4 | 2026-09-05 | a1251e4 | 18,563 B | A | view · diff |
| git:20260802.aa89bd6 | 2026-08-02 | aa89bd6 | 18,813 B | A | view · diff |
| git:20260802.de82059 | 2026-08-02 | de82059 | 18,189 B | A | view · diff |
| git:20260802.ffe5426 | 2026-08-02 | ffe5426 | 17,981 B | A | view · diff |
| git:20260801.cae96e2 | 2026-08-01 | cae96e2 | 15,490 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 (22051 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_wu53woh44kofsoss GET https://markdownregistry.com/api/v1/resolve?ref=khasky/awesome-agent-skills/awesome-git-history-reset GET https://markdownregistry.com/api/v1/blob/bcdf4869ac5f00ba2b0b7cd795ebd738e6fecaf9846819103686875ae0880812
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.