merge-ready SKILL.md skillA
merge-ready from urmzd/dotfiles is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add urmzd/dotfiles/merge-ready@git:20260710.4354132Pins git:20260710.4354132 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- urmzd/dotfiles
- Path
dot_agents/skills/merge-ready/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260710.4354132, committed Jul 10, 2026
- Size
- 9,742 bytes
- Repository stars
- 5
- License
- Apache-2.0
Drive an existing pull request to a mergeable state: get CI green, resolve merge conflicts with the base branch, address and resolve review comments, trigger required bot reviews/approvals (e.g. commenting '@claude review'), link associated issues, and clean up the PR title and description. Ends with a readiness report listing any remaining human-only blockers (required reviewer approvals, CODEOWNERS). Uses the CLI matching the repo's forge: gh for GitHub, glab for GitLab merge requests, tea…
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
# Merge Ready Take an open PR from wherever it is to "ready to merge", and report exactly what still needs a human when automation can't finish the job. ## Steps 1. **Detect the forge and pick the CLI**: Read the remote (`git remote get-url origin`) and choose the matching CLI, verifying it is installed and authenticated before proceeding: | Host in remote URL | CLI | PR concept | Auth check | |---|---|---|---| | github.com / GHE | `gh` | pull request | `gh auth status` | | gitlab.com / self-hosted GitLab | `glab` | merge request (MR) | `glab auth status` | | Gitea / Forgejo / Codeberg | `tea` | pull request | `tea login list` | The steps below are written with `gh`; on another forge, translate each operation to the equivalent verb (`gh pr view` -> `glab mr view --output json` / `tea pr <n>`, `gh pr comment` -> `glab mr note`, `gh run view` -> `glab ci view`, `gh pr update-branch` -> `glab mr rebase`, review threads -> `glab api projects/:id/merge_requests/:iid/discussions`). Confirm exact flags with `--help` rather than guessing. If the forge has no CLI (e.g. Bitbucket), fall back to `git` plus the forge's REST API via …
Read the whole file at its exact version.
How to install
mdr add urmzd/dotfiles/merge-ready@sha256:12d86cf6c68888f3The line at the top of this page pins the label git:20260710.4354132, 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_wha2xmahlum7e3wd)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 10, 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 (9742 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
urmzd/dotfiles · 5 stars · license Apache-2.0 · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wha2xmahlum7e3wd GET https://markdownregistry.com/api/v1/resolve?ref=urmzd/dotfiles/merge-ready GET https://markdownregistry.com/api/v1/blob/12d86cf6c68888f3b62419c962079b6c18b1c1995f10e76095b68d96d458afb4
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.