cicd-pipeline-designlisted

Designs, scaffolds, and audits a repository's CI/CD pipeline against spec/project/continuous-integration/ (pre-merge stage sequence, reproducible inputs, cache discipline, local↔CI parity), spec/project/continuous-delivery/ (artifact immutability, provenance, the artifact-to-securing-stage matrix, rollback, the handover boundary to deployment), and spec/project/github-actions-best-practices/ (digest pinning, least-privilege permissions, untrusted input, short-lived credentials, reusable-workflow reuse, concurrency, caching). Writes and patches workflow files in the target repository. Invoke when the user asks to design, set up, rework, harden, or audit a CI/CD pipeline or GitHub Actions workflows; also German. Don't use to triage a red run (`workflow-health-triage`), run the gate (`quality-gate`), or publish a release (`release-publish-trigger`). Supports resume on re-invocation per `spec/claude/resumable-work/`.
nolte/claude-shared · ★ 0 · DevOps & Infrastructure · score 74

Install: claude install-skill nolte/claude-shared

# CI/CD Pipeline Design Operationalizes three specs into one working pipeline: `spec/project/continuous-integration/` (the pre-merge half), `spec/project/continuous-delivery/` (the post-merge half), and `spec/project/github-actions-best-practices/` (the single concrete platform binding). The specs declare the discipline; this skill applies it to a specific repository and writes the result. ## Why this is a skill, not an agent - **It writes.** Designing a pipeline ends in workflow files on disk. An agent returns a report and forgets; the deliverable here is a diff. - **It's a multi-step dialogue.** Stage selection depends on the project type, the artifact classes it ships, and which stages the operator wants required versus advisory. Those are decisions to take with the operator, not to infer. - **It has a read-only companion.** The detection half is genuinely isolated and parallel, so it lives in the `cicd-pipeline-reviewer` agent, which this skill dispatches for the `audit` operation. Skill writes, agent detects—the same split as `dockerfile-audit` and its scanner. ## User-language policy Detect the user's language and conduct the dialogue in it. Workflow files, comments inside them, and commit messages stay English per the repository's authoring rules, regardless of conversation language. ## German trigger phrases The frontmatter `description` keeps its trigger lexicon English-only per `spec/claude/skill-management/` §Structure. Treat these as equivalent: - "entwirf