git-amend-hits-async-post-commit-hook-commit SKILL.md skillA
git-amend-hits-async-post-commit-hook-commit 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-amend-hits-async-post-commit-hook-commit@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/git-amend-hits-async-post-commit-hook-commit/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.0, committed Jul 8, 2026
- First version recorded
- May 29, 2026
- Size
- 4,008 bytes
- Repository stars
- 3
- License
- MIT
Use when a `git commit --amend` silently rewrites the WRONG commit in a repo that has an async/background post-commit hook. Trigger: after a normal commit, `git log` shows an unexpected extra commit on top that a background hook created (`[auto-docs] ...`, a docs/site regen, a changelog/checkbox tick) — and a later `--amend` folds your change into THAT hook commit instead of your feature commit. The amend reports success; no error. Also use proactively before instructing subagents to `--amend`…
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 commit --amend` hits the async post-commit hook's commit ## Problem A repo has an **async post-commit hook** — it fires in the background after a commit and creates its OWN follow-up commit (auto-generated docs, a site regen, a changelog or plan-checkbox tick). If you (or a subagent) run `git commit --amend` after that hook has fired, `--amend` rewrites **the hook's commit**, not your work commit. Your change's content is folded into a commit titled e.g. `[auto-docs] ...`; your real `feat(...)` commit is left untouched. The amend "succeeds" — no error — so it is easy to miss. ## Context / Trigger Conditions - The repo has a background/async post-commit hook (look for a `post-commit` hook that backgrounds work, or commits with prefixes like `[auto-docs]`, `chore: regenerate site`, etc. appearing without a human authoring them). - You ran `git commit`, then later `git commit --amend` (often a code-review fix, a typo fix, or "tidy the last commit"). - `git log` shows HEAD's message is the hook's, not yours — and your change is inside that hook commit. - Especially common in **subagent-driven development**: a fix subagent is told …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/git-amend-hits-async-post-commit-hook-commit@sha256:d9f8660ab0999c9eThe 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_hl63jiclkjix3g7b)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 29, 2026 and Jul 8, 2026, about one every 40 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-07-08 | f1254dd | 4,008 B | A | view · diff |
| v1.0.0 | 2026-05-29 | 059688a | 3,977 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 (4008 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_hl63jiclkjix3g7b GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/git-amend-hits-async-post-commit-hook-commit GET https://markdownregistry.com/api/v1/blob/d9f8660ab0999c9e8e5b7e325e07429c9c465654c58fce4140a7da89a8c30d22
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.