validate-issue-loop SKILL.md skillA
validate-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/validate-issue-loop@git:20261006.61bf5e6Pins git:20261006.61bf5e6 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/validate-issue-loop/SKILL.md- Versions recorded
- 13
- Latest version
- git:20261006.61bf5e6, committed Oct 6, 2026
- First version recorded
- Aug 14, 2026
- Size
- 4,463 bytes
- Repository stars
- 50
- License
- MIT
Use when the user asks to validate a GitHub issue and then autonomously drive it to a reviewed PR in one shot — "validate and work on this issue", "validate-issue-loop", "fully automate issue #N". Runs validate-issue, auto-applies its update-issue edits when the verdict calls for it, then hands off to work-on-issue-loop with no plan stage — stopping instead when validation flags the issue as too large, architecturally infeasible, or already addressed by an existing PR, or recommended for…
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
# validate-issue-loop Chain validate-issue → (conditional) update issue → work-on-issue-loop into one autonomous run. Where validate-issue's `→` next-step line would wait for the user's reply, read the verdict yourself and decide the next step. **Do not skip validation.** Every step of validate-issue still runs; only the "wait for the user's reply" step is replaced by the decision rules below. ## Input Same as fable-validate-loop, including the optional `targetBranch`. ## Steps Follow **fable-validate-loop steps 1 through 3**, which own the verdict block, the `owner/repo#N` record, the stop table, and the edit step with its landing check, with these changes: **Step 1 (validation):** invoke the plain `validate-issue` skill (Skill tool, `skill: validate-issue`) in place of `fable-validate`. Let it run its full process, steps 0 through 8, and parse the verdict block that fable-validate-loop step 1 quotes. Its final `→` next-step line is written for interactive use, so treat the verdict as structured output and decide from the step 2 table. Record the resolved issue as `owner/repo#N` per fable-validate-loop step 1. …
Read the whole file at its exact version.
How to install
mdr add richkuo/rk-skills/validate-issue-loop@sha256:7f7a1b7175822e0fThe line at the top of this page pins the label git:20261006.61bf5e6, 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_snoz6evlczdvnavn)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 13 versions of this file, between Aug 14, 2026 and Oct 6, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.61bf5e6 latest | 2026-10-06 | 61bf5e6 | 4,463 B | A | view · diff |
| git:20261006.4c6da76 | 2026-10-06 | 4c6da76 | 4,411 B | A | view · diff |
| git:20261005.e9b5f92 | 2026-10-05 | e9b5f92 | 4,894 B | A | view · diff |
| git:20261002.6c4566e | 2026-10-02 | 6c4566e | 4,865 B | A | view · diff |
| git:20261002.51ca084 | 2026-10-02 | 51ca084 | 4,887 B | A | view · diff |
| git:20260929.665e60a | 2026-09-29 | 665e60a | 4,904 B | A | view · diff |
| git:20260928.2014375 | 2026-09-28 | 2014375 | 4,899 B | A | view · diff |
| git:20260927.55c2280 | 2026-09-27 | 55c2280 | 5,684 B | A | view · diff |
| git:20260923.66d4f63 | 2026-09-23 | 66d4f63 | 5,626 B | A | view · diff |
| git:20260903.6fdbab1 | 2026-09-03 | 6fdbab1 | 5,459 B | A | view · diff |
| git:20260903.9f8defc | 2026-09-03 | 9f8defc | 5,385 B | A | view · diff |
| git:20260822.c2c4dd0 | 2026-08-22 | c2c4dd0 | 5,075 B | A | view · diff |
| git:20260814.7b57ecd | 2026-08-14 | 7b57ecd | 5,093 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 (4463 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_snoz6evlczdvnavn GET https://markdownregistry.com/api/v1/resolve?ref=richkuo/rk-skills/validate-issue-loop GET https://markdownregistry.com/api/v1/blob/7f7a1b7175822e0f4184b36c33a2897537ff2c2d7cddf305b1d29678c53f382f
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.