KiloClawPowered by OpenClaw

Back to Cookbook

CI/CD Pipeline YAML Scaffolding Tool

aka “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.

House RecipeWork2 min

Try in KiloClawFree 7-day trial

INGREDIENTS

🐙GitHub

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

Tags:#ci-cd#automation#devops#pipelines

Related Recipes

Pipeline Paramedic

Stop the push-and-pray CI debugging loop

Paste your failing pipeline config and the error log. Your Claw spots YAML mistakes, platform-specific gotchas, and likely root causes before you burn another CI run.

Pipeline Paramedic

Stop guessing why your CI failed — get a diagnosis in seconds

Paste a failed CI log and get a root cause analysis, not a wall of red text. Catches the usual suspects — dependency resolution failures, flaky test patterns, Docker layer cache misses, permission errors, and timeout issues — then tells you exactly what to fix and where.

CLAWBITE AI

Local-first AI assistant that automates small daily tasks safely on your device

A personal, local-first AI assistant that automates small daily tasks—organizing files, setting reminders, and monitoring system events—without touching sensitive data or taking risky actions without your approval.

Bulk Change Airbnb Rates

Update pricing across all your Airbnb listings without clicking through each one

Automate bulk rate changes across multiple Airbnb listings using your Claw. Useful for seasonal pricing updates, last-minute discounts, or syncing rates after a change in your hosting strategy.