agentsclimarketplace

Ci cd pipelines

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

Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.

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.

2 things to look at

  • 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 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 author says it does

Copied from the file, not written here

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.

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

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

Output format

## Pipeline design: <repo>

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

### Critical conf
…

### Risks
…

### Example workflow sketch

Rules

  1. Required checks must be actually required in branch protection.
  2. Do not print secrets; mask and minimize permissions (permissions: blocks).
  3. Prefer immutable artifacts promoted across envs over rebuild-per-env.
  4. Flaky tests belong in quarantine with owners — not silent retries forever.
  5. Deploy from main/trunk or tagged releases, not arbitrary forks, without review.
  6. 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.

Gives 0 of the 12 instructions most ci cd skills give in 301 tokens

Counted across 392 of the 394 authors here whose files we hold, read 2026-08-06

  • pin third-party actions to full commit SHAsin 33 of 392
  • cache dependencies appropriatelyin 24 of 392, across 12 files
  • optimize pipelines exceeding ten minutesin 20 of 392, across 6 files
  • enforce all quality gates before mergein 20 of 392, across 7 files
  • Configure branch protection rulesin 19 of 392, across 5 files
  • use environments for deployment trackingin 19 of 392, across 7 files
  • implement manual gates for productionin 19 of 392, across 7 files
  • implement security scanningin 18 of 392, across 5 files
  • fix failing code instead of disabling checksin 18 of 392, across 4 files
  • use CI/CD variables for secretsin 18 of 392, across 6 files
  • move checks upstream in the pipelinein 17 of 392, across 3 files
  • use specific image tagsin 17 of 392, across 5 files

Said here and by no other author read

  • Map pipeline stages from lint to smoke
  • Minimize permissions
  • Prefer immutable artifacts promoted across environments
  • Deploy from main trunk or tagged releases
  • Pin actions by version digest when security-sensitive
  • Use path filters for monorepos

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.