Agent skill · operations · sickn33
pre-release-review
Run a read-only pre-release review for deploy readiness, migrations, config, secrets, rollout order, rollback risk, and launch blockers.
Why this skill is useful
Adds a structured pre-release review process that identifies deployment risks and gaps not typically covered in standard CI/CD practices.
What it needs
Requires gh, git, rg installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Pre-release Review Use this skill to run a read-only production release readiness review. The goal is to reduce release time and coordination failures by finding missing deploy materials, unsafe ordering, configuration gaps, data migration gaps, and ambiguous production risks before CI/CD or manual release steps begin. When to Use This Skill Use when the user asks for a release audit, pre-release review, go-live review, or deploy readiness check. Use before publishing a tag, deploying production services, or merging a release branch. Use when a PR or git range may include migrations, environment changes, queues, cache behavior, object storage assets, or service contract changes. Use when the user asks whether a change is safe to ship and needs a read-only risk report. Non-negotiable rules Do not modify source code, configs, migrations, secrets, deployment files, or generated files. Do not execute migrations, clear or warm caches, upload assets, trigger CI/CD, deploy services, publish tags, rotate secrets, or change remote infrastructure. Produce a concise report that lists only confirmed problems and plausible risks needing confirmation. Do not bury the reader in clean checklist items. Sort findings from highest to lowest priority. Include module, finding, evidence, inferred owner, risk, and recommended action for each item. Never reveal private keys, account passwords, tokens, certificates, cookies, or full secret values. Report only file path, line number, variable name, secret type, and a redacted hint. If evidence is incomplete but the risk could block production, list it as a confirmation item. Required references Read references/checklist.md before analyzing findings so important release domains are not skipped. Read references/report-template.md before writing the final report so priorities, owner inference, secret redaction, and output shape stay consistent. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/pre-release-review--612260