# Release Ready

> Perform a final readiness audit of a repository, package, tool, model, dataset, or public artifact before release. Use when the user asks whether work is ready to publish, open-source, tag, package, or hand off. Do not use for ordinary feature completion or to publish anything without explicit authorization.

- Skill: `denizaslan36/release-ready` (Agent Skill)
- Install (CLI): `npx skillmds@latest add denizaslan36/release-ready`
- Raw SKILL.md: https://api.skillmd.com/api/skills/denizaslan36/release-ready/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: denizaslan36 (https://skillmd.com/u/denizaslan36)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/denizaslan36/release-ready

---


# Release Ready

Find release blockers that correctness checks alone miss.

## Readiness Audit

1. Establish the release target, intended audience, supported environment, and claims being made. Infer only what the artifact itself makes clear.
2. Inspect the applicable surfaces:
   - functional correctness and fresh verification evidence;
   - public interface, configuration, and compatibility;
   - documentation accuracy and runnable examples;
   - package metadata, versions, entry points, and generated artifacts;
   - secrets, private data, unsafe defaults, and dependency risk;
   - license, attribution, and provenance of bundled material;
   - reproducibility of benchmark, performance, and quality claims;
   - repository hygiene, including accidental local or internal files.
3. Trace the shortest newcomer path from acquisition to useful result. Record blockers in the artifact; do not write a user testing guide unless asked.
4. Rank each finding:
   - **blocker** — release could fail, mislead, leak, or violate a requirement;
   - **important** — release works but creates material support or trust risk;
   - **nice-to-have** — improvement that does not justify delaying release.
5. Re-check changed surfaces after authorized fixes. Do not silently broaden into unrelated cleanup.
6. Give one verdict: **ready**, **ready with known limitations**, or **not ready**. List only evidence and unresolved items that justify the verdict.

## Release Boundaries

- Do not push, publish, tag, upload, message third parties, or change external state without explicit authorization.
- Never treat a clean diff, passing unit tests, or polished documentation as sufficient on its own.
- Do not require checks irrelevant to the artifact's actual distribution model.
- If legal or policy certainty is required, identify the issue and avoid pretending the audit is professional legal advice.