/release-check
Run the complete release readiness pipeline (version checks, changelog, final quality gates) and assign a release confidence score.
$ npx -y skills add yeaight7/agent-powerups --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/release-check
Context preview
What this command does when you run it.
Run the complete release readiness pipeline (version checks, changelog, final quality gates) and assign a release confidence score.
Command definition
release-check.mddescription: "Run the complete release readiness pipeline (version checks, changelog, final quality gates) and assign a release confidence score."
argument-hint: "<intended-version>"
Release Readiness Certification
Run the complete Agent Powerups release pipeline to ensure the repository is ready for a new version tag.
Process Overview
This command orchestrates a full readiness review.
1. Artifact Verification
- Check that the `package.json`, `Cargo.toml`, or relevant manifests contain the target version `$ARGUMENTS`.
- Ensure `CHANGELOG.md` has an entry for the target version, with categorized changes (Features, Fixes, Breaking).
2. Deep Quality Gate
- Trigger a full test suite run including integration and end-to-end tests if available.
- Ensure zero linting errors and clean type checks.
- Verify that there are no remaining FIXME, TODO(release), or unresolved merge conflict markers.
3. Dependency Audit
- Run a quick security audit on dependencies.
- Flag any critical vulnerabilities that must be resolved before cutting the release.
4. Certification Badge
Assign a confidence badge based on the results:
| Badge | Criteria | |-------|----------| | ๐ข Ready | All versions match, changelog is perfect, tests pass, no vulnerabilities. | | ๐ก Warn | Tests pass, but changelog lacks detail or minor dependency warnings exist. | | ๐ด Blocked | Tests fail, versions mismatch, or critical security vulnerabilities found. |
Output
Generate a comprehensive Release Certification markdown report detailing the findings in each phase and explicitly stating the final Go/No-Go decision.
Read more
description: "Run the complete release readiness pipeline (version checks, changelog, final quality gates) and assign a release confidence score." argument-hint: "<intended-version>"
Release Readiness Certification
Run the complete Agent Powerups release pipeline to ensure the repository is ready for a new version tag.
Process Overview
This command orchestrates a full readiness review.
1. Artifact Verification
- Check that the `package.json`, `Cargo.toml`, or relevant manifests contain the target version `$ARGUMENTS`.
- Ensure `CHANGELOG.md` has an entry for the target version, with categorized changes (Features, Fixes, Breaking).
2. Deep Quality Gate
- Trigger a full test suite run including integration and end-to-end tests if available.
- Ensure zero linting errors and clean type checks.
- Verify that there are no remaining FIXME, TODO(release), or unresolved merge conflict markers.
3. Dependency Audit
- Run a quick security audit on dependencies.
- Flag any critical vulnerabilities that must be resolved before cutting the release.
4. Certification Badge
Assign a confidence badge based on the results:
| Badge | Criteria | |-------|----------| | ๐ข Ready | All versions match, changelog is perfect, tests pass, no vulnerabilities. | | ๐ก Warn | Tests pass, but changelog lacks detail or minor dependency warnings exist. | | ๐ด Blocked | Tests fail, versions mismatch, or critical security vulnerabilities found. |
Output
Generate a comprehensive Release Certification markdown report detailing the findings in each phase and explicitly stating the final Go/No-Go decision.
Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more
Repo: yeaight7/agent-powerups
Other commands on agent-powerups.
- /bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Open command - /build-fix
Use when a build, type check, or test suite is failing and needs to be unblocked with a minimal change.
Open command - /debug
Use when a bug needs systematic diagnosis before a fix is attempted.
Open command - /doctor
Use to diagnose environment, tooling, and Agent Powerups setup problems.
Open command - /implement
Use to turn a spec or user request into working, tested code.
Open command - /mcp-check
Use to check MCP server prerequisites before activating or using a server.
Open command

