Agent skill · software engineering · sickn33
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Why this skill is useful
Adds executable CI/CD pipeline scripts and automation strategies that enhance deployment capabilities beyond standard practices.
What it needs
Requires node, npm, postgres installed locally. About 7k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
CI/CD and Automation Overview Automate quality gates so that no change reaches production without passing tests, lint, type checking, and build. CI/CD is the enforcement mechanism for every other skill — it catches what humans and agents miss, and it does so consistently on every single change. Shift Left: Catch problems as early in the pipeline as possible. A bug caught in linting costs minutes; the same bug caught in production costs hours. Move checks upstream — static analysis before tests, tests before staging, staging before production. Faster is Safer: Smaller batches and more frequent releases reduce risk, not increase it. A deployment with 3 changes is easier to debug than one with 30. Frequent releases build confidence in the release process itself. When to Use Setting up a new project's CI pipeline Adding or modifying automated checks Configuring deployment pipelines When a change should trigger automated verification Debugging CI failures The Quality Gate Pipeline Every change goes through these gates before merge: No gate can be skipped. If lint fails, fix lint — don't disable the rule. If a test fails, fix the code — don't skip the test. Execution boundary These are separate templates for a project with the named scripts and locked CLIs already installed. Pin reviewed action revisions and use least-privilege permissions. Production and preview jobs need their own authorized identity, target and environment protections; untrusted PRs must not receive deployment secrets. Verify artifact transfer and recovery scope before applying. Auto-merge is optional and must follow the repository’s actual maintainer policy. GitHub Actions Configuration Basic CI Pipeline With Database Integration Tests Note: Even for CI-only test databases, use GitHub Secrets for credentials rather than hardcoding values. This builds good habits and prevents accidental reuse of test credentials in other contexts. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/ci-cd-and-automation--43354c