[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CS6Z4AC2VYY2EX3X8P39KD":3,"skill-same:01M7CS6Z4AC2VYY2EX3X8P39KD":48},{"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":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CS6Z4AC2VYY2EX3X8P39KD","ci-cd-pipeline-authoring",null,"Use when a repository needs CI\u002FCD - author GitHub Actions workflows so TaskTrooper's pipeline auto-detects your validate\u002Fbuild\u002Ftest jobs and stage\u002Fpreprod\u002Fprod deploys, and so a dispatch delivery profile can dispatch the production deploy","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\u002Fmobile-developer\u002Fskills\u002Fci-cd-pipeline-authoring\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ci-cd-pipeline-authoring\ncategory: ci-cd\ndescription: Use when a repository needs CI\u002FCD - author GitHub Actions workflows so TaskTrooper's pipeline auto-detects your validate\u002Fbuild\u002Ftest jobs and stage\u002Fpreprod\u002Fprod deploys, and so a dispatch delivery profile can dispatch the production deploy\n---\n# CI\u002FCD Pipeline Authoring\n\n## Overview\n\nTaskTrooper does not run your build — it **reads your GitHub Actions workflows** and maps their jobs and files onto its own pipeline. A task entering `code_review` waits for your `validate`\u002F`build`\u002F`test` jobs on its pull request (`get_pipeline_status` shows them); once a component's delivery profile is `dispatch`, the release engineer dispatches your production deploy workflow at the release tag after the merge. If your workflows are not named the way the detector expects, the pipeline silently skips them and the task stalls at that gate.\n\n**Core principle:** The workflow you author is the contract with the platform. Name jobs and files with the keywords the detector matches, or the stage does not exist as far as TaskTrooper is concerned.\n\n## Two kinds of pipeline slot\n\n**Status slots** (mapped to a *job name* in any workflow) — read for pass\u002Ffail on the PR at `code_review`:\n\n| Slot | Job name must contain (by repo kind) |\n|------|--------------------------------------|\n| `validate` | `lint`, `vet`, `staticcheck` (backend\u002Fworker) · `lint`, `tsc`, `typecheck` (frontend) · `lint`, `swiftlint`, `analyze` (mobile) |\n| `build` | `build`, `compile`, `docker` (backend\u002Fworker\u002Ffrontend) · `build`, `xcodebuild`, `archive`, `fastlane` (mobile) |\n| `test` | `test`, `vitest`, `jest` |\n\nA mobile `build` job must **not** contain `docker` (excluded). Give each job a clear `name:` — the detector matches the job's display name.\n\n**Deploy slots** (mapped to a *workflow file*) — dispatched, one workflow file per slot:\n\n| Slot | Workflow `name:` \u002F file must contain |\n|------|--------------------------------------|\n| `stage_deploy` | `stage`, `staging`, `preview` |\n| `preprod_deploy` | `preprod`, `pre-prod`, `pre-production` |\n| `prod_deploy` | `prod`, `production`, `release` (must NOT contain `preprod`) |\n\n## Rules\n\n- **CI** lives in one workflow `\u003Cid>-ci.yml` with jobs named `validate`\u002F`lint`, `build`, `test`. **Deploy** lives in separate files, one per environment: `\u003Cid>-deploy-stage.yml`, `\u003Cid>-deploy-preprod.yml`, `\u003Cid>-deploy-prod.yml`.\n- **A `dispatch` delivery profile's deploy workflow declares `on: workflow_dispatch` with no required inputs.** The platform dispatches with the branch ref only — it passes no inputs, so a workflow that requires one can never be released this way. Bake the environment into the file; read config from repo\u002Fenvironment **vars**, not inputs.\n- **An `on_merge` delivery profile deploys on push to the default branch, on purpose.** `push: { branches: [main] }` on the stage (or the component's only) deploy is correct there — the merge itself deploying is the whole point of that mode, and the release engineer watches, verifies and rolls back rather than dispatching. Preprod\u002Fprod still default to dispatch-only (`workflow_dispatch`) so a human\u002FQA gate controls them, unless the component is explicitly `on_merge` end to end.\n- **Authenticate with GitHub OIDC**, never long-lived cloud keys. GCP → Workload Identity Federation; AWS → an IAM role via `aws-actions\u002Fconfigure-aws-credentials`. The job needs `permissions: { id-token: write, contents: read }`.\n- **Config in vars, secrets only for true secrets.** Project id, region, service name, image repo → repo\u002Fenvironment `vars`. With OIDC there are usually no cloud secrets at all. Never commit a service-account JSON or access key.\n- Deploy job ends with a **health-check \u002F smoke step** that fails the job on a bad deploy. This is a build-time gate, not the release verdict: the release engineer's post-deploy verification is what actually decides `released` vs a rollback.\n- Pin third-party actions to their current major (or a commit SHA) — check `gh api repos\u002F\u003Cowner>\u002F\u003Caction>\u002Freleases\u002Flatest` rather than trusting a cached version number; `actions\u002Fcheckout@v7` is current as of this writing, not `@v5`.\n- Don't author deploy YAML from scratch: `search_boilerplate_catalog` for `deploy \u003Ccloud> \u003Ctype>` (e.g. `deploy gcp backend`), copy that folder's workflow templates, and rename them to `\u003Cid>-deploy-\u003Cenv>.yml`.\n\n## Batch release workflows (a `batch` delivery profile: desktop, mobile, and anything else a human cuts by hand)\n\nA `batch` component never dispatches a workflow — cutting the release creates a tag (or, for a `local` executor, runs a command on the release machine). Author the deploy side of a `batch` component's pipeline around that:\n\n- **`github_actions` executor** — the release\u002Fpublish workflow triggers on the tag push itself, not on a branch push or `workflow_dispatch`: `on: { push: { tags: ['v*'] } }` (match the component's delivery profile `tag_pattern`, `v*` for the default `v{version}`). Read the version being released from `GITHUB_REF_NAME` (the tag TaskTrooper just pushed) — never from a version file or a bump commit, because cutting a batch release never touches one. **The workflow must not create its own tag or version** (no `semantic-release`, `changesets`, `release-please` step): TaskTrooper pushes the tag that triggers this workflow, and a tool that tries to push a pre-existing tag of its own fails the release.\n- **`local` executor** — there is no workflow to author; the command configured on the delivery profile runs directly on this machine in a detached worktree of the cut commit. It receives `RELEASE_VERSION`, `RELEASE_TAG`, and `RELEASE_COMMIT` in its environment — read the version from there, the same way a tag-triggered workflow reads `GITHUB_REF_NAME`.\n- **`store` executor** — see the mobile developer's app-store-deploy skill; there is no workflow either, the store build is started directly.\n\n## Worked Example\n\n`on:` block a `dispatch` deploy workflow needs so the platform can dispatch it:\n\n```yaml\nname: myapi-deploy-prod          # \"prod\" → prod_deploy slot\non:\n  workflow_dispatch: {}          # platform dispatches with ref only, no inputs\npermissions:\n  id-token: write                # OIDC\n  contents: read\njobs:\n  deploy:\n    runs-on: ubuntu-latest\n    environment: production       # env-scoped vars\u002Fsecrets + protection rules\n    steps:\n      - uses: actions\u002Fcheckout@v7\n      # auth via OIDC (WIF \u002F configure-aws-credentials), then deploy the image,\n      # then a smoke step that curls the health endpoint and fails on non-200.\n```\n\nBecause the file name and `name:` contain `prod`, the detector maps this workflow to the component's `prod_deploy` check — the file name a `dispatch` delivery profile names as its `workflow`. The release engineer dispatches it at the release tag (`release\u002F\u003Csha12>`) after the merge, then verifies the deploy (health, smoke checks, runtime errors) before finishing or rolling back.\n\n## Common Mistakes\n\n- A `dispatch`-profile deploy workflow with `on: push` only and no `workflow_dispatch` → it can never be dispatched; either switch the component to `on_merge`, or add `workflow_dispatch`.\n- A `workflow_dispatch` with a `required: true` input → dispatch fails (platform sends no inputs).\n- One `deploy.yml` for all envs → the detector can only map one workflow per slot; you lose stage\u002Fpreprod separation. Split per env.\n- A prod workflow named `deploy-preprod-and-prod` → `preprod` substring rules it out of the prod slot.\n- A batch release workflow that bumps its own version or pushes its own tag → collides with the tag TaskTrooper already pushed.\n- Committing cloud keys instead of using OIDC.\n\n## Red Flags\n\n- Job names like `job1`\u002F`step` that contain none of the detector keywords → the slot stays empty and the pipeline gate never sees it.\n- Deploy that reports success even when the health check failed.\n- Secrets that could be vars sitting in `secrets:`.\n","# CI\u002FCD Pipeline Authoring\n\n## Overview\n\nTaskTrooper does not run your build — it **reads your GitHub Actions workflows** and maps their jobs and files onto its own pipeline. A task entering `code_review` waits for your `validate`\u002F`build`\u002F`test` jobs on its pull request (`get_pipeline_status` shows them); once a component's delivery profile is `dispatch`, the release engineer dispatches your production deploy workflow at the release tag after the merge. If your workflows are not named the way the detector expects, the pipeline silently skips them and the task stalls at that gate.\n\n**Core principle:** The workflow you author is the contract with the platform. Name jobs and files with the keywords the detector matches, or the stage does not exist as far as TaskTrooper is concerned.\n\n## Two kinds of pipeline slot\n\n**Status slots** (mapped to a *job name* in any workflow) — read for pass\u002Ffail on the PR at `code_review`:\n\n| Slot | Job name must contain (by repo kind) |\n|------|--------------------------------------|\n| `validate` | `lint`, `vet`, `staticcheck` (backend\u002Fworker) · `lint`, `tsc`, `typecheck` (frontend) · `lint`, `swiftlint`, `analyze` (mobile) |\n| `build` | `build`, `compile`, `docker` (backend\u002Fworker\u002Ffrontend) · `build`, `xcodebuild`, `archive`, `fastlane` (mobile) |\n| `test` | `test`, `vitest`, `jest` |\n\nA mobile `build` job must **not** contain `docker` (excluded). Give each job a clear `name:` — the detector matches the job's display name.\n\n**Deploy slots** (mapped to a *workflow file*) — dispatched, one workflow file per slot:\n\n| Slot | Workflow `name:` \u002F file must contain |\n|------|--------------------------------------|\n| `stage_deploy` | `stage`, `staging`, `preview` |\n| `preprod_deploy` | `preprod`, `pre-prod`, `pre-production` |\n| `prod_deploy` | `prod`, `production`, `release` (must NOT contain `preprod`) |\n\n## Rules\n\n- **CI** lives in one workflow `\u003Cid>-ci.yml` with jobs named `validate`\u002F`lint`, `build`, `test`. **Deploy** lives in separate files, one per environment: `\u003Cid>-deploy-stage.yml`, `\u003Cid>-deploy-preprod.yml`, `\u003Cid>-deploy-prod.yml`.\n- **A `dispatch` delivery profile's deploy workflow declares `on: workflow_dispatch` with no required inputs.** The platform dispatches with the branch ref only — it passes no inputs, so a workflow that requires one can never be released this way. Bake the environment into the file; read config from repo\u002Fenvironment **vars**, not inputs.\n- **An `on_merge` delivery profile deploys on push to the default branch, on purpose.** `push: { branches: [main] }` on the stage (or the component's only) deploy is correct there — the merge itself deploying is the whole point of that mode, and the release engineer watches, verifies and rolls back rather than dispatching. Preprod\u002Fprod still default to dispatch-only (`workflow_dispatch`) so a human\u002FQA gate controls them, unless the component is explicitly `on_merge` end to end.\n- **Authenticate with GitHub OIDC**, never long-lived cloud keys. GCP → Workload Identity Federation; AWS → an IAM role via `aws-actions\u002Fconfigure-aws-credentials`. The job needs `permissions: { id-token: write, contents: read }`.\n- **Config in vars, secrets only for true secrets.** Project id, region, service name, image repo → repo\u002Fenvironment `vars`. With OIDC there are usually no cloud secrets at all. Never commit a service-account JSON or access key.\n- Deploy job ends with a **health-check \u002F smoke step** that fails the job on a bad deploy. This is a build-time gate, not the release verdict: the release engineer's post-deploy verification is what actually decides `released` vs a rollback.\n- Pin third-party actions to their current major (or a commit SHA) — check `gh api repos\u002F\u003Cowner>\u002F\u003Caction>\u002Freleases\u002Flatest` rather than trusting a cached version number; `actions\u002Fcheckout@v7` is current as of this writing, not `@v5`.\n- Don't author deploy YAML from scratch: `search_boilerplate_catalog` for `deploy \u003Ccloud> \u003Ctype>` (e.g. `deploy gcp backend`), copy that folder's workflow templates, and rename them to `\u003Cid>-deploy-\u003Cenv>.yml`.\n\n## Batch release workflows (a `batch` delivery profile: desktop, mobile, and anything else a human cuts by hand)\n\nA `batch` component never dispatches a workflow — cutting the release creates a tag (or, for a `local` executor, runs a command on the release machine). Author the deploy side of a `batch` component's pipeline around that:\n\n- **`github_actions` executor** — the release\u002Fpublish workflow triggers on the tag push itself, not on a branch push or `workflow_dispatch`: `on: { push: { tags: ['v*'] } }` (match the component's delivery profile `tag_pattern`, `v*` for the default `v{version}`). Read the version being released from `GITHUB_REF_NAME` (the tag TaskTrooper just pushed) — never from a version file or a bump commit, because cutting a batch release never touches one. **The workflow must not create its own tag or version** (no `semantic-release`, `changesets`, `release-please` step): TaskTrooper pushes the tag that triggers this workflow, and a tool that tries to push a pre-existing tag of its own fails the release.\n- **`local` executor** — there is no workflow to author; the command configured on the delivery profile runs directly on this machine in a detached worktree of the cut commit. It receives `RELEASE_VERSION`, `RELEASE_TAG`, and `RELEASE_COMMIT` in its environment — read the version from there, the same way a tag-triggered workflow reads `GITHUB_REF_NAME`.\n- **`store` executor** — see the mobile developer's app-store-deploy skill; there is no workflow either, the store build is started directly.\n\n## Worked Example\n\n`on:` block a `dispatch` deploy workflow needs so the platform can dispatch it:\n\n```yaml\nname: myapi-deploy-prod          # \"prod\" → prod_deploy slot\non:\n  workflow_dispatch: {}          # platform dispatches with ref only, no inputs\npermissions:\n  id-token: write                # OIDC\n  contents: read\njobs:\n  deploy:\n    runs-on: ubuntu-latest\n    environment: production       # env-scoped vars\u002Fsecrets + protection rules\n    steps:\n      - uses: actions\u002Fcheckout@v7\n      # auth via OIDC (WIF \u002F configure-aws-credentials), then deploy the image,\n      # then a smoke step that curls the health endpoint and fails on non-200.\n```\n\nBecause the file name and `name:` contain `prod`, the detector maps this workflow to the component's `prod_deploy` check — the file name a `dispatch` delivery profile names as its `workflow`. The release engineer dispatches it at the release tag (`release\u002F\u003Csha12>`) after the merge, then verifies the deploy (health, smoke checks, runtime errors) before finishing or rolling back.\n\n## Common Mistakes\n\n- A `dispatch`-profile deploy workflow with `on: push` only and no `workflow_dispatch` → it can never be dispatched; either switch the component to `on_merge`, or add `workflow_dispatch`.\n- A `workflow_dispatch` with a `required: true` input → dispatch fails (platform sends no inputs).\n- One `deploy.yml` for all envs → the detector can only map one workflow per slot; you lose stage\u002Fpreprod separation. Split per env.\n- A prod workflow named `deploy-preprod-and-prod` → `preprod` substring rules it out of the prod slot.\n- A batch release workflow that bumps its own version or pushes its own tag → collides with the tag TaskTrooper already pushed.\n- Committing cloud keys instead of using OIDC.\n\n## Red Flags\n\n- Job names like `job1`\u002F`step` that contain none of the detector keywords → the slot stays empty and the pipeline gate never sees it.\n- Deploy that reports success even when the health check failed.\n- Secrets that could be vars sitting in `secrets:`.\n",{"name":5,"category":24,"description":7},"ci-cd","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fmobile-developer\u002Fskills\u002Fci-cd-pipeline-authoring",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill ci-cd-pipeline-authoring",{"tool":40,"command":41},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill ci-cd-pipeline-authoring",{"tool":43,"command":44},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill ci-cd-pipeline-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fmobile-developer\u002Fskills\u002Fci-cd-pipeline-authoring\u002FSKILL.md",true,[],[49,55,62,69,76,83],{"skillNo":50,"name":51,"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":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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",[],[]]