GitHub Actions CI/CD Pipeline Generator

What it does

/ci-pipeline is a Cursor slash command. Type it in chat to run a saved workflow: GitHub Actions CI/CD Pipeline Generator.

Generates robust GitHub Actions workflows for continuous integration: parallel linting, type checks, unit tests, Playwright suites, and automated deploys.

Automated test runner, type check, linting, and production deployment scripts. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /ci-pipeline for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /ci-pipeline exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Engineering Kit. It is wired to the DevOps & Deployment Pro (devops-engineer) and Technical Lead & System Architect (tech-lead) agents. Required skills: GitHub Actions CI/CD Pipeline Automation; Multi-Stage Docker & Container Deployments.

When to use it

• Use when setting up continuous integration or automated release workflows.
• Use /ci-pipeline when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just wrote marketing copy.

When not to use it

• Do not run /ci-pipeline as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. Define GitHub Actions YAML workflow with Node.js matrix version testing
2. Configure dependency caching to accelerate CI pipeline execution
3. Set up test, lint, and build verification jobs with failure notifications
4. Configure production deployment triggers on main branch merges

Example usage

Type this in Cursor chat: /ci-pipeline Create GitHub Actions workflow for PR preview deployments and unit test matrix

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: .github/workflows/ci.yml
• Expected artifact: .github/workflows/deploy.yml

Best practices

• Keep the prompt specific. /ci-pipeline Create GitHub Actions workflow for PR preview deployments and unit test matrix is the shape: object, constraint, and outcome.
• Let the listed agents work in order: devops-engineer → tech-lead.
• Save outputs in the repo. Chat-only answers evaporate.
• Engineering commands should leave tests or an audit note, not only implementation files.

Common mistakes

• Typing /ci-pipeline with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the GitHub Actions CI/CD Pipeline Automation skill that the command depends on.