Skip to content
Back to skills

Pre Release Verification

ASecurity

Use before tagging a release or deploying to production to ensure all quality gates have passed.

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 29, 2026
ai-agentsgogitapi

Works with

  • cli
  • api

Security analysis

A100/100

Scanned May 29, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Pre Release Verification?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pre Release Verification
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yeaight7-pre-release-verification/badge)](https://www.skillsdirectory.com/skills/yeaight7-pre-release-verification)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: pre-release-verification
description: "Use before tagging a release or deploying to production to ensure all quality gates have passed."
---

# Pre-Release Verification

Releases must be deterministic and verified. No "hope driven" deployments.

## Verification Checklist

Before authorizing or participating in a release process, verify the following:

1. **Clean Working Tree**: `git status` must be completely clean. No untracked files or uncommitted changes.
2. **Green CI**: The latest commit on the main branch MUST have a passing CI pipeline.
3. **Lint & Types**: Run the project's linter (`npm run lint`, `cargo clippy`, etc.) and type checker (`tsc --noEmit`). They must exit with 0.
4. **Test Gate**: Run the full test suite locally if CI is not available or if requested.
5. **No Secrets**: Ensure no API keys or credentials have been accidentally hardcoded or staged.

If any check fails, the release is blocked. State the exact failure and stop.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…