Ci cd pipelines

Skill shinzoxD/knackbox/skills/coding/ci-cd-pipelines

Design and review CI/CD pipelines for speed, safety, and clear failure signals. Use whenever the user edits GitHub Actions, GitLab CI, Jenkinsfiles, or asks how to structure tests, builds, caches, deploy gates, and rollbacks in continuous integration.From its SKILL.md

Install

npx -y skills add shinzoxD/knackbox --skill ci-cd-pipelines

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.8 KB, 301 tokens by cl100k_base, as published. Nobody here has run it

CI/CD Pipelines

Pipelines should be boring: deterministic, fast enough, and hard to bypass on the way to production.

Workflow

Map stages: lint → unit → build → integration → security → deploy → smoke.
Separate PR checks from release/deploy workflows.
Caching and parallelism without flaky races.
Secrets: OIDC/short-lived creds over long-lived keys when possible.
Deploy strategy: gated environments, approvals, progressive delivery.
Failure UX: clear logs, annotations, and ownership.

Output format

## Pipeline design: <repo>

### Stages
| Stage | Trigger | Required? | Notes |

### Critical conf
…

### Risks
…

### Example workflow sketch

Rules

Required checks must be actually required in branch protection.
Do not print secrets; mask and minimize permissions (permissions: blocks).
Prefer immutable artifacts promoted across envs over rebuild-per-env.
Flaky tests belong in quarantine with owners — not silent retries forever.
Deploy from main/trunk or tagged releases, not arbitrary forks, without review.
Pin actions/images by version digest when security-sensitive.

Edge cases

Monorepo: path filters; avoid full-build on docs-only.
Mobile/native: signing secrets and build machine constraints.
Infra pipelines: plan on PR, apply on merge with protections.

What ships with it: 1 file

1.4 KB alongside SKILL.md

benchmarks/

prompts.json1.4 KB