Borrowing it
Nothing to install: this file belongs to silver2dream/ai-workflow-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/silver2dream/ai-workflow-kit/main/.ai/skills/release-checklist/SKILL.mdgit clone --depth 1 https://github.com/silver2dream/ai-workflow-kitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/silver2dream/ai-workflow-kit/release-checklist)<a href="https://agentmods.dev/skills/silver2dream/ai-workflow-kit/release-checklist"><img src="https://agentmods.dev/badge/skills/silver2dream/ai-workflow-kit/release-checklist/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/silver2dream/ai-workflow-kit/release-checklist"><img src="https://agentmods.dev/badge/skills/silver2dream/ai-workflow-kit/release-checklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00545 |
| Opus 5.5 | $0.00000 | $0.00218 |
| Sonnet 5.5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
release-checklist scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Checklist Skill
Pre-release verification workflow that systematically validates all quality gates before a release merge to main.
Overview
This skill runs a comprehensive checklist of verifications to determine whether the current state of the codebase is ready for release. It produces a clear go/no-go decision with supporting evidence for each check.
When to Use
Use this skill when:
- Preparing to merge an integration branch into
main - Before creating a release tag
- User invokes
/release-checklist - User asks "are we ready to release?"
- Before creating a release PR (
feat/<branch>->main)
Workflow
Phase 1: Verify Release
Read phases/verify-release.md
Run the full pre-release verification:
- Verify all tests pass
- Check for uncommitted changes
- Verify changelog/version
- Check dependency vulnerabilities
- Validate CI status
- Verify branch state (up to date with main)
- Output go/no-go decision
Critical Rules
- ALL checks must pass for a GO decision -- no exceptions
- Do not auto-fix issues -- report them and let the user decide
- Be explicit about what failed -- include exact error output
- Check the correct branch -- verify you are on the integration branch, not main
- Never push or merge -- this skill is verification only
Integration with AWK Workflow
This skill is typically the last step before a release PR:
awkit kickoff → issues processed → PRs merged to integration branch
↓
/release-checklist → GO decision
↓
Create PR: integration branch → main (Release: true)
Per .ai/rules/_kit/git-workflow.md:
- Release PRs target
main - Only create release PRs when the ticket says
Release: true
Self-Check
On each phase entry, output:
[RELEASE-CHECKLIST] <timestamp> | <phase> | loaded: <filename>
Quick Reference
| Phase | Action | File |
|---|---|---|
| 1. Verify Release | Full pre-release verification | phases/verify-release.md |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 75 lines · 0 tokens per session scan A d506fc89a8ff
release-checklist is a skill published in the GitHub repository silver2dream/ai-workflow-kit (2 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 545 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
changelog-scan
Scan merged PRs and commits since a given reference, extract titles, labels, types, and signals. Produces structured input for release notes drafting.
draft-release-notes
Turn changelog-scan output into polished, categorized release notes draft. Propose only.
git-workflow
A Git workflow guide for organizing commits, branches, pull requests, releases, and automated version-control tasks. Git is the system developers use to track code changes and collaborate.
git-publish-release
A release assistant for GitHub, a service for hosting software projects. It compares project history and creates a GitHub Release with notes for a chosen version tag.
versioning-by-impact
Use when completing a task and deciding whether repository changes require a semantic version bump and changelog entry before commit/push.
tfx-ship
A release workflow for publishing triflux versions through GitHub Releases, the npm package registry, and the Claude Code marketplace. It also supports version changes, dry runs, skipped tests, and no-publish runs.