ci-cd-pipelines
Skill216 starsChanged 6 months agoMITView on GitHub
Automated quality gates from commit to production. Every merge to main is potentially shippable. No manual steps in the deployment path.
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
All gates must pass before merge is allowed:
- Distinctive: line 39
Every step is automated — no manual "click to deploy."
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Overview
CI/CD is the automation layer that enforces quality gates consistently, without relying on human memory or discipline. When CI is green, you know the code is tested, linted, and deployable. When it's red, nothing ships.
When to Use
- Setting up a new project
- Adding a new quality gate
- Reviewing CI/CD pipeline configuration
Process
Step 1: CI Gates (Every PR)
- All gates must pass before merge is allowed:
- Lint: code style and static analysis
- Unit tests: all pass
- Integration tests: key boundaries covered
- Security scan: SAST, dependency vulnerabilities
- Build: production artifact builds successfully
- Gates run in parallel where possible (speed matters).
- Maximum CI time: 10 minutes. If slower, optimize.
Verify: Merging is blocked when any gate fails.
Step 2: CD Pipeline (Every Main Merge)
- Main branch is always deployable.
- Deployment pipeline:
- Deploy to staging → run smoke tests → deploy to production (canary) → full rollout
- Every step is automated — no manual "click to deploy."
- Rollback is automated and tested.
Verify: A push to main triggers automated deployment with no human intervention required.
Step 3: Feature Flags Over Feature Branches
- Incomplete features go behind feature flags — not long-lived branches.
- Feature flags allow dark launching, A/B testing, and instant rollback without redeployment.
- Feature flag state is tracked in a dashboard.
Verify: New features are behind flags. No feature branches > 2 days old.
Step 4: Pipeline as Code
- CI/CD config is in the repo (
.github/workflows/,.gitlab-ci.yml, etc.). - Pipeline changes go through code review like any other change.
- Pipeline config is tested: changes to CI don't break CI.
Verify: CI config is in the repo and reviewed.
Common Rationalizations (and Rebuttals)
| Excuse | Rebuttal |
| "It's a small change, CI is optional" | Every "small change" that skipped CI is in the origin story of a major incident. |
| "Manual deployment gives us control" | Manual steps introduce human error. Automation gives you control. |
| "CI is too slow" | Optimize it. Don't skip it. |
Verification
- All quality gates run on every PR
- Merge blocked when any gate fails
- Main → production deployment is fully automated
- Rollback is automated and tested
- Feature flags in place for incomplete features
References
- production-deployment skill
- git-workflow skill
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- harrissohail6/claude-code-config★ 1same name
- KMaruthi2002/universal-llm-skills★ 1same name
- medy-gribkov/arcana★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-qa-run-reviewSkill
- ai-output-validationSkill
- api-designSkill
- citruscoastaiSkill
- code-explanationSkill
- code-reviewSkill
- context-loadingSkill
- debugging-methodologySkill
- documentationSkill
- error-handlingSkill
- frontend-engineeringSkill
- git-workflowSkill
- goal-driven-executionSkill
- hallucination-preventionSkill
- idea-to-specSkill
- incremental-codingSkill
- integration-testingSkill
- meeting-notes-to-tasksSkill
- multi-agent-orchestrationSkill
- observabilitySkill
- performance-optimizationSkill
- production-deploymentSkill
- prompt-injection-defenseSkill
- rag-and-memorySkill
- refactoringSkill
- research-and-summarizeSkill
- security-hardeningSkill
- simplicity-firstSkill
- surgical-changesSkill
- task-decompositionSkill
- test-driven-developmentSkill
- think-before-codingSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.