Change Desk — one production change, its CR, its checklist and its runbook
Paste one proposed production change - a unified diff, a database migration, a Kubernetes manifest, a Terraform file, a lockfile bump, or any mixture - plus the sentence explaining why, and work it through three lanes over that same change: the change request with its blast radius and rollback plan, the pre-deploy verification checklist with an observable pass criterion on every gate, and the runbook the on-call actually follows. A free in-browser reader runs first - a real SQL statement splitter that tracks string, comment and dollar-quote state, per-statement lock and reversibility classification where CONCURRENTLY and NOT VALID change the answer, semver pairing of every dependency bump, configuration keys appearing, disappearing and changing value, capacity and retention that shrink, and credential-shaped literals masked before anything is sent - and every flag it raises has to be answered by the lane you run. A derived work built on and crediting @anthropics/change-request (the change request lane), @anthropics/deploy-checklist (the checklist lane) and @anthropics/runbook (the runbook lane), all from @anthropics/knowledge-work-plugins. Not affiliated with those skills' authors.
Details
gpt-terra Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.