| name | ci-cd-guardrails |
| description | Skill for building safer, faster, and more reliable delivery pipelines Use when this capability is needed. |
| metadata | {"author":"coozyme"} |
CI/CD Guardrails Skill
Guidelines for enforcing quality and safety gates in build, test, and deployment workflows.
When to Use This Skill
- When creating or hardening CI/CD pipelines
- When pull requests often break main branch
- When releases are frequent and rollback risk is high
- When flaky tests block developer productivity
Guardrail Layers
1. Pre-Merge Guardrails
- Require branch protection and at least one review
- Run mandatory checks: lint, unit tests, static analysis
- Require all checks to pass before merge
- Block force-push on protected branches
2. Build and Test Guardrails
- Use deterministic builds (lock files and pinned versions)
- Cache dependencies and build artifacts to reduce pipeline time
- Fail fast on formatting/lint errors before expensive steps
- Separate fast checks (PR) from full checks (main/nightly)
3. Deployment Guardrails
- Use progressive delivery (canary/rolling/blue-green)
- Add health-check gates before traffic switch
- Automate rollback when error budget or health checks fail
- Record deployment metadata (commit, actor, environment, timestamp)
Flaky Test Handling Protocol
- Detect flaky tests from historical failure patterns.
- Quarantine flaky tests with a tracking ticket.
- Keep quarantine list small and reviewed weekly.
- Fix root cause quickly (timing, shared state, test data race).
- Remove quarantine entry after stable runs.
Pipeline Quality Checklist
Useful Commands
npm ci
npm run lint
npm test
pip install -r requirements.txt
ruff check .
pytest
Output Expectations
When applying this skill, produce:
- Updated CI/CD workflow with explicit quality gates
- Rollback strategy and trigger conditions
- Short operational notes for on-call/deploy owners
Source: coozyme/agent-starter-kit — distributed by TomeVault.