Agent skill · DevOps & Cloud

pre-release-review

Run a read-only pre-release review for deploy readiness, migrations, config, secrets, rollout order, rollback risk, and launch blockers.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill pre-release-review --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 10 KB
Bundled scripts: none
Declared author: chaunsin
Path: skills/pre-release-review/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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

What's inside
Steps it walks through
  1. When to Use This Skill
  2. Non-negotiable rules
  3. Required references
  4. Project guidance discovery
  5. Scope selection
  6. Read-only evidence collection
  7. Review workflow
  8. Dirty worktree handling
  9. Evidence expectations
  10. Findings versus verification limits
  11. Output rules
  12. Limitations
  13. Test prompts
Ships with 2 files
  • references/checklist.md
  • references/report-template.md
Commands it runs
git status --short
git rev-parse --show-toplevel
git rev-parse --abbrev-ref HEAD
git rev-parse HEAD
rg --files -g 'AGENTS.md' -g 'CLAUDE.md'
git tag --merged HEAD --sort=-creatordate
git tag --points-at HEAD
git for-each-ref --sort=-creatordate --format="%(refname:short) %(objectname:short)" refs/tags
git describe --tags --abbrev=0 HEAD
git diff --name-status <base>..<head>
More from agentic-awesome-skills
All skills →
About this skill
What does the pre-release-review skill do?

Run a read-only pre-release review for deploy readiness, migrations, config, secrets, rollout order, rollback risk, and launch blockers.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill pre-release-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going