Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
Audits release readiness by classifying risk level, checking verification evidence, and confirming operational readiness before deploying or merging.
npx claudepluginhub bravekingzhang/agent-coding-playbook --plugin agent-coding-playbookHow this skill is triggered — by the user, by Claude, or both
Slash command
/agent-coding-playbook:acp-release-checkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill before releasing, deploying, publishing, or merging a change into a production-bound branch.
Audits production readiness using local evidence: runtime, auth, data, payments, background tasks, AI, and deployment boundaries. For pre-release, post-merge, or 'what will break in production?' questions.
Audits production readiness of apps using local evidence only. Useful for pre-launch reviews, post-merge checks, and 'what breaks in prod?' questions without sending repo data externally.
Generates customizable pre-deployment checklists to verify CI status, tests, reviews, migrations, feature flags, rollback plans, and monitor production deploys.
Share bugs, ideas, or general feedback.
Use this skill before releasing, deploying, publishing, or merging a change into a production-bound branch.
The goal is to reduce release risk, not to create a long ceremony.
Summarize:
Classify the release as low, medium, or high risk.
High-risk signals:
Look for:
If evidence is missing, mark it as a release risk.
Confirm:
Release scope:
- ...
Risk level:
- Low / Medium / High
Verification evidence:
- ...
Missing evidence:
- ...
Rollback plan:
- ...
Recommendation:
- Go / Go with caution / No-go
Do not say a release is safe only because the code compiles.
A release is safe when the change scope, verification evidence, runtime observability, and rollback path are all clear.