ci-pipelineslisted
Install: claude install-skill rustcircle/c101
# CI pipelines
Pipeline engineering: speed, reliability, reuse. The security checklist for CI (template injection,
`pull_request_target`, runner trust, supply chain) lives in `security-review` section 8; review lines
live in `code-review-checklist`. This skill keeps a short hardening summary (section 8) and points there.
Action versions below were current in October 2026; let Renovate or pinact move them, do not hand-edit.
Deep material:
[GitHub Actions recipes and the full worked-example workflow](references/github-actions-recipes.md) |
[GitLab CI mapping and equivalent pipeline](references/gitlab-ci.md)
## 1. Stage order and budgets
Cheapest and most likely to fail first. Each stage has a wall-clock budget; a stage over budget is a bug.
| # | Stage | Typical tools | Budget (PR) | Runs on |
|---|---|---|---|---|
| 1 | Format and lint | ruff, eslint/biome, shellcheck, actionlint, zizmor | < 1 min | every PR |
| 2 | Type-check | mypy/pyright, tsc --noEmit, cargo check | < 2 min | every PR |
| 3 | Unit tests | pytest, vitest, go test, nextest | < 5 min per shard | every PR |
| 4 | Build | package, binary, image (no push on PRs) | < 3 min cached | every PR |
| 5 | Integration | Testcontainers, compose services | < 8 min per shard | PR when paths match, merge queue |
| 6 | E2E / deploy | Playwright, smoke tests, deploy to staging | < 15 min | merge queue / main |
Rules:
- PR feedback target: p50 wall clock under 10 minutes from push to all required checks green.
- Serialize