Pre release verification

Skill yeaight7/agent-powerups/plugins/quality-gates/skills/pre-release-verification

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

Install

npx -y skills add yeaight7/agent-powerups --skill pre-release-verification

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when a release candidate needs final checks before tagging, publishing, or production deployment.

SKILL.md

2.1 KB, 472 tokens by cl100k_base, as published. Nobody here has run it

Purpose

Block releases until the repository state, CI status, local validation, and publish metadata are known and reproducible.

When to Use

Before creating a release tag.
Before deploying to production.
Before approving a release candidate prepared by another agent.
When CI is green but local package or catalog checks still need proof.

Do not use as a substitute for fixing failures. If any gate fails, stop and report the blocker.

Inputs

Intended version or deployment identifier
Current branch and commit
CI status for the release commit
Project-specific build, lint, test, and packaging commands

Workflow

Confirm the working tree is clean:

git status --short

Confirm the release commit and recent history:

git log --oneline --decorate -n 10

Confirm CI is green for the exact commit. For GitHub:

gh run list --limit 5
gh run view <run-id> --json conclusion,status,headSha,url

Run local validation. Use the project's documented commands, for example:

npm run build
npm test
python scripts/validate-skills.py
python scripts/validate-catalog.py

Check for secrets or accidental local files:

git diff --stat
git status --short

Report go/no-go with exact evidence.

Output

RELEASE VERIFICATION: go / no-go
Commit: <sha>
CI: <status and URL>
Local checks: <commands and results>
Blockers: <none or list>
Next action: <tag / deploy / stop>

Verification

Working tree was clean or dirty files were reported.
CI status was tied to the exact release commit.
Local validation commands exited 0.
No secrets or accidental local files were included.
Go/no-go recommendation included evidence, not confidence.

Failure Modes

Releasing from an uncommitted or untracked local state.
Checking CI for a different commit than the release candidate.
Treating lint/build success as full test coverage.
Continuing after a failed gate because the release is "small".

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most quality gates skills give in 472 tokens

Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-07

Read the output and check the exit codein 54 of 1195, across 14 files
Verify requirements using a line-by-line checklistin 53 of 1195, across 12 files
Identify the verification command proving the claimin 51 of 1195, across 12 files
Run the full verification commandin 50 of 1195, across 11 files
Verify output confirms the claimin 49 of 1195, across 12 files
Check version control diff after agent delegationin 46 of 1195, across 6 files
State claim with evidencein 44 of 1195, across 4 files
Run the test suitein 33 of 1195, across 26 files
Keep state in memory by defaultin 27 of 1195, across 6 files
Make prototype runnable with one commandin 26 of 1195, across 5 files
Produce a verification reportin 25 of 1195, across 14 files
Detect the package manager from lockfilesin 24 of 1195, across 5 files

Said here and by no other author read

confirm the working tree is clean
confirm the release commit history
confirm CI is green for the exact commit
check for secrets or accidental local files
report go or no-go with exact evidence

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.