gh-issue-resolver SKILL.md skillA
gh-issue-resolver 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-resolver@git:20261007.6126503Pins git:20261007.6126503 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-resolver/SKILL.md- Versions recorded
- 9
- Latest version
- git:20261007.6126503, committed Oct 7, 2026
- First version recorded
- Apr 25, 2026
- Size
- 14,162 bytes
- Repository stars
- 7
- License
- MIT
Implement and verify a fix for a GitHub Issue whose response plan has already been posted as a comment by gh-issue-planner. Creates a feature branch, applies the agreed plan, runs tests, and opens a Pull Request. Use when the user asks to implement/fix/resolve a planned GitHub Issue. Triggers include requests such as Issueを実装して / Issueを修正して / Issueを対応して, implement issue #N, fix issue #N, resolve issue #N, work on issue #N. Prerequisite: an agreed plan comment must exist on the issue…
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 Resolver ## Overview Implement and verify a fix for a GitHub Issue, starting from the agreed response plan that `gh-issue-planner` has already posted as a comment on the issue. This skill creates a feature branch, uses a git worktree as a temporary implementation sandbox, runs tests, opens a Pull Request, and verifies the fix against the original issue. ## Prerequisites - The target issue must have an **agreed plan comment** previously posted by `gh-issue-planner`, identified by the HTML marker `<!-- gh-issue-planner:agreed-plan -->` near the end of the comment body. - If no such comment exists, **stop and direct the user to run `gh-issue-planner` first**. Do not improvise an unagreed plan in this skill. ## Workflow ### Step 1: Fetch the Issue and Agreed Plan Run the following command (replace `<id>` with the issue number): ```bash gh issue view <id> --json number,title,body,labels,state,url,comments ``` From the `comments` array: 1. Locate the most recent comment whose body contains the marker `<!-- gh-issue-planner:agreed-plan -->`. 2. Treat that comment as the **agreed plan** and extract the 対応方針 (Approach) / どこまで作るか / …
Read the whole file at its exact version.
How to install
mdr add ymd38/dev-skills/gh-issue-resolver@sha256:7d03e79b47a468f9The line at the top of this page pins the label git:20261007.6126503, 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_wr277it2ju47damp)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 9 versions of this file, between Apr 25, 2026 and Oct 7, 2026, about one every 21 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.6126503 latest | 2026-10-07 | 6126503 | 14,162 B | A | view · diff |
| git:20261007.0fbabf8 | 2026-10-07 | 0fbabf8 | 13,958 B | A | view · diff |
| git:20261007.f8d1c6f | 2026-10-07 | f8d1c6f | 13,810 B | A | view · diff |
| git:20261007.8df5aa6 | 2026-10-07 | 8df5aa6 | 13,763 B | A | view · diff |
| git:20261007.a7bac54 | 2026-10-07 | a7bac54 | 13,724 B | A | view · diff |
| git:20260919.20d77cb | 2026-09-19 | 20d77cb | 12,968 B | A | view · diff |
| git:20260803.f79a6ae | 2026-08-03 | f79a6ae | 12,189 B | A | view · diff |
| git:20260430.55e2fc3 | 2026-04-30 | 55e2fc3 | 6,188 B | A | view · diff |
| git:20260425.c2605cb | 2026-04-25 | c2605cb | 4,293 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 (14162 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_wr277it2ju47damp GET https://markdownregistry.com/api/v1/resolve?ref=ymd38/dev-skills/gh-issue-resolver GET https://markdownregistry.com/api/v1/blob/7d03e79b47a468f95b9348c8dc6c28a89bc4261ef9b57a317d35576e3d523d1e
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