Deploy checklist writer

Skill rakibulism/agent-skills-os/skills/deploy-checklist-writer

THE UNIVERSAL AGENT SKILLS LIBRARY

Install

npx -y skills add rakibulism/agent-skills-os --skill deploy-checklist-writer

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

2 stars2 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.

What its author says it does

Copied from the file, not written here

Builds a pre-deployment verification checklist covering migrations, feature flags, rollback triggers, and approvals. Use before shipping a release or deploying a change with database migrations.

SKILL.md

2.7 KB, as published. Nobody here has run it

Deploy Checklist Writer

You produce a checklist specific to the actual change being deployed, not a generic boilerplate list.

How to build the checklist

Classify the change: schema migration, feature flag rollout, config change, dependency bump, infra change, or a combination. The checklist items depend entirely on this classification.
For migrations: is it backward-compatible with the currently-running code (can old and new code both run against the new schema during rollout)? Is there a backfill, and does it lock the table? Is the migration reversible?
For feature flags: what's the default state, what's the rollout plan (percentage, cohort), what's the kill switch?
For every change: what does CI status need to be, what approvals are required, is there a maintenance window needed, what's the traffic pattern risk (deploying before a known high-traffic period)?
Define rollback triggers up front — the specific metric/error thresholds that mean "roll back now," decided before deploy, not improvised during an incident.
Define the rollback procedure itself: is it a revert-and-redeploy, a flag flip, or does the migration make rollback non-trivial (and if so, say so loudly)?

Output format

## Change classification
<migration / flag / config / infra / combination>

## Pre-deploy
- [ ] CI green on <branch>
- [ ] <migration-specific or flag-specific items>
- [ ] Required approvals: <who>
- [ ] Maintenance window needed: <yes/no, why>

## Deploy steps
1. ...

## Rollback triggers
- <metric/error> exceeds <threshold> within <time window>

## Rollback procedure
<specific steps — flag flip / revert / manual data-fix needed>

## Post-deploy verification
- [ ] <specific thing to check, e.g. "error rate on /checkout back to baseline">

What to avoid

Don't include generic items ("test in staging") without saying what specifically needs testing given this change.
Don't skip calling out irreversible migrations — flag them explicitly as higher risk.
Don't set rollback triggers after the fact; they must be defined before the deploy happens.