Home / jerseycheese / agent-skills · GitHub

post-merge SKILL.md skillA

post-merge from jerseycheese/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add jerseycheese/agent-skills/post-merge@git:20261016.04e815b

Pins git:20261016.04e815b in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: jerseycheese/agent-skills
Path: skills/post-merge/SKILL.md
Versions recorded: 2
Latest version: git:20261016.04e815b, committed Oct 16, 2026
First version recorded: Jun 28, 2026
Size: 7,477 bytes
Repository stars: 3
License: MIT

Runs after a PR merges: syncs the base branch, deletes the merged branch and worktree, closes out linked issues without asking (even on a develop base), then recommends the next issue. Trigger on: "merged PR #42", "PR is merged", "just merged the auth fix", "I merged #123".

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 Workflow

Three phases: sync and clean the working tree, tidy up the issues the PR addressed, then recommend what to do next.

## Phase 0: Sync and Clean the Working Tree

Do this first. Most post-merge rework comes from the next task starting against a stale base branch or a leftover feature branch/worktree — clean it up now while you have the context.

### 1. Find the base and head branches

Don't assume `main`. Read what the PR actually merged into:

```bash
gh pr view [NUMBER] --json number,title,baseRefName,headRefName,mergedAt
```

`baseRefName` is the branch to sync (often `develop` or `main`); `headRefName` is the merged feature branch to delete.

### 2. Sync the base branch

```bash
git fetch --prune
git checkout [BASE_BRANCH]
git pull --ff-only
```

If your current checkout is a worktree pinned to the merged feature branch, you can't switch it to the base — leave it and handle the worktree in step 3.

### 3. Delete the merged branch and its worktree

```bash
git worktree list                    # find any worktree holding the feature branch
git worktree remove [WORKTREE_PATH]  # only if it lives in a worktree
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add jerseycheese/agent-skills/post-merge@sha256:95d902173d6384a7

The line at the top of this page pins the label git:20261016.04e815b, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_elqxgw42bsjxtd4b.svg)](https://markdownregistry.com/a/art_elqxgw42bsjxtd4b)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, between Jun 28, 2026 and Oct 16, 2026, about one every 110 days.

version	committed	commit	size	audit
git:20261016.04e815b latest	2026-10-16	04e815b	7,477 B	A	view · diff
git:20260628.9366aee	2026-06-28	9366aee	7,919 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (7477 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

GitHub

jerseycheese/agent-skills · 3 stars · license MIT · pushed 2026-10-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_elqxgw42bsjxtd4b
GET https://markdownregistry.com/api/v1/resolve?ref=jerseycheese/agent-skills/post-merge
GET https://markdownregistry.com/api/v1/blob/95d902173d6384a71e53714934e1e954035fa353b2849eb63254ba6da912390e

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 jerseycheese/agent-skills

abstraction-finder SKILL.md skill

jerseycheese/agent-skills · skills/abstraction-finder/SKILL.md · Finds recurring patterns worth extracting into shared code and proposes the smallest form for each (helper, util, base…