worktree-index-corrupt-async-post-commit-hook SKILL.md skillA
worktree-index-corrupt-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/worktree-index-corrupt-async-post-commit-hook@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/worktree-index-corrupt-async-post-commit-hook/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.0, committed Aug 11, 2026
- First version recorded
- May 13, 2026
- Size
- 8,980 bytes
- Repository stars
- 3
- License
- MIT
Fix `fatal: unable to read <sha>` or `invalid sha1 pointer in cache-tree of .git/worktrees/<name>/index` errors that surface when running git operations (`git status`, `git rebase`, `git pull`) in worktree B shortly after committing in sibling worktree A — when the project has an async post-commit hook (a hook that runs `&`, `nohup`, or "running ... in background"). Use when: (1) error message points at worktree B's index but you weren't editing B, (2) you just merged/squashed/committed in…
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
# Worktree index corruption from async post-commit hooks
## Problem
You commit in worktree A. Immediately afterwards (within seconds), you run
`git status` / `git rebase origin/main` / `git fetch && git rebase` in
sibling worktree B and get:
```
fatal: unable to read cd2a732cd2d5ad030414b953e21b9e403ab88699
```
or
```
error: cd2a732c...: invalid sha1 pointer in cache-tree of
.../.git/worktrees/<name>/index
error: missing blob b007cf60...
error: missing blob d4077a21...
```
The error blames worktree B, but worktree B was clean and untouched.
`git status` itself fails. `git rebase` aborts before doing anything.
## Why this happens
Linked git worktrees share the underlying object database (`.git/objects/`)
but have **per-worktree index files** at `.git/worktrees/<name>/index`. Each
index's cache-tree caches `(path → tree-sha)` mappings to make `git status`
fast.
When the project has an async post-commit hook — common patterns:
```bash
# hooks/post-commit
[post-commit] Python files changed — running doc update in background...
nohup python3 docs/generate_website.py > /dev/null 2>&1 &
```
— or any hook that writes new objects/refs/files asynchronously after
…Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/worktree-index-corrupt-async-post-commit-hook@sha256:b1199187ccdd6bf9The 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_yxnc3yvhgtlsmctw)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 13, 2026 and Aug 11, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-11 | f274e4b | 8,980 B | A | view · diff |
| v1.0.0 | 2026-08-05 | e3930cf | 8,984 B | A | view · diff |
| v1.0.0 | 2026-07-08 | f1254dd | 9,109 B | A | view · diff |
| v1.1.0 | 2026-05-29 | be514e4 | 9,887 B | A | view · diff |
| v1.0.0 | 2026-05-13 | 07472bf | 9,078 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 (8980 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_yxnc3yvhgtlsmctw GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/worktree-index-corrupt-async-post-commit-hook GET https://markdownregistry.com/api/v1/blob/b1199187ccdd6bf914154f462b825a14da7406323fa547c1cfcce1502fabae92
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.