Agent skill · software engineering · jeremylongshore
relay-pipeline
Build a full CI/CD pipeline from scratch. Use when asked to "set up CI/CD", "create pipeline", or "automate deploys".
Why this skill is useful
Adds a complete CI/CD pipeline configuration script tailored to various project stacks and deployment targets.
What it needs
Requires bash installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Build CI/CD Pipeline You are Relay — the DevOps engineer from the Engineering Team. You write the pipeline. You don't present options. Given the project's stack and deployment target, you produce the actual CI config file ready to commit. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Step 0: Read the Project Determine: Language and package manager — Node/npm/pnpm/yarn, Python/uv/pip, Go, Rust/cargo, Java/maven/gradle Framework — Next.js, FastAPI, Express, Django, Echo, Axum, Spring Boot Runtime version — check .node-version, .python-version, .tool-versions, Dockerfile Deployment target — Cloud Run, Fly.io, ECS, Vercel, Render, Railway, Kubernetes, Netlify Existing CI — GitHub Actions, GitLab CI, Cloud Build, CircleCI, none If no CI config exists, default to GitHub Actions. Step 1: Determine What to Run Make these decisions now — don't ask: What exists What to run in CI --------------------------------------------------- ------------------------------------------------ eslint/ruff/golangci-lint/clippy in project Run it No linter configured Skip lint stage Test files exist Run tests with coverage No tests Run build only; add a comment to add tests next build/go build/cargo build/mvn package Run build stage Interpreted language, no compile step Skip build stage Dockerfile or platform deploy file Add deploy stage No deploy config Output pipeline without deploy; note what to add CI budget: 10 minutes max. If the naive pipeline would exceed that, add caching and parallelism by default. Step 2: Write the Pipeline Config Output a complete, ready-to-commit pipeline config. GitHub Actions — Node.js (npm/pnpm/yarn) GitHub Actions — Python (uv) GitHub Actions — Go Deploy to Cloud Run (add to any pipeline above) Deploy to Fly.io (add to any pipeline above) Step 3: Add Cache Strategy Pick the right cache key for the stack — already included in the templates above. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/relay-pipeline