菜单
Inspect GitHub issues and pull requests before a NanoLang release, scope them to the release in progress, and close stale work only with an explicit, auditable annotation.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/jordanhubbard/nanolang --skill release-readiness命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Regenerate and refresh the NanoLang developer presentation and narrative from current language, compiler, NanoISA, NanoVM, and release evidence.
Diagnose NanoVM opcode, stack, value, and FFI failures with the optional NANO_VM_TRACE instrumentation.
Plan and execute repository product work through docs/ROADMAP.md. Use this before starting features, refactors, optimization programs, or other work with multiple deliverables. Add ordered checkboxes first, execute from top to bottom, and mark only verified work complete.
正在显示 SKILL.md
| name | release-readiness |
| description | Inspect GitHub issues and pull requests before a NanoLang release, scope them to the release in progress, and close stale work only with an explicit, auditable annotation. |
I do not release while work scoped to the release is still open. This check uses the GitHub CLI and requires an authenticated account with permission to read the repository and close issues or pull requests.
gh repo view --json nameWithOwner.RELEASE_VERSION to the version being prepared.release/v$RELEASE_VERSION
label, the v$RELEASE_VERSION milestone, or explicitly names the release
in its title or body.The release gate reports all open items, but only release-scoped items block the release. Unscoped work remains visible and must not be closed merely to make the gate green.
For each release-scoped open item:
Before closing a stale issue or pull request, add a comment using this form:
Stale for release vX.Y.Z: closing because <specific reason>.
Evidence: <commit, replacement issue/PR, decision, or reproduction result>.
Reopen or reference <link> if this is still relevant.
Apply the stale label when the repository has one. Do not close a pull
request solely because it is old: record why the proposed change is no longer
wanted or has been superseded.
Run:
gh issue list --state open --limit 1000 --json number,title,body,url,labels,milestone
gh pr list --state open --limit 1000 --json number,title,body,url,labels,milestone
The gate passes only when no release-scoped issue or pull request remains open. Save the query output and the triage comments in the release evidence; the absence of an item from a list is not evidence that it was reviewed.
This skill requires an LLM coding CLI. Human-only release handling is not a supported path because the review requires repository context, roadmap linking, and precise stale annotations.