git-rebase-stalls-async-post-commit-hook SKILL.md skillA
git-rebase-stalls-async-post-commit-hook 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/git-rebase-stalls-async-post-commit-hook@v1.1.0Pins v1.1.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/git-rebase-stalls-async-post-commit-hook/SKILL.md- Versions recorded
- 4
- Latest version
- v1.1.0, committed Aug 11, 2026
- First version recorded
- May 13, 2026
- Size
- 14,278 bytes
- Repository stars
- 3
- License
- MIT
Fix `git rebase origin/main` (or any multi-commit rebase) silently stalling mid-replay with `hint: pick <SHA> ... It has been rescheduled; To edit the command before continuing, please edit the todo list first` output, leaving a stuck `.git/worktrees/<name>/rebase-merge/` directory that `git rebase --abort` does NOT clear. Use when: (1) you ran `git rebase origin/main` on a branch with N commits to replay, (2) the rebase output shows partial progress (`Rebasing (1/N)... Rebasing (2/N)...`)…
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 rebase` stalls mid-replay because async post-commit hook holds resources ## Problem You run `git rebase origin/main` on a branch with several commits ahead. The rebase begins applying commits one by one and partway through prints output like: ``` Rebasing (1/10)Rebasing (2/10)...Rebasing (5/10) [post-commit] Python files changed — running doc update in background... hint: hint: pick 8b625b6b8b... fix(runbook): split verification probe ... hint: hint: It has been rescheduled; To edit the command before continuing, please hint: edit the todo list first: hint: hint: git rebase --edit-todo hint: git rebase --continue ``` `git status` reports `## HEAD (no branch)` (detached HEAD), the rebase is not complete, but no merge conflict was raised. `git rebase --abort` appears to succeed silently, but the next `git rebase` reports: ``` fatal: It seems that there is already a rebase-merge directory, and I wonder if you are in the middle of another rebase. ``` You're stuck. The branch can't move forward and the rebase machinery won't reset cleanly. ## Trigger conditions All of these together: 1. Multi-commit rebase (`origin/main` is several commits ahead). …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/git-rebase-stalls-async-post-commit-hook@sha256:d2d0ae7ae01ec4e1The line at the top of this page pins the label v1.1.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_lqmpcedugzrl34ly)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 13, 2026 and Aug 11, 2026, about one every 30 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-08-11 | f274e4b | 14,278 B | A | view · diff |
| v1.1.0 | 2026-08-05 | e3930cf | 14,279 B | A | view · diff |
| v1.1.0 | 2026-07-08 | f1254dd | 14,478 B | A | view · diff |
| v1.0.0 | 2026-05-13 | 07472bf | 12,959 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 (14278 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_lqmpcedugzrl34ly GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/git-rebase-stalls-async-post-commit-hook GET https://markdownregistry.com/api/v1/blob/d2d0ae7ae01ec4e1efef37fe55c274b5a7008ab5d26e1d7631eac626e26f956d
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.