CI/CD Pipeline Config Writer skill for Claude and Codex
A production-ready CI/CD pipeline file for your platform and stack, with the stages, triggers, caching, and environment separation you pick.
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
Use when a developer needs a CI/CD config file for a stated tool, stack, and deployment target. Do not use for debugging a failing pipeline or infrastructure provisioning. Related topics: devops, coding, pipeline.
What it will ask you for
- CI/CD tool (choose one: GitHub Actions, GitLab CI, CircleCI, Bitbucket Pipelines, Jenkins)
- Project type (choose one: Node.js or React, Python, Flutter, Docker container, Static site, Ruby on Rails, Go)
- Stages to include (choose any: Install dependencies, Lint, Unit tests, Integration tests, Build, Docker build and push, Deploy to staging, Deploy to production, Notify on Slack or Teams)
- Deployment platform (choose one: Firebase Hosting, AWS, GCP, Azure, Heroku, Vercel, DigitalOcean, Self-hosted)
- Environments (choose any: Development, Staging, Production)
- Triggers (choose any: Push to main, Pull request, Tag release, Manual trigger, Scheduled)
How it works
- Map the chosen stages to jobs and decide which can run in parallel and which must wait.
- Write the config in the chosen tool's syntax with dependency caching keyed on the lockfile.
- Add the trigger rules and restrict production deploys to main or a tag, with approval where supported.
- Reference secrets by name only and list each one the user must create.
- Add first-run setup steps, done when someone could commit the file and get a green run.
What you get
The complete pipeline file with per-job comments, a list of required secrets, and short first-run setup steps.
What it watches out for
- Allowing production deploys from pull request branches.
- Embedding tokens or keys in the file instead of referencing the secret store.
- Caching on a key that never changes, which serves stale dependencies.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.