new-issue-loop SKILL.md skillA
new-issue-loop from richkuo/rk-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add richkuo/rk-skills/new-issue-loop@git:20261006.4c6da76Pins git:20261006.4c6da76 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- richkuo/rk-skills
- Path
skills/new-issue-loop/SKILL.md- Versions recorded
- 9
- Latest version
- git:20261006.4c6da76, committed Oct 6, 2026
- First version recorded
- Jul 4, 2026
- Size
- 3,926 bytes
- Repository stars
- 50
- License
- MIT
Use when the user asks to file a GitHub issue and then autonomously drive it all the way to a reviewed PR in one shot — "new-issue-loop", "create the issue and run it to completion", "file this and fully automate it". Runs new-issue to create a fully-specified issue, then hands the new issue's `owner/repo#N` reference to validate-issue-loop (validate → update → work-on-issue-loop) — stopping instead when new-issue finds a duplicate or the discussion hasn't converged on one 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
# new-issue-loop Chain new-issue → validate-issue-loop into one autonomous run with no human between steps: the loop feeds the issue it just filed into the validate-and-implement pipeline. **Do not skip filing a complete issue.** Every step of new-issue still runs (grounding, approach design, complexity score); only the "offer next steps and wait" step is replaced by the handoff. ## Input Same as new-issue: an optional description of what the issue should cover; with no input, derive it from the current conversation. Optionally `owner/repo` when the issue belongs elsewhere. ## Steps ### 1. Run new-issue Invoke the `new-issue` skill (Skill tool, `skill: new-issue`) with the user's description (or conversation-derived scope). Let it run its full process. Capture the created issue from its report as the full reference `owner/repo#N`: the repository new-issue filed to (its `-R owner/repo`, else the current checkout per `gh repo view --json nameWithOwner -q .nameWithOwner`) and the new number. ### 2. Stop gate — cases the loop can't safely continue | Condition | Action | |---|---| …
Read the whole file at its exact version.
How to install
mdr add richkuo/rk-skills/new-issue-loop@sha256:84b9362da8fa3cc6The line at the top of this page pins the label git:20261006.4c6da76, 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_fu77lkccmbh3jjvi)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 9 versions of this file, between Jul 4, 2026 and Oct 6, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.4c6da76 latest | 2026-10-06 | 4c6da76 | 3,926 B | A | view · diff |
| git:20261005.e9b5f92 | 2026-10-05 | e9b5f92 | 4,733 B | A | view · diff |
| git:20261002.6c4566e | 2026-10-02 | 6c4566e | 4,738 B | A | view · diff |
| git:20261002.51ca084 | 2026-10-02 | 51ca084 | 4,760 B | A | view · diff |
| git:20260928.2014375 | 2026-09-28 | 2014375 | 4,722 B | A | view · diff |
| git:20260927.55c2280 | 2026-09-27 | 55c2280 | 4,396 B | A | view · diff |
| git:20260808.babc894 | 2026-08-08 | babc894 | 4,402 B | A | view · diff |
| git:20260807.c1f1b83 | 2026-08-07 | c1f1b83 | 4,412 B | A | view · diff |
| git:20260704.c7939e4 | 2026-07-04 | c7939e4 | 4,376 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 (3926 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
richkuo/rk-skills · 50 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fu77lkccmbh3jjvi GET https://markdownregistry.com/api/v1/resolve?ref=richkuo/rk-skills/new-issue-loop GET https://markdownregistry.com/api/v1/blob/84b9362da8fa3cc62be0c7739193a81e95e4fba8bce5d4105035cbf5ba235b31
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.