[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSH704M60T2GKXY5FV45CM":3,"skill-same:01M7CSH704M60T2GKXY5FV45CM":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CSH704M60T2GKXY5FV45CM","rollback-runbook",null,"Use before and after calling rollback_release - what a rollback restores per delivery mode, when a schema change makes a code rollback unsafe, how to work and report manual_steps, and what to do when rollback_release refuses","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Frelease-engineer\u002Fskills\u002Frollback-runbook\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: rollback-runbook\ncategory: release\ndescription: Use before and after calling rollback_release - what a rollback restores per delivery mode, when a schema change makes a code rollback unsafe, how to work and report manual_steps, and what to do when rollback_release refuses\nsource: ankane\u002Fstrong_migrations (MIT), wshobson\u002Fagents (MIT), adapted\n---\n\n# Rollback runbook\n\n`rollback_release` always reverts the release's task merge commits on the default branch and pushes that revert — production can never ship the bad change again, whatever else happens. What restores the RUNNING service depends on the component's delivery mode:\n\n- **`dispatch`** — the previous good release's commit is tagged and the deploy workflow is dispatched at it (`Mechanism: workflow_dispatch`). No previous release: it dispatches at the revert commit instead.\n- **`on_merge`** — the revert push itself is the redeploy (`Mechanism: revert_push`); there is nothing else to trigger.\n- **`batch`** (desktop, mobile) — nothing is redeployed. `Status` goes straight to `rolled_back`: a published desktop build or a store build cannot be unpublished by reverting a git commit, so there is no redeploy for `watch_release` to follow. See `batch-artifact-verification` for the yank step.\n\nFor `dispatch`\u002F`on_merge`, `Status` becomes `rolling_back` and you are expected to call `watch_release` again to follow the redeploy through to `rolled_back`.\n\n## Before you roll back: check what schema the release changed\n\nA code revert is not automatically safe. For each task in `release.tasks`, `get_task_pull_request({ task_id, include_diff: false })` to list files, then look for migration paths: `migrations\u002F`, `db\u002Fmigrate\u002F`, `prisma\u002Fmigrations\u002F`, `alembic\u002Fversions\u002F`, `V*__*.sql`, `*.up.sql`. Read the up file (`get_task_pull_request` with the diff, or `read_file`) for any match.\n\n- **Additive** — `CREATE TABLE`\u002F`CREATE INDEX`, `ADD COLUMN` that is nullable or has a constant default: reverting the code is safe. The previous version simply ignores the new objects — **leave the schema in place**; do not drop what the forward migration added.\n- **Destructive or renaming** — `DROP COLUMN`\u002F`DROP TABLE`, `RENAME COLUMN`\u002F`RENAME TABLE`, `ALTER COLUMN TYPE`, `SET NOT NULL` on an existing column: the previous version may not run against this schema at all. If the task's `rollback_plan` covers it, follow the plan exactly. Otherwise do **not** call `rollback_release` — comment the evidence plus \"a code rollback would run the previous version against a schema it does not know — needs a human: forward fix or a down-migration first\", and stop.\n\nThis is the parallel-change pattern (DORA): decouple a database change from the application change that depends on it, so either one can revert on its own. A migration that only adds is reversible by the code revert alone; one that removes or reshapes is not, unless a plan already accounted for it.\n\n## What a revert cannot undo\n\n`git revert` undoes code. It does not:\n\n- reverse a database migration,\n- turn a feature flag back off,\n- purge a CDN or cache,\n- roll back a third-party configuration change,\n- un-send a webhook, an email, or anything else the code triggered while it ran.\n\n`rollback.manual_steps` is exactly this list, built from each rolled-back task's own `rollback_plan`\u002F`before_deploy`\u002F`after_deploy` fields — the developer who made the change is the only one who knew which of these applied.\n\n## Batch releases add one more, first\n\nFor a `batch` release, `manual_steps` puts one entry ahead of the tasks' own: unpublish or halt the artifact the revert cannot touch. See `batch-artifact-verification` for the exact commands. Treat it like any other manual step: perform it if you can, report it if you cannot, and put it first in your report — it is the step that actually stops the bad build reaching more users, not the code revert.\n\n## Work through it\n\n1. Read every item in `manual_steps`.\n2. Perform every one you can with the tools you have — most manual steps are outside this system's reach (a third-party console, a human-run command) and are for a human; `release-terminal-scope` names the one write you may make yourself.\n3. Say explicitly, on the card, which ones you performed and which you could not, and who has to finish them.\n\n✅ \"Reverted the code (revert `a1b2c3d`). Left for a human: migration 043 added `tasks.priority` (`NOT NULL DEFAULT 'medium'`); the previous version ignores it, so it stays — dropping it would discard values written since the deploy. T-12's `after_deploy` enabled flag `new_pricing`: turn it off in the flag console. T-14 recorded no rollback plan.\"\n\n❌ \"Rolled back; the column added by migration 042 needs a human to drop it.\" — additive columns are not dropped; see \"Before you roll back\" above.\n\nA rollback reported as complete when half of it was not is worse than one that admits what it did not do — the next release will ship on top of whatever was left half-undone.\n\n## No plan recorded\n\nIf a rolled-back task recorded no rollback plan at all, say that too. The absence is a finding for whoever reviews this release next, not something to paper over with \"nothing else to do here\".\n\n## When rollback_release refuses\n\nDo not retry — a refusal here is final the same way a merge refusal is (`board_rollback_release_refused`):\n\n- **Too old** (more than 24h since it was released) or **a newer release already shipped** — production now runs something newer than what you'd be rolling back to. One comment saying so, and that this needs a forward fix as a new task (a human or PM call), then stop.\n- **A newer release is open** — resolve that one first; leave this one alone.\n- **`verifying` or `deploying`** — the sweeper will hand it back to you at the right moment; stop and let it.\n","# Rollback runbook\n\n`rollback_release` always reverts the release's task merge commits on the default branch and pushes that revert — production can never ship the bad change again, whatever else happens. What restores the RUNNING service depends on the component's delivery mode:\n\n- **`dispatch`** — the previous good release's commit is tagged and the deploy workflow is dispatched at it (`Mechanism: workflow_dispatch`). No previous release: it dispatches at the revert commit instead.\n- **`on_merge`** — the revert push itself is the redeploy (`Mechanism: revert_push`); there is nothing else to trigger.\n- **`batch`** (desktop, mobile) — nothing is redeployed. `Status` goes straight to `rolled_back`: a published desktop build or a store build cannot be unpublished by reverting a git commit, so there is no redeploy for `watch_release` to follow. See `batch-artifact-verification` for the yank step.\n\nFor `dispatch`\u002F`on_merge`, `Status` becomes `rolling_back` and you are expected to call `watch_release` again to follow the redeploy through to `rolled_back`.\n\n## Before you roll back: check what schema the release changed\n\nA code revert is not automatically safe. For each task in `release.tasks`, `get_task_pull_request({ task_id, include_diff: false })` to list files, then look for migration paths: `migrations\u002F`, `db\u002Fmigrate\u002F`, `prisma\u002Fmigrations\u002F`, `alembic\u002Fversions\u002F`, `V*__*.sql`, `*.up.sql`. Read the up file (`get_task_pull_request` with the diff, or `read_file`) for any match.\n\n- **Additive** — `CREATE TABLE`\u002F`CREATE INDEX`, `ADD COLUMN` that is nullable or has a constant default: reverting the code is safe. The previous version simply ignores the new objects — **leave the schema in place**; do not drop what the forward migration added.\n- **Destructive or renaming** — `DROP COLUMN`\u002F`DROP TABLE`, `RENAME COLUMN`\u002F`RENAME TABLE`, `ALTER COLUMN TYPE`, `SET NOT NULL` on an existing column: the previous version may not run against this schema at all. If the task's `rollback_plan` covers it, follow the plan exactly. Otherwise do **not** call `rollback_release` — comment the evidence plus \"a code rollback would run the previous version against a schema it does not know — needs a human: forward fix or a down-migration first\", and stop.\n\nThis is the parallel-change pattern (DORA): decouple a database change from the application change that depends on it, so either one can revert on its own. A migration that only adds is reversible by the code revert alone; one that removes or reshapes is not, unless a plan already accounted for it.\n\n## What a revert cannot undo\n\n`git revert` undoes code. It does not:\n\n- reverse a database migration,\n- turn a feature flag back off,\n- purge a CDN or cache,\n- roll back a third-party configuration change,\n- un-send a webhook, an email, or anything else the code triggered while it ran.\n\n`rollback.manual_steps` is exactly this list, built from each rolled-back task's own `rollback_plan`\u002F`before_deploy`\u002F`after_deploy` fields — the developer who made the change is the only one who knew which of these applied.\n\n## Batch releases add one more, first\n\nFor a `batch` release, `manual_steps` puts one entry ahead of the tasks' own: unpublish or halt the artifact the revert cannot touch. See `batch-artifact-verification` for the exact commands. Treat it like any other manual step: perform it if you can, report it if you cannot, and put it first in your report — it is the step that actually stops the bad build reaching more users, not the code revert.\n\n## Work through it\n\n1. Read every item in `manual_steps`.\n2. Perform every one you can with the tools you have — most manual steps are outside this system's reach (a third-party console, a human-run command) and are for a human; `release-terminal-scope` names the one write you may make yourself.\n3. Say explicitly, on the card, which ones you performed and which you could not, and who has to finish them.\n\n✅ \"Reverted the code (revert `a1b2c3d`). Left for a human: migration 043 added `tasks.priority` (`NOT NULL DEFAULT 'medium'`); the previous version ignores it, so it stays — dropping it would discard values written since the deploy. T-12's `after_deploy` enabled flag `new_pricing`: turn it off in the flag console. T-14 recorded no rollback plan.\"\n\n❌ \"Rolled back; the column added by migration 042 needs a human to drop it.\" — additive columns are not dropped; see \"Before you roll back\" above.\n\nA rollback reported as complete when half of it was not is worse than one that admits what it did not do — the next release will ship on top of whatever was left half-undone.\n\n## No plan recorded\n\nIf a rolled-back task recorded no rollback plan at all, say that too. The absence is a finding for whoever reviews this release next, not something to paper over with \"nothing else to do here\".\n\n## When rollback_release refuses\n\nDo not retry — a refusal here is final the same way a merge refusal is (`board_rollback_release_refused`):\n\n- **Too old** (more than 24h since it was released) or **a newer release already shipped** — production now runs something newer than what you'd be rolling back to. One comment saying so, and that this needs a forward fix as a new task (a human or PM call), then stop.\n- **A newer release is open** — resolve that one first; leave this one alone.\n- **`verifying` or `deploying`** — the sweeper will hand it back to you at the right moment; stop and let it.\n",{"name":5,"source":24,"category":25,"description":7},"ankane\u002Fstrong_migrations (MIT), wshobson\u002Fagents (MIT), adapted","release","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Frelease-engineer\u002Fskills\u002Frollback-runbook",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill rollback-runbook",{"tool":41,"command":42},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill rollback-runbook",{"tool":44,"command":45},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill rollback-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Frelease-engineer\u002Fskills\u002Frollback-runbook\u002FSKILL.md",true,[],[50,56,63,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","ux-copy","Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CSV6H0J38659NDXHJQ8396","screen-mockup-html","Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CSV3JFRF3BM3XK52M7YEYR","performance-awareness","How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CSTZDH00YRF5SCT7BRT9QD","design-variants","Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CSTV6P3SM3PAE28DB0RF77","design-system-authoring","Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]