devops-ci-architectlisted

Sets up GitHub Actions CI/CD for a project. Every stack gets the same standard pipeline: push a feat branch → a PR opens (auto-pr.yml) → CI runs build + test as the merge gate (ci.yml) → when CI is green the board moves to In-Test, and Shopify additionally deploys the app to the store (in-test.yml). (dev-story-implementer set the board to In-Progress at story start.) Stacks differ only in their build/test commands and their on-green deploy step. iOS also ships a manual TestFlight button. Stack-specific details live in templates/stacks/<id>/manifest.md — adding a project type is a drop-in directory, no skill-body edits. ALWAYS use this skill when the user asks to set up CI/CD, GitHub Actions, deploy/release automation, or a build pipeline. Triggers: "set up CI", "github actions kur", "ci/cd workflow", "release workflow", "shopify deploy", "ci kur". Output: .github/workflows/ (ci.yml + auto-pr.yml + in-test.yml + the stack's release/distribution workflow) + .github/scripts/set-project-status.sh + stack support
ahmetatar/product-pipeline-plugin · ★ 0 · DevOps & Infrastructure · score 72

Install: claude install-skill ahmetatar/product-pipeline-plugin

# DevOps CI Architect You set up GitHub Actions CI/CD for a project. The pipeline is the SAME for every stack; stacks only swap in their own build/test commands and their on-green deploy step. You never hardcode a stack — you read the project's `CI/CD target`, load that stack's manifest, and write the files it declares. Runs **once per project**. If the workflows already exist, you update them (Section 6). --- ## The standard pipeline (every stack) Ordered stages. Each row: what fires it → what runs → what it does → the board Status after it. `workflow_run` means the GitHub Actions event "a named workflow finished"; `feat/**` is the story branch glob. | # | Trigger | Runs | Action | Board after | |---|---|---|---|---| | 1 | story start (manual) | `dev-story-implementer` | mark In-Progress, code, commit `Closes #N`, push to `feat/**` | **In-Progress** | | 2 | push to `feat/**` | `auto-pr.yml` | open the PR if none exists | (unchanged) | | 3 | PR + push to `feat/**`/`main` | `ci.yml` | build + test — the required check; PR cannot merge until green | (unchanged) | | 4 | `workflow_run` of `ci.yml` = success on `feat/**` | `in-test.yml` | *(Shopify only: deploy the app version to the store first)*, then move the board | **In-Test** | | 5 | user accepts → runs `/story-done` (manual) | `/story-done` | verify CI green, squash-merge the PR, move the board | **Done** | | 6 | PR merged to `main` | `release.yml` | Shopify: release the version live · iOS: nothing (use `testflight.ym