| name | pre-release-review |
| description | Run a read-only pre-release review for deploy readiness, migrations, config, secrets, rollout order, rollback risk, and launch blockers. |
| category | operations |
| risk | safe |
| source | community |
| source_repo | chaunsin/agent-skills |
| source_type | community |
| date_added | 2026-06-29 |
| author | chaunsin |
| tags | ["release","deploy-readiness","ci-cd","rollback","production"] |
| tools | ["git","gh","rg"] |
| license | Apache-2.0 |
| license_source | https://github.com/chaunsin/agent-skills/blob/master/LICENSE |
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.
Project guidance discovery
Before interpreting the release diff, look for project-local guidance files such as AGENTS.md and
CLAUDE.md in the repository root and relevant service directories. Read them when present so the
review respects the user's project-specific conventions, service boundaries, release rules,
validation expectations, ownership hints, and known operational constraints.
- Treat project guidance as context for how to interpret risks, not as permission to perform
mutating release actions.
- If project guidance conflicts with this skill's non-negotiable safety rules, the read-only,
no-secret-disclosure rules in this skill win.
