[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7882X53XGCCS06H6MAR8SF5":3,"skill-same:01M7882X53XGCCS06H6MAR8SF5":46},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":45},"01M7882X53XGCCS06H6MAR8SF5","deploy-verify-loop",null,"Post-deploy verification loop — poll a rollout until every instance is on the new version and healthy, then run one smoke check against a real user path. Meant to be handed to a time-based loop with a timeout, not polled by hand.","officialunofficial\u002Fskills","officialunofficial","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F127067914?v=4","01M78827JABEMMN63AC8J1RCXV","Official Unofficial, Inc.","01M78827KC164SFKN4DXTCKK7N",7,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fofficialunofficial\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fdeploy-verify-loop\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: deploy-verify-loop\ndescription: Post-deploy verification loop — poll a rollout until every instance is on the new version and healthy, then run one smoke check against a real user path. Meant to be handed to a time-based loop with a timeout, not polled by hand.\ndisable-model-invocation: true\n---\n\n# Deploy-verify loop\n\nA deploy that reports success isn't the same as a deploy that's actually healthy — a rollout can finish while a pod crash-loops, a health check flakes, or the new version 400s on a path the deploy step never exercised. This loop watches the window right after a deploy closes and turns \"did it work?\" into a checked answer instead of a hope.\n\n## Step 1 — Establish what \"rolled out\" means here\n\nBefore polling, confirm the concrete signal for this deploy target — it varies by platform:\n\n- Kubernetes: every replica of the relevant Deployment(s)\u002FStatefulSet(s) on the new image digest\u002Ftag, `Ready`, no `CrashLoopBackOff`.\n- A PaaS\u002Fserverless platform: the release\u002Fdeployment resource's own status field reaches its terminal \"active\"\u002F\"succeeded\" state.\n- A generic host: the running process's version endpoint (or build hash) matches what you just shipped.\n\n**Done when** you can name the exact check that proves the rollout finished — not \"give it a few minutes.\"\n\n## Step 2 — Poll with a bound, not indefinitely\n\nCheck the Step 1 signal on an interval matched to how fast this deploy actually rolls (a Kubernetes rollout finishes in seconds to minutes; a CDN\u002Fedge propagation can take longer — don't poll a slow system every few seconds). Set a hard timeout. If the timeout is reached before the signal clears, stop and report exactly what's still not ready — don't keep polling past the bound hoping it resolves.\n\n## Step 3 — Check for the failure the rollout signal can't see\n\nA rollout can report \"ready\" while the new version is still wrong: pull recent logs for the just-deployed instances and scan for a crash loop, an elevated error rate, or a startup panic that a readiness probe doesn't catch. If anything here looks wrong, stop and report it — don't proceed to the smoke check against something already unhealthy.\n\n## Step 4 — Run one smoke check\n\nExercise a real, critical-path action end to end (not just a `\u002Fhealth` endpoint returning 200) — whatever this system's core round-trip is: a request that touches the code you just shipped, not a static page. One meaningful check beats a broad shallow sweep here; the goal is \"does the thing users actually do still work,\" not full regression coverage.\n\n**Done when** the smoke check has run against the newly-deployed instance and you have a pass\u002Ffail result, not an assumption.\n\n## Step 5 — Report and stop\n\n- **Success** — rollout signal cleared, no failure signs in logs, smoke check passed. Stop the loop.\n- **Failure** — name exactly which step failed and what you observed (the specific pod\u002Finstance, the specific log line, the specific smoke-check response). Don't just say \"deploy looks broken\" — a report that isn't actionable defeats the point of automating the watch.\n- **Timeout** — report current state as of the timeout, not a guess about what would happen if you kept waiting.\n\nDo not roll back, restart, or otherwise change the running system as part of this loop — verification surfaces the problem; fixing it is a separate, deliberate decision.\n","# Deploy-verify loop\n\nA deploy that reports success isn't the same as a deploy that's actually healthy — a rollout can finish while a pod crash-loops, a health check flakes, or the new version 400s on a path the deploy step never exercised. This loop watches the window right after a deploy closes and turns \"did it work?\" into a checked answer instead of a hope.\n\n## Step 1 — Establish what \"rolled out\" means here\n\nBefore polling, confirm the concrete signal for this deploy target — it varies by platform:\n\n- Kubernetes: every replica of the relevant Deployment(s)\u002FStatefulSet(s) on the new image digest\u002Ftag, `Ready`, no `CrashLoopBackOff`.\n- A PaaS\u002Fserverless platform: the release\u002Fdeployment resource's own status field reaches its terminal \"active\"\u002F\"succeeded\" state.\n- A generic host: the running process's version endpoint (or build hash) matches what you just shipped.\n\n**Done when** you can name the exact check that proves the rollout finished — not \"give it a few minutes.\"\n\n## Step 2 — Poll with a bound, not indefinitely\n\nCheck the Step 1 signal on an interval matched to how fast this deploy actually rolls (a Kubernetes rollout finishes in seconds to minutes; a CDN\u002Fedge propagation can take longer — don't poll a slow system every few seconds). Set a hard timeout. If the timeout is reached before the signal clears, stop and report exactly what's still not ready — don't keep polling past the bound hoping it resolves.\n\n## Step 3 — Check for the failure the rollout signal can't see\n\nA rollout can report \"ready\" while the new version is still wrong: pull recent logs for the just-deployed instances and scan for a crash loop, an elevated error rate, or a startup panic that a readiness probe doesn't catch. If anything here looks wrong, stop and report it — don't proceed to the smoke check against something already unhealthy.\n\n## Step 4 — Run one smoke check\n\nExercise a real, critical-path action end to end (not just a `\u002Fhealth` endpoint returning 200) — whatever this system's core round-trip is: a request that touches the code you just shipped, not a static page. One meaningful check beats a broad shallow sweep here; the goal is \"does the thing users actually do still work,\" not full regression coverage.\n\n**Done when** the smoke check has run against the newly-deployed instance and you have a pass\u002Ffail result, not an assumption.\n\n## Step 5 — Report and stop\n\n- **Success** — rollout signal cleared, no failure signs in logs, smoke check passed. Stop the loop.\n- **Failure** — name exactly which step failed and what you observed (the specific pod\u002Finstance, the specific log line, the specific smoke-check response). Don't just say \"deploy looks broken\" — a report that isn't actionable defeats the point of automating the watch.\n- **Timeout** — report current state as of the timeout, not a guess about what would happen if you kept waiting.\n\nDo not roll back, restart, or otherwise change the running system as part of this loop — verification surfaces the problem; fixing it is a separate, deliberate decision.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","e1e71e8aa302edca3e052370aefa9272f86d07ee","skills\u002Fengineering\u002Fdeploy-verify-loop",0,"https:\u002F\u002Fgithub.com\u002Fofficialunofficial\u002Fskills","https:\u002F\u002Fgithub.com\u002Fofficialunofficial","officialunofficial.com","2026-11-06 10:07:10",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add officialunofficial\u002Fskills --skill deploy-verify-loop",{"tool":39,"command":40},"bunx","bunx skills add officialunofficial\u002Fskills --skill deploy-verify-loop",{"tool":42,"command":43},"pnpm","pnpm dlx skills add officialunofficial\u002Fskills --skill deploy-verify-loop","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fofficialunofficial\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fdeploy-verify-loop\u002FSKILL.md",[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7887BDP2BC5HFHEKCNMBZ4Q","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002Fofficialunofficial\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwriting-great-skills\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M788772K4QYXCZX3Y2P2AX9V","technical-writing","House style for technical writing — the voice, sentence craft, formatting, and user-facing-copy rules that make docs and product text clear, direct, and consistent. Use when writing or editing a README, docs, a spec, release notes, a changelog, help text, or any error\u002FCLI\u002FUI copy a person reads; when reviewing a diff that touches prose or messages; or when a project needs a writing standard. Reference-heavy mechanics live in REFERENCE.md.","https:\u002F\u002Fgithub.com\u002Fofficialunofficial\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M78875087F1XKP7C6VRC49CY","teach","Teach the user a new skill or concept, within this workspace.","https:\u002F\u002Fgithub.com\u002Fofficialunofficial\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fteach\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M78872Z38MACN22AQDY9410P","handoff","Compact the current conversation into a handoff document for another agent to pick up.","https:\u002F\u002Fgithub.com\u002Fofficialunofficial\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fhandoff\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M78870FVRDYRT1WVP9HJ6FQ3","grilling","Interrogate the user's plan or design one decision at a time until you both share the same understanding. Use when the user wants to pressure-test an idea before building it, or reaches for any 'grill' trigger phrase.","https:\u002F\u002Fgithub.com\u002Fofficialunofficial\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fgrilling\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7886XGPEWXZYDA6K310HNYP","grill-me","A relentless, one-decision-at-a-time interview that sharpens a plan or design.","https:\u002F\u002Fgithub.com\u002Fofficialunofficial\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fgrill-me\u002FSKILL.md",[],[]]