gh-issue-drafter skillA
gh-issue-drafter is agent-read markdown (skill) from ymd38/dev-skills: 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. This is the human-authored counterpart to report-to-issues (which registers machine-generated findings). Use when the user wants to file a new Issue from a r.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns 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 already well-formed. …
Read the whole file at its exact version.
How to install
mdr add ymd38/dev-skills/gh-issue-drafter@git:20260919.20d77cbmdr add ymd38/dev-skills/gh-issue-drafter@sha256:a9cbea6bcf2537acPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_d4wvo3762kbluvks)
1 badge views in 30 days
Versions
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 (7662 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 · 4 stars · license MIT · pushed 2026-09-19 · 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/a9cbea6bcf2537ac7e3b586efb1285878d7c99a81ec4d4eafb957a9a25df30da
Your agent 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.
More from ymd38/dev-skills
Every file in ymd38/dev-skills