deliver-issue SKILL.md skillA
deliver-issue from phmatray/ai-migration-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add phmatray/ai-migration-kit/deliver-issue@git:20261010.9485205Pins git:20261010.9485205 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- phmatray/ai-migration-kit
- Path
skills/deliver-issue/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261010.9485205, committed Oct 10, 2026
- First version recorded
- Sep 2, 2026
- Size
- 19,134 bytes
- Repository stars
- 4
- License
- MIT
Take ONE idea or ONE planned issue all the way to a merged PR, hands-off — file or seed it with create-issue, build it with implement-issue, land it with merge-pr, each phase in a FRESH sub-agent context. Use when the user wants the whole chain run for a single item: "deliver issue 47 end to end", "take this idea to a merged PR", "run the full lifecycle on #12", « livre l'issue 47 de bout en bout », « de l'idée à la PR mergée ». `--stop-at ready` stops before the merge. Does NOT apply to many…
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
# Deliver an issue — one item, idea to merged PR, hands-off ## What this does The lifecycle is three skills the user types one after another — `create-issue` ends with `/implement-issue #N`, `implement-issue` ends with `/merge-pr #PR`, `merge-pr` lands it — and [`../_shared/recap.md`](../_shared/recap.md)'s hand-off table exists because those prompts are what the user acts on next. `auto-dev` walks that chain for N issues at once through two fresh-context worker commands. This skill is the **single-item form**: one idea or one planned issue, taken to a merged PR, with the same two command files doing the work and this skill doing only the deciding. It is an **orchestrator, never an implementer**. It runs nothing of the three phases in its own context: each phase is a fresh sub-agent dispatched through the Agent tool (ADR 0007), its final message is read as a report, and the decision between phases is made here. The reason is measured, not stylistic — `commands/auto-dev-worker.md` § *Why two phases* records the merge phase at ~247K tokens of context per turn when run inside the implement context, and ~82% cheaper in a fresh one. …
Read the whole file at its exact version.
How to install
mdr add phmatray/ai-migration-kit/deliver-issue@sha256:b68591e8ea3197a0The line at the top of this page pins the label git:20261010.9485205, 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_wtyqj6wnxjt6635h)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 2, 2026 and Oct 10, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261010.9485205 latest | 2026-10-10 | 9485205 | 19,134 B | A | view · diff |
| git:20260914.a9bc0b6 | 2026-09-14 | a9bc0b6 | 19,142 B | A | view · diff |
| git:20260913.9388358 | 2026-09-13 | 9388358 | 19,152 B | A | view · diff |
| git:20260905.fff03f3 | 2026-09-05 | fff03f3 | 19,116 B | A | view · diff |
| git:20260902.218e53a | 2026-09-02 | 218e53a | 19,035 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 (19134 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
phmatray/ai-migration-kit · 4 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wtyqj6wnxjt6635h GET https://markdownregistry.com/api/v1/resolve?ref=phmatray/ai-migration-kit/deliver-issue GET https://markdownregistry.com/api/v1/blob/b68591e8ea3197a0f646f4804f0153b2833e5d357c8277ec39999af32ba256d3
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 phmatray/ai-migration-kit
Every file in phmatray/ai-migration-kit