Pre release verification

Skill yeaight7/agent-powerups/skills/pre-release-verification

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

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.

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,524 of the 2,830 authors here whose files we hold, read 2026-09-06

Read full output and check exit codein 45 of 1524, across 40 files
Verify output confirms the claimin 44 of 1524, across 39 files
Identify the command that proves the claimin 43 of 1524, across 39 files
Execute the full verification commandin 36 of 1524, across 30 files
Produce a verification reportin 34 of 1524, across 18 files
Review git diff changesin 30 of 1524, across 16 files
Fix build failures immediatelyin 29 of 1524, across 9 files
Group findings by severityin 28 of 1524
State claim only with evidencein 27 of 1524, across 22 files
Verify regression tests with red-green cyclein 26 of 1524, across 22 files
Run the full test suitein 26 of 1524, across 25 files
Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

Confirm CI status for the release commit
Check for secrets or accidental files
Report go or no-go with 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.