deploy-templates
Built-in deploy recipes and deploy targets. Use when a task asks you to set up or change a stage/preprod/prod deploy workflow, including the system's "Set up <env> deploy" tasks.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 122
- Forks
- 18
01 前言 Front Matter
- name
- deploy-templates
- category
- operations
- description
- Built-in deploy recipes and deploy targets. Use when a task asks you to set up or change a stage/preprod/prod deploy workflow, including the system's "Set up <env> deploy" tasks.
03 SKILL.md 正文
Deploy templates
Deploying is a defined step like build and test, not improvisation. Every environment
(stage, preprod, prod) of a repository has a deploy target: a provider, its
variables, a health URL and a rollback policy. Each provider has a template: the
workflow to write, the secrets it needs, the smoke check and the rollback.
Workflow
- A "Set up
<env>deploy" task already carries the rendered recipe in its description — start from that rather than asking the tools for it again. get_deploy_targetwith the repository id and env to re-read what this repo ships to, plus the recipe rendered with its variables, whenever you need it again mid-task.load_deploy_templatefor the full raw recipe (secrets, smoke check, rollback) when the rendered version in the task description is not enough, or the task gives no recipe (a change to an existing deploy rather than a new one) —list_deploy_templates, optionally filtered by repo kind, to see what is available first.- Write the workflow into
.github/workflows/exactly as the recipe describes. Keep theworkflow_dispatchtrigger: the board dispatches deploys by workflow file. - Name the file and the workflow's
name:per ci-cd-pipeline-authoring so the detector maps it to the right slot (stage_deploy/preprod_deploy/prod_deploy). If the slot still shows unmapped after that, say so in one comment: mapping the detected slot is the human's action, not something you can force from here.
Non-negotiables
- A deploy must verify itself. A green deploy step that never checked the service is a lie. Every deploy ends with a smoke check against the environment's health URL.
- A deploy must be reversible. Include the rollback step from the recipe (
if: failure()). If a provider cannot roll back automatically, document the exact manual command. - Wait for the rollout.
kubectl rollout status,aws ecs wait services-stableand their equivalents are what make the result honest; dropping them for speed hides crash-looping releases. - No secrets in the workflow. Use OIDC/Workload Identity Federation and repository secrets. Never commit a key file.
- Concurrency guard. One deploy per environment at a time (
concurrency.group), otherwise two releases race and the environment ends up in an undefined state. - If a required variable is missing (the rendered recipe shows
{{key — SET THIS}}), ask for it. Do not guess a project id, region or cluster name.
04 同仓库更多 Skills
visual-craft
暂无简介
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
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
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.
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
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