github-issue-format skillA
github-issue-format is agent-read markdown (skill) from richkuo/rk-skills: Required format for creating or editing any GitHub issue — [C<score>] title convention, complexity rationale line, complete-body rule, mandatory Plain simple English section, attribution footer. Load BEFORE creating or editing a GitHub issue..
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 format ## Title - `[C<score>] <title>`: a plain-simple-English sentence in ASD-STE100, precise about component and behavior, e.g. `[C95] Orders can be filled twice when two fills arrive at the same moment`. - The **complexity score (0–100)** is a model and effort routing signal. `validate-issue` step 6 owns the formula, axes, and routing table; never restate or approximate them here. ## Body - **Never create a placeholder, stub, or empty-bodied issue.** Every issue gets a complete body at creation, even in a batch. If a follow-up is not ready to spec, track it in the parent issue or notes until it is. - **Section order:** complexity rationale line, `## Problem`, `## Goal`, `## Approach`, `## Acceptance criteria`, `## Plain simple English`, then any Execution block, then the attribution footer. An Execution block is machine metadata and keeps its place between the last prose section and the footer. - **Complexity rationale line** (first line of the body): matches the title prefix and ends with an explicit fableplan signal: …
Read the whole file at its exact version.
How to install
mdr add richkuo/rk-skills/github-issue-format@git:20260923.d8bb824mdr add richkuo/rk-skills/github-issue-format@sha256:00a92927089ca05cPin 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_p3cnz6o7xq4d4ohz)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260923.d8bb824 latest | 2026-09-23 | d8bb824 | 3,054 B | A | view · diff |
| git:20260905.cd7c29b | 2026-09-05 | cd7c29b | 3,050 B | A | view · diff |
| git:20260903.6fdbab1 | 2026-09-03 | 6fdbab1 | 3,018 B | A | view · diff |
| git:20260901.c877bb0 | 2026-09-01 | c877bb0 | 2,868 B | A | view · diff |
| git:20260901.6c08e4b | 2026-09-01 | 6c08e4b | 3,332 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 (3054 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 · 49 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p3cnz6o7xq4d4ohz GET https://markdownregistry.com/api/v1/resolve?ref=richkuo/rk-skills/github-issue-format GET https://markdownregistry.com/api/v1/blob/00a92927089ca05c5e9bc3652756ba751f241c5fa58737468029754e924ed1cd
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.