release-readiness-checklist
Inspect a small npm CLI release candidate and produce a row-by-row release-readiness checklist report with evidence, pass rules, severity, N/A policy, and a final gate. Use when the task is to review a release candidate without publishing it.
git clone --depth 1 https://github.com/LearnPrompt/LearnPrompt /tmp/release-readiness-checklist && cp -r /tmp/release-readiness-checklist/research/articles/checklist-skill-design/showcase/release-readiness-checklist/fixture/.agents/skills/release-readiness-checklist ~/.claude/skills/release-readiness-checklistSKILL.md
# Release readiness checklist
## When to use
Use this skill when the user asks for a release-readiness check, release candidate inspection, pre-publish checklist, or dry-run go/no-go decision for a small npm CLI package.
## Workflow
1. Read `references/checklist-contract.md`.
2. Run:
```bash
node .agents/skills/release-readiness-checklist/scripts/collect-evidence.mjs \
--expected-version 1.4.0 \
--output-json reports/release-readiness.json \
--output-md reports/release-readiness.md
```
3. Keep the generated report even if the exit code is non-zero. The point is to preserve evidence, not to stop at the first failing row.
4. Run `npm test`.
5. Return only the JSON object requested by the caller schema.
## Boundaries
- Never run `npm publish`.
- Never edit `package.json`, `CHANGELOG.md`, or `release/install-command.txt`.
- Do not replace checklist rows with “looks fine” prose.
- If the host blocks the skill or model execution, report that block plainly instead of fabricating a pass.Create or rewrite exactly one LearnPrompt Starlight MDX tutorial to the repository's golden-sample standard, with bottom-of-page auditable sources instead of SourceCard, a research pack, evidence ledger, reproducible showcase, independent review, quality score, and successful site build. Use for one LearnPrompt article, tutorial, chapter, or MDX page; in batch goals, invoke once per topic in an isolated task.
Read a read-only release feed over HTTP, enforce an auditable request contract, and write redacted JSON and Markdown reports. Use when the task is to inspect releases from a REST endpoint without mutating upstream state.
Save a shared web link as a clean Obsidian note. Use when the user gives a URL and asks to save, clip, or archive it into their Obsidian vault as a markdown note with title, source, and summary.
Migrate three legacy Markdown docs into Starlight-compatible migration candidates inside an isolated temp repo. Use when you need stage receipts, crash recovery, resume validation, or deterministic candidate packaging without touching real user docs.
从一个 issue 和一段 diff 生成结构化发布摘要，固化“读 issue → 读 diff → 归类改动 → 评估风险 → 写验证步骤”的重复工作流。
Distill a candidate skill from observable repair receipts, then prove it on holdout fixtures. Use when you have repeated accepted patches, corrections, and validator results, but do not have permission to use private transcripts or hidden chain-of-thought.
Repair synthetic MDX frontmatter when title, description, or sidebar.order drift from the frontmatter contract. Use for files that follow the same observable patterns proven in the receipts; do not use on private transcripts, secret-bearing material, or arbitrary YAML.
Prepare a dry-run rename plan for a batch of receipt PDFs. Use when the user wants repository-style receipt filenames normalized under the local naming policy without renaming files yet.