Description
ci-cd-and-automation is an agent skill from Addy Osmani's agent-skills collection that helps set up and change build and deployment pipelines so that no change reaches production without passing automated quality gates. The gates are tests, lint, type checking and the build. The skill frames CI/CD as the enforcement mechanism for the other skills in the collection, because it catches what people and agents miss, on every change. It states two principles. The first is shift left: catch problems as early in the pipeline as possible, with static analysis before tests, tests before staging, and staging before production, since a bug caught in linting costs minutes while one caught in production costs hours. The second is that faster is safer: smaller batches and more frequent releases reduce risk, because a deployment with three changes is easier to debug than one with thirty. The skill applies when setting up a new project's CI, adding or changing automated checks, configuring deployment pipelines, when a change should trigger verification, and when CI failures need debugging. It suits teams who want a repeatable pipeline that every change goes through.…
Highlights
- Quality gates for tests, lint, types and build
- Shift-left checks in the pipeline
- Smaller, more frequent releases
- Setup and debugging of CI failures
Ratings & Reviews
No ratings yet
Be the first to rate ci-cd-and-automation.
People also visit
coding-agent
Delegate coding work to Codex, Claude Code, or OpenCode as background workers
gh-issues
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs
loop-me
Grill me about specs for the workflows I want to build, within this workspace
ci-cd-and-automation FAQ
What does the ci-cd-and-automation skill do?
It helps set up and change CI/CD pipelines and automated quality gates for tests, lint, type checking and builds.
How do I install it?
Run: npx skills add https://github.com/addyosmani/agent-skills --skill ci-cd-and-automation
What does 'shift left' mean here?
Moving checks earlier in the pipeline: static analysis before tests, tests before staging, and staging before production.
Why does it favor smaller releases?
The skill says a deployment with three changes is easier to debug than one with thirty, so frequent small releases reduce risk.
What security checks has it passed?
skills.sh lists three audits: Gen Agent Trust Hub Pass, Socket Pass and Snyk Pass.
What are the best ci-cd-and-automation alternatives?
Popular alternatives to ci-cd-and-automation include coding-agent, gh-issues and peekaboo. See all ci-cd-and-automation alternatives