check-merged SKILL.md skillA
check-merged from eltmon/overdeck is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add eltmon/overdeck/check-merged@git:20260522.817c2c7Pins git:20260522.817c2c7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- eltmon/overdeck
- Path
sync-sources/skills/check-merged/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260522.817c2c7, committed May 22, 2026
- Size
- 4,087 bytes
- Repository stars
- 35
- License
- MIT
Verify whether an issue's feature branch has been merged into main. Checks git history, branch existence, and commit presence. Returns MERGED, NOT_MERGED, or BRANCH_NOT_FOUND with evidence. Designed for cheap models (Haiku) to run quickly.
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
# Check Merged
Verify whether a feature branch for an issue has been merged into the main branch.
## Purpose
After an issue reaches "Done" on the kanban board, we need to confirm the code was actually merged — not just that the tracker status was updated. This skill checks git evidence to give a definitive answer.
## When to Use
- **Close-out ceremony**: Before archiving workspace artifacts
- **Done column audit**: Batch-verify all Done items are genuinely merged
- **Stale branch cleanup**: Identify branches that were abandoned vs merged
- **As a subagent**: Spawn from a parent agent to verify multiple issues in parallel
## Input
The skill expects an issue ID (e.g., `PAN-123`, `MIN-456`) and a project path.
## Execution
### Step 1: Resolve Branch Name
```bash
# Standard naming convention
BRANCH="feature/${ISSUE_ID_LOWER}"
# Also check alternate patterns
# edwardbecker/${issue-slug} (Linear default)
# feature/${issue-id}-description
```
### Step 2: Check If Branch Exists
```bash
# Check local branches
git -C "$PROJECT_PATH" branch --list "$BRANCH" 2>/dev/null
# Check remote branches
git -C "$PROJECT_PATH" ls-remote --heads origin "$BRANCH" 2>/dev/null
…Read the whole file at its exact version.
How to install
mdr add eltmon/overdeck/check-merged@sha256:fa66002d211f0e33The line at the top of this page pins the label git:20260522.817c2c7, 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_pza2atijlxjwuzej)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 22, 2026.
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 (4087 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
eltmon/overdeck · 35 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pza2atijlxjwuzej GET https://markdownregistry.com/api/v1/resolve?ref=eltmon/overdeck/check-merged GET https://markdownregistry.com/api/v1/blob/fa66002d211f0e33885f66d029bc543946ddf90112c0069d1020ff39967e7d1a
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.