post-merge SKILL.md skillA
post-merge from swingerman/engineer is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add swingerman/engineer/post-merge@git:20261020.d56de69Pins git:20261020.d56de69 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- swingerman/engineer
- Path
engineer/skills/post-merge/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261020.d56de69, committed Oct 20, 2026
- First version recorded
- Jun 4, 2026
- Size
- 5,836 bytes
- Repository stars
- 162
- License
- MIT
Use immediately after a PR is merged to clean up the local feature branch and resync main. Triggers — "/engineer.post-merge", "did we merge", "did we push", "PR merged", "post-merge cleanup", or right after a `gh pr merge` succeeds in the same session.
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
# post-merge
The branch-hygiene skill that runs **immediately** after a PR merges — not deferred to the next session. `next` and `session-summary` already catch a stale branch at session boundaries (v1.7.1); `post-merge` closes the gap in between, where users were still asking *"are we still on the feature branch?"* mid-session.
## When to use
- **Auto** — invoke right after observing a successful `gh pr merge`, `gh pr merge --auto`, or a "Merged" PR state in `gh pr view --json state`. The agent that ran the merge calls this skill before doing anything else.
- **Manual** — `/engineer.post-merge` or the trigger phrases above.
**Not for:** cleanup when the PR isn't merged yet (the work isn't done); session-end teardown (`session-summary` handles that); session-start survey (`next` already probes for stale branches as a backstop).
## Workflow
1. **Resolve + identify merged branch.** Resolve the methodology root via `${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py`. Get the current branch (`git branch --show-current`). If it's `main`/`master`/the repo's default branch, there's nothing to clean — stop and report.
…Read the whole file at its exact version.
How to install
mdr add swingerman/engineer/post-merge@sha256:30cec30bde989fd9The line at the top of this page pins the label git:20261020.d56de69, 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_hjitr6urrjayfenm)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jun 4, 2026 and Oct 20, 2026, about one every 46 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.d56de69 latest | 2026-10-20 | d56de69 | 5,836 B | A | view · diff |
| git:20260729.715119e | 2026-07-29 | 715119e | 5,431 B | A | view · diff |
| git:20260710.5dd248a | 2026-07-10 | 5dd248a | 4,978 B | A | view · diff |
| git:20260604.c294fe7 | 2026-06-04 | c294fe7 | 4,353 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 (5836 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
swingerman/engineer · 162 stars · license MIT · pushed 2026-10-27 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_hjitr6urrjayfenm GET https://markdownregistry.com/api/v1/resolve?ref=swingerman/engineer/post-merge GET https://markdownregistry.com/api/v1/blob/30cec30bde989fd913bca7d8881d56223cce97d33d95cb092f9a4fc6f9c29d21
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.
More from swingerman/engineer
Every file in swingerman/engineer