async-post-commit-hook-commit-orphaned-by-squash-merge SKILL.md skillA
async-post-commit-hook-commit-orphaned-by-squash-merge from wan-huiyan/agent-traffic-control is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wan-huiyan/agent-traffic-control/async-post-commit-hook-commit-orphaned-by-squash-merge@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wan-huiyan/agent-traffic-control
- Path
plugins/agent-traffic-control/skills/async-post-commit-hook-commit-orphaned-by-squash-merge/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Jul 8, 2026
- Size
- 7,116 bytes
- Repository stars
- 3
- License
- MIT
In a repo with an ASYNC/background post-commit hook (one that fires after a commit and creates its OWN follow-up commit — `[auto-docs] …`, a docs/site regen, a changelog/checkbox tick), the hook's commit can land LOCAL-ONLY *after* your `git push` already captured just your work commit, so it is never in the PR and gets ORPHANED + silently lost when the squash-merged branch is deleted. Use when: (1) you pushed a fix, PR'd it, and squash-merged, then a later `git status -sb` shows your feature…
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
# Async post-commit hook's commit is orphaned by a squash-merge ## Problem A repo has an **async post-commit hook** that fires in the background after each commit and creates its OWN follow-up commit — typically auto-generated docs, a site regen, or a "correct the design doc to match the code you just changed" edit (you'll see `[post-commit] … running doc update in background…` at commit time and an `[auto-docs] …` commit appear seconds-to-minutes later). The race that loses content: 1. You commit your fix (`feat/fix …`). 2. `git push -u origin <branch>` runs — and **completes before the async hook finishes**, so the remote has only your fix commit. 3. You open the PR and squash-merge it. The squash-merge is built from the pushed remote state → it contains only your fix commit. 4. *Then* the background hook's `[auto-docs]` commit lands — **local-only**, on top of your branch. It's never pushed, never in the PR, never on main. Now your local branch is `[ahead 1]` of `origin/<branch>`, holding a commit with real, useful content (e.g. a design doc corrected to match your change). If you delete the merged branch or just start the next task, that content is **silently …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/async-post-commit-hook-commit-orphaned-by-squash-merge@sha256:f8f86593796d669aThe line at the top of this page pins the label v1.0.0, 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_jofkh6v2lnku44nr)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 8, 2026.
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 (7116 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
wan-huiyan/agent-traffic-control · 3 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jofkh6v2lnku44nr GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/async-post-commit-hook-commit-orphaned-by-squash-merge GET https://markdownregistry.com/api/v1/blob/f8f86593796d669acf2fe8a611d5fa35b52704d9207f0ed331dc46ff02ed3861
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.