ship-issue SKILL.md skillA
ship-issue from jerseycheese/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jerseycheese/agent-skills/ship-issue@git:20261016.04e815bPins 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/ship-issue/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261016.04e815b, committed Oct 16, 2026
- First version recorded
- Jun 28, 2026
- Size
- 3,257 bytes
- Repository stars
- 3
- License
- MIT
Drives one GitHub issue from cold start to merged PR: sync, analyze, minimal fix with a test, PR, CI green, merge, post-merge cleanup, wrap-up. Trigger on: "ship issue #X", "ship #123", "take #N to merge", "do issue #X end to end".
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
# Ship Issue Drive a single issue from a cold start to a merged PR and a clean handoff. This is a conductor: each step leans on an existing skill or native control rather than re-implementing it. Apply a minimal, root-cause fix — don't patch a symptom or pad the change past the issue's scope. Take the issue number from the user (e.g. "ship issue #326"). If they named an issue instead of numbering it, find it: ```bash gh issue list --search "[keywords]" --json number,title | head -5 ``` ## The loop 1. **Pre-flight — sync and locate.** Run `git fetch && git status`. Get onto the right base branch (`develop` if it exists, else `main`) and up to date. If you're working in a worktree, confirm it's the right one and that its dev server points at it. Never build or test against a stale checkout — that's where most rework comes from. 2. **Analyze.** Run the `analyze-issue` skill: fetch the issue, discover existing patterns in the codebase, set scope boundaries, and produce an implementation plan with MVP-level tests. Diagnose the root cause before writing any code. …
Read the whole file at its exact version.
How to install
mdr add jerseycheese/agent-skills/ship-issue@sha256:3ddd85689dcc3633The 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.
[](https://markdownregistry.com/a/art_2sbvtkvvfyukpodv)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jun 28, 2026 and Oct 16, 2026, about one every 55 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.04e815b latest | 2026-10-16 | 04e815b | 3,257 B | A | view · diff |
| git:20260729.5e4ea92 | 2026-07-29 | 5e4ea92 | 3,511 B | A | view · diff |
| git:20260628.9366aee | 2026-06-28 | 9366aee | 3,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 (3257 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
jerseycheese/agent-skills · 3 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2sbvtkvvfyukpodv GET https://markdownregistry.com/api/v1/resolve?ref=jerseycheese/agent-skills/ship-issue GET https://markdownregistry.com/api/v1/blob/3ddd85689dcc363342cdf488bfe9b67f9171c4912fc1606ecdc47434e9efc848
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.