release-check
Standardizes the pre-release checklist to ensure builds, tests, and documentation are ready.
Install
mkdir -p .claude/skills/release-check-work-w-chrstnrpj && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15896" && unzip -o skill.zip -d .claude/skills/release-check-work-w-chrstnrpj && rm skill.zipInstalls to .claude/skills/release-check-work-w-chrstnrpj
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Prepare code for merge or release with verification, docs, environment, and deployment checks.Key capabilities
- →Confirm scope and unresolved work
- →Review lint, typecheck, test, build, and e2e commands
- →Check documentation and changelog
- →Verify environment variables and deployment notes
- →Confirm no secrets or unrelated local files are included
How it works
The skill guides through a workflow of verification, documentation, environment, and deployment checks to prepare code for merge or release.
Inputs & outputs
When to use release-check
- →Prepare for production release
- →Verify code before merge
- →Update deployment documentation
- →Run final build checks
About this skill
Release Check
Workflow
- Confirm scope and unresolved work.
- Review relevant lint, typecheck, test, build, and e2e commands from project docs.
- Check docs, changelog, environment variables, deployment notes, and generated files.
- Confirm no secrets, large generated outputs, or unrelated local files are included.
- Summarize verification results and known risks.
Boundaries
- Do not deploy to production without approval.
- Do not claim checks passed unless they ran or were reviewed from reliable output.
- Do not include generated graph or snapshot outputs unless intentionally reviewed.
Output
- Relevant files or docs inspected.
- Work completed or plan produced.
- Tests or verification run or recommended.
- Docs updated or skipped with reason.
- Remaining risks, assumptions, and handoffs.
When not to use it
- →When deploying to production without approval
- →When claiming checks passed without reliable output
- →When including generated graph or snapshot outputs without intentional review
Limitations
- →Does not deploy to production without approval
- →Does not claim checks passed unless they ran or were reviewed from reliable output
- →Does not include generated graph or snapshot outputs unless intentionally reviewed
How it compares
This skill provides a structured checklist for release preparation, ensuring all critical aspects are reviewed before merge or deployment, unlike an informal check.
Compared to similar skills
release-check side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| release-check (this skill) | 0 | 1mo | No flags | Intermediate |
| agent-workflow-automation | 4 | 6mo | Review | Advanced |
| project-os | 1 | 6mo | Review | Intermediate |
| project-tooling | 1 | 4mo | Caution | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by work-w-chrstnrpj
View all by work-w-chrstnrpj →You might also like
agent-workflow-automation
ruvnet
Agent skill for workflow-automation - invoke with $agent-workflow-automation
project-os
Peiiii
AI project OS for autonomous loop, automated orchestration, and rule-driven execution.
project-tooling
alinaqi
gh, vercel, supabase, render CLI and deployment platform setup
release-version
corvo007
Use when releasing a new version - guides through version bump, changelog generation, commit grouping, tagging, and GitHub CI tracking. Triggers on "发布新版本", "release", "发版", or version release requests.
Release
tobagin
Create a new Keymaker release — analyze changes, bump version, update changelog/README/AppStream metadata, build, commit, tag, push, and create GitHub release
release
RajwanYair
Bump the version, update the changelog, tag, and publish a GitHub release for RegiLattice. Use when preparing a new release, updating version numbers, creating a CHANGELOG entry, or pushing a version tag to trigger the CI release workflow. Triggers on: 'bump version', 'release', 'publish', 'version'