CI Scaffolder
Generate CI/CD pipelines from "I have a Node app that deploys to K8s" instead of copy-pasting from Stack Overflow
Generates complete CI/CD pipeline configs (GitHub Actions, GitLab CI, CircleCI) from a description of your project. Includes build, test, security scan, and deploy stages with proper caching, secrets handling, and environment promotion.
INGREDIENTS
PROMPT
Create a skill called "CI Scaffolder". Generate CI/CD pipeline configurations from project descriptions: When I describe my project (language, test framework, build system, deploy target), generate a complete pipeline for my CI platform: Stages: 1. Lint (language-appropriate: eslint, ruff, golangci-lint, etc.) 2. Test (with proper caching and parallel test splitting if possible) 3. Security scan (trivy for containers, npm audit/pip-audit for dependencies) 4. Build (Docker build with multi-stage, or native build) 5. Deploy to staging (with smoke tests) 6. Deploy to production (manual approval gate) Include: - Proper dependency and Docker layer caching - Secret references (not values) for credentials - Path filters to skip when only docs/configs change - Concurrency groups to cancel redundant runs - Branch protection suggestions - Status checks configuration Support GitHub Actions, GitLab CI, and CircleCI formats.
How It Works
Every project needs a CI/CD pipeline, and every engineer wastes hours
piecing one together from documentation and Stack Overflow. This skill
generates a complete, production-grade pipeline from your project description.
What You Get
- Complete pipeline config for your CI platform (GitHub Actions, GitLab CI, CircleCI)
- Stages: lint, test, build, security scan, deploy (with environment promotion)
- Proper dependency caching for your language/runtime
- Secret handling best practices (no secrets in logs, proper masking)
- Docker build and push with multi-stage optimization
- Kubernetes deployment (or your preferred deploy target)
- Conditional stages (skip deploy on PRs, run security scan on main only)
Setup Steps
- Describe your project: language, runtime, test framework, deploy target
- Specify your CI platform (GitHub Actions, GitLab CI, etc.)
- Review the generated pipeline config
- Customize secrets, environments, and triggers as needed
Tips
- Always include a lint and security scan stage — catch issues before they reach review
- Use path filters to skip the pipeline when only docs change
- Cache dependencies aggressively — it's the biggest speed win
- Use concurrency groups to cancel redundant runs
- Add status checks as required on your main branch to enforce the pipeline