From auro-release-process
Run the Auro 2.0 release-caused incident response — the first hour after a bad release. Use when a post-deploy smoke test fails, an error or latency spike appears after a recent deploy, a PagerDuty alert fires on a service just released to, a customer reports a problem within the active monitoring window, or the team explicitly says they have a release incident. Trigger with "release incident", "we just deployed and it's broken", "error spike post-deploy", "should we roll back or fix forward", "open the incident thread", "post-deploy issue", "P1 release issue", or "P2 release issue". Walks the release runner through detection, triage, severity, the rollback-vs-fix-forward decision, internal and customer comms, resolution, and postmortem handover. Drafts Teams updates, in-app banner copy, status-page entries, and resolution summaries on demand. Do not trigger for general production incidents not linked to a recent deploy, planned maintenance, or unrelated tech debt.
How this skill is triggered — by the user, by Claude, or both
Slash command
/auro-release-process:release-incident-responseThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> Required connectors: ClickUp, GitHub. See [CONNECTORS.md](../../CONNECTORS.md).
Required connectors: ClickUp, GitHub. See CONNECTORS.md.
This skill operationalises the Auro 2.0 Release Incident Response process. The canonical document is the Release Incident Response page in the ClickUp Release Process Playbook; this skill is the active companion that helps the release runner work the process under pressure.
Invoke this skill when any of the following is happening within the one-hour active monitoring window after a release:
If the symptoms started before the deploy or have no plausible link to the change set, stop — this is a general production incident; defer to the Alerting & Incident Management Plan.
This skill is a tactical companion. When invoked:
| Level | Criteria | Default action |
|---|---|---|
| P1 | Production down, data loss, security breach, all customers affected | Page on-call immediately. Roll back unless rollback unsafe. |
| P2 | Major feature broken, significant degradation, partial outage | 15-min response. Roll back unless small fix already prepared. |
| P3 | Minor issues, single customer, non-critical errors | 4-hour response. Usually fix forward in next release. |
| P4 | Cosmetic, warnings, low-impact | Ticket. Fix forward in next release. |
INCIDENT — [severity] — [one-line symptom] — deploy at [time] — investigating
Apply the rollback-vs-fix-forward criteria. Roll back unless all of the following are true:
If any point is uncertain, roll back. If rolling back, hand off to the release-rollback skill — the release runner cannot self-serve a production rollback; the tech lead or EM has to trigger the workflow.
For P1 / P2 customer-visible incidents:
We are currently investigating a problem with [feature].
Updates will be posted here as we learn more.
Resolution post template for the Teams thread:
RESOLVED — [one-line symptom] — [duration: HH:MM]
Cause: [one-line cause, can be "TBC, see postmortem"]
Action taken: [rollback / hotfix vX.Y.Z]
Customers affected: [scope]
Postmortem: [ClickUp link]
Open the postmortem entry against the release rollup. P1 / P2 get a full postmortem within 5 working days; P3 gets a short note on the rollup; P4 gets a brief note on the rollup.
When invoked, offer to draft any of:
release-rollback skill / Rollback Runbook.Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub harmonysmarttechnology/auro-engineering-marketplace --plugin auro-release-process