开发与测试
github-issue-format
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.
richkuo · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add richkuo/rk-skills --skill github-issue-format技能说明
name: github-issue-format description: Required format for creating or editing any GitHub issue — [C] title convention, complexity rationale line, complete-body rule, mandatory Plain simple English section, attribution footer. Load BEFORE creating or editing a GitHub issue.
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-issuestep 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:
**Complexity: 95/100** — Capability 3 (Risk 4, Uncertainty 2 — money/data-integrity on order-fill path); Volume 20 (Scope 4, Coupling 3, Verification 3) — Opus 5, xhigh · fableplan: yes. The line always carries all five axis grades; thevalidate-issuescoring reference owns the axes and their anchors. - fableplan signal:
· fableplan: yeswhen the score is ≥ 71 (a Fable 5.1 plan is posted before the build; the builder is Opus 5 at xhigh);· fableplan: nobelow 71. Always write it: absence is ambiguous. Fable 5.1 defaults tohigh;xhighon Fable is legal only when the user asks for it or stamps it (the LLM Attribution Footer section of CLAUDE.md owns this rule). ## Plain simple Englishis mandatory on every issue: one short paragraph under 55 words in ASD-STE100, per the CLAUDE.md/AGENTS.md Response Style definition. State what is wrong or missing and why it matters, for a reader who knows the product but not the code. Never restate the approach, list file paths or symbols, or give a time or effort estimate there. An edit that rewrites body prose adds the section when it is missing; an edit that changes only machine metadata (the Execution block, or the[C<score>]title prefix) leaves every prose section unchanged and does not add it.- LLM Attribution Footer ends the body:
Createdfor a new issue,Validatedwhen a validation pass produced the edit (validate-issueand its wrappers),Updatedfor any other edit. Stack the new line under the existing ones; never replace them, and never append an exact duplicate of a line already there. - Project precedence: a repo CLAUDE.md issue or footer format overrides this default.