gh-issue-drafter SKILL.md skillA
gh-issue-drafter from ymd38/dev-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ymd38/dev-skills/gh-issue-drafter@git:20261007.c71d404Pins git:20261007.c71d404 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ymd38/dev-skills
- Path
skills/gh-issue-drafter/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261007.c71d404, committed Oct 7, 2026
- First version recorded
- Sep 19, 2026
- Size
- 11,823 bytes
- Repository stars
- 7
- License
- MIT
Turn a rough, hand-written intent into a well-scoped GitHub Issue before planning starts. Takes a loose 'what I want' from the user, proposes the missing structure (Done definition, Out of scope, Design constraints), gets the user's approval, and creates the Issue via the gh CLI with a scoped-issue marker so gh-issue-planner can pick it up. When the intent is too large for one Issue, it proposes splitting it into independent Issues or an Epic with sub-issues. This is the human-authored…
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
# GitHub Issue Drafter ## Overview The quality of everything downstream — the plan, the reviews, the implementation, the CI verification — is capped by the quality of the Issue that starts it. A rough, one-line Issue forces every later step to guess at the author's intent. This skill takes the user's rough intent (the *What*) and, without slowing them down, proposes the three things a hand-written Issue almost always omits: a machine-checkable **Done definition**, an explicit **Out of scope**, and optional **Design constraints**. The user approves or edits the proposal, then the skill creates a structured GitHub Issue tagged with a marker that `gh-issue-planner` recognizes. **Scope boundary:** this skill only drafts and files the Issue. It does not investigate code, propose a response plan, or implement anything. Hand off to `gh-issue-planner` once the Issue exists. ## When NOT to expand If the user's input already contains a clear Done definition and scope (e.g. they pasted a fully-formed Issue, or a `report-to-issues` output), do not re-interrogate them — just confirm and file. The goal is to fill gaps, not to add ceremony to Issues that are …
Read the whole file at its exact version.
How to install
mdr add ymd38/dev-skills/gh-issue-drafter@sha256:64e762864a700ec0The line at the top of this page pins the label git:20261007.c71d404, 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_d4wvo3762kbluvks)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 19, 2026 and Oct 7, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.c71d404 latest | 2026-10-07 | c71d404 | 11,823 B | A | view · diff |
| git:20261007.f8d1c6f | 2026-10-07 | f8d1c6f | 8,437 B | A | view · diff |
| git:20261007.a7bac54 | 2026-10-07 | a7bac54 | 8,386 B | A | view · diff |
| git:20260919.20d77cb | 2026-09-19 | 20d77cb | 7,662 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 (11823 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
ymd38/dev-skills · 7 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_d4wvo3762kbluvks GET https://markdownregistry.com/api/v1/resolve?ref=ymd38/dev-skills/gh-issue-drafter GET https://markdownregistry.com/api/v1/blob/64e762864a700ec08618c2b47b6238723ba33c0d7923bf493498bb928b2760db
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 ymd38/dev-skills
Every file in ymd38/dev-skills