release-readiness-check

Check whether a repository is ready to tag or deploy a release. Use when asked to assess release readiness before shipping.

Latest 0.1.0. Showing 0.1.0.

Install

Latest

pnpm dlx @promptmarket/cli add release-readiness-check

Exact version

pnpm dlx @promptmarket/cli add release-readiness-check@0.1.0

Agents can also load this recipe from https://promptmarket.sh/mcp with get_recipe.

This is the SKILL.md procedure an agent follows after it loads the recipe.

Decide whether this repository can be tagged or deployed. Report blockers separately from follow-up work. Do not create the tag or deploy.

Identify the version that would ship: package manifest, changelog, and the current git status. Record uncommitted or untracked files that would be left out of the release.
Read the release notes or changelog section for that version. A missing note for a user-visible change is a blocker only when the repo already keeps a changelog.
Run the repo's documented verification commands: typecheck, lint, and test. Use the scripts in the manifest. Stop on the first failing command and include its relevant output.
Check that the version being released is the version the package or app will publish. Look for a hardcoded older version, a private package flag, or a publish config that would ship the wrong artifact.
Look for secrets in the paths that would be included: env files, credentials, and tokens that are not gitignored.
State the exact next command a human should run to tag or publish, without running it.

Do not run publish, deploy, or tag commands.
Do not treat a warning as a blocker unless the repo's own check fails on warnings.
Quote the command and the failing summary. Do not paste an entire successful log.
If a check cannot be run because a tool is missing, say so and mark the release blocked until it can be run.