Agent skill

Cicd Setup

by shawnpang in shawnpang/startup-founder-skills

When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI", "automate deployment", "add tests to pipeline", "fix my build".

MITAuto-check passedDevOps & Cloud

Install Cicd Setup

skills CLI
$ npx skills add shawnpang/startup-founder-skills --skill cicd-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install shawnpang/startup-founder-skills cicd-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cicd-setup .claude/skills/cicd-setup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cicd-setup
GitHub stars
341
Token cost
~1.7k tokens
SKILL.md length
636 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI", "automate deployment", "add tests to pipeline", "fix my build".

  • Works in 7 steps: Detect stack from repo signals — Scan… → Choose pipeline stages — Start with a… → Generate pipeline config — Write CI… → …
  • Needs to set up
  • SKILL.md covers When to Use, Context Required, Workflow and Output Format, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Cicd Setup is an agent skill from shawnpang/startup-founder-skills. When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI", "automate deployment", "add tests to pipeline", "fix my build".

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering CI/CD. It works with GitHub Actions and GitLab. The repository describes itself as: AI agent skills for tech startup founders — fundraising, sales, product, recruiting, engineering, legal, ops, and growth. Works with Claude Code, Cursor, Codex, and any Agent… The licence is MIT.

When your agent uses it

  • Needs to set up
  • Improve CI/CD pipelines — GitHub Actions
  • Deployment automation
  • Automate deployment

Example prompts

  • “set up CI”
  • “automate deployment”
  • “add tests to pipeline”
  • “/cicd-setup”

Requirements

  • Python 3
  • Node.js

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Detect stack from repo signals — Scan for lockfiles (package-lock.json, yarn.lock, poetry.lock, go.sum, Cargo.lock), language manifests…
  2. Choose pipeline stages — Start with a dependable baseline: checkout, runtime setup, dependency install with caching, then sequential lint…
  3. Generate pipeline config — Write CI config for the detected platform. Output machine-readable YAML with correct caching strategy for the…
  4. Configure secrets — List required secrets and how to add them. Use platform-managed secret stores. Recommend OIDC for cloud auth over…
  5. Add deployment stages safely — Begin CI-only (lint/test/build). Add staging deployment with explicit environment info. Add production…
  6. Validate before merge — Confirm generated YAML is syntactically valid, all commands exist in the project, caching aligns with the package…
  7. Deliver config and instructions — Full config file plus setup steps.

What it can do on your machine

Read from SKILL.md and the folder at commit 4ad31b4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cicd Setup loads about 1.7k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 636 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~51
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from shawnpang/startup-founder-skills at commit 4ad31b4, republished under its MIT licence (© shawnpang). 636 words, ~1,734 tokens.

Download SKILL.mdSave it as .claude/skills/cicd-setup/SKILL.md (or your agent's skills folder).
name
cicd-setup
description
When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI", "automate deployment", "add tests to pipeline", "fix my build".
related
code-review, security-review
reads
startup-context

CI/CD Setup

When to Use

  • Setting up CI for a new project from scratch
  • Replacing unreliable copied pipeline configurations that do not match the actual stack
  • Transitioning between GitHub Actions and GitLab CI platforms
  • Reviewing whether pipeline stages align with actual project tooling
  • Optimizing slow builds (caching, parallelism, conditional steps)
  • Establishing a stable CI foundation before adding specialized hardening

Context Required

From startup-context: tech stack, deployment target, team size. Also detect or ask:

  • Language and framework (auto-detect from repo files before asking)
  • Deployment target (Vercel, AWS, GCP, Fly.io, etc.)
  • CI/CD platform (default: GitHub Actions; also supports GitLab CI)
  • Environments (dev, staging, production) and existing test coverage
  • Secrets and credentials needed for build or deploy

Workflow

  1. Detect stack from repo signals — Scan for lockfiles (package-lock.json, yarn.lock, poetry.lock, go.sum, Cargo.lock), language manifests (package.json, pyproject.toml, go.mod), and script definitions (test, lint, build commands). Lockfiles indicate package manager choice. Absent scripts trigger conservative defaults. Never assume Node for a Python project.
  2. Choose pipeline stages — Start with a dependable baseline: checkout, runtime setup, dependency install with caching, then sequential lint, test, build. Only add complexity after the baseline works.
  3. Generate pipeline config — Write CI config for the detected platform. Output machine-readable YAML with correct caching strategy for the detected package manager. Verify all referenced commands actually exist in the project.
  4. Configure secrets — List required secrets and how to add them. Use platform-managed secret stores. Recommend OIDC for cloud auth over long-lived keys. Never hardcode credentials in YAML.
  5. Add deployment stages safely — Begin CI-only (lint/test/build). Add staging deployment with explicit environment info. Add production deployment with manual approval. Maintain transparency in rollout and rollback procedures.
  6. Validate before merge — Confirm generated YAML is syntactically valid, all commands exist in the project, caching aligns with the package manager, and branch protections match organizational requirements.
  7. Deliver config and instructions — Full config file plus setup steps.

Output Format

markdown
# CI/CD Pipeline: [Project Name]
## Stack Detection Results — detected language, runtime, tools, and build commands
## Pipeline Overview — Mermaid flowchart showing stages
## Pipeline Configuration — Full YAML config file
## Secrets Required — table: name, where to get, how to add
## Setup Instructions — step-by-step to activate
## Validation Checklist — commands verified, caching confirmed, branch rules set
## Optimization Notes — caching strategy, estimated build time

Frameworks & Best Practices

Detection-First Pipeline Generation

Always detect before generating. The detector relies on concrete file signals:

  • Lockfiles indicate package manager choice (npm, yarn, pip, cargo, go modules)
  • Language manifests identify runtime families
  • Script definitions in package.json/pyproject.toml inform lint/test/build commands
  • Absent scripts trigger conservative default commands rather than assumptions
Caching Strategies by Ecosystem
EcosystemCache PathCache Key
Node.js~/.npm or node_moduleshashFiles('**/package-lock.json')
Python~/.cache/piphashFiles('**/requirements*.txt')
Go~/go/pkg/modhashFiles('**/go.sum')
Rust~/.cargo/registry, target/hashFiles('**/Cargo.lock')
Rubyvendor/bundlehashFiles('**/Gemfile.lock')
Show full SKILL.md (245 more words)Show less
Pipeline Architecture Principles
  • Lint first — fail early before expensive test runs
  • Sequential baseline — checkout, install, lint, test, build, then artifact publish
  • Cache aggressively — cuts 30-60% off build times
  • Pin action versions — use SHA hashes, not tags, for supply chain security
  • Set timeouts (timeout-minutes: 15) and concurrency to cancel redundant runs
  • One enhancement at a time — do not add matrix builds, security scanning, and deployment in one PR
Environment Strategy
EnvironmentTriggerApprovalPurpose
CIEvery push/PRNoneRun lint + tests
StagingMerge to mainNone (auto)Integration testing, QA
ProductionGit tag or manualRequiredLive users
Common Pitfalls
  1. Applying Node-specific pipelines to Python or Go repos (detect first)
  2. Enabling deployment before establishing reliable test coverage
  3. Overlooking dependency caching configuration
  4. Running full matrix builds on minor branch updates (use path filters)
  5. Omitting branch protections on production deployments
  6. Embedding credentials directly in pipeline YAML
Scaling & Platform Notes
  • Split long-running jobs when execution exceeds 10 minutes
  • Implement test matrices only when genuine compatibility concerns exist
  • GitHub Actions for GitHub ecosystem; GitLab CI for self-hosted SCM+CI
  • Maintain a single canonical pipeline source per repository
  • code-review — chain to review the CI config itself before committing
  • security-review — chain to add or audit security scanning stages (trivy, semgrep, npm audit)

Examples

Example prompt: "Set up CI/CD for my Next.js app deployed on Vercel."

Good output snippet:

yaml
name: CI
on:
  push: { branches: [main] }
  pull_request: { branches: [main] }
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
jobs:
  lint:
    runs-on: ubuntu-latest
    timeout-minutes: 10
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: 20, cache: 'npm' }
      - run: npm ci
      - run: npm run lint && npx tsc --noEmit
  test:
    runs-on: ubuntu-latest
    timeout-minutes: 15
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: 20, cache: 'npm' }
      - run: npm ci && npm test -- --coverage

Example prompt: "My Python CI takes 8 minutes, how do I speed it up?"

Good output snippet:

Stack detection shows: Python 3.11, pytest, pip. Three fixes to cut to ~3 minutes:
(1) Add pip caching keyed on hashFiles('requirements*.txt'),
(2) split unit/integration tests into parallel jobs,
(3) add path filters to skip CI on docs-only changes.

© shawnpang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/cicd-setup of shawnpang/startup-founder-skills.

Open the folder on GitHubat commit 4ad31b4

Compare with similar skills

Cicd Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cicd Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cicd Setup this skillshawnpang/startup-founder-skills341—~1.7kAutomated safety check: PassMIT
Fingerprint CI Gateliarjsdev/liarjs-skills5181 repos~986Automated safety check: NotesMIT
Megalinter Checknvuillam/npm-groovy-lint2481 repos~3.9kAutomated safety check: NotesMIT
Migrate To TeamcityJetBrains/teamcity-cli125—~1.3kAutomated safety check: PassApache-2.0
CI CDEliasOulkadi/shokunin114—~3.4kAutomated safety check: NotesMIT
CI CDahmedasmar/devops-claude-skills203—~3.5kAutomated safety check: PassNone

Similar skills

  • Fingerprint CI Gate

    liarjsdev/liarjs-skills

    Gate a build on browser fingerprint regressions with liarjs - save a baseline scan as JSON, diff later runs against it, and fail the job when the consistency score falls below a floor.

    518 GitHub starsUsed in 1 repo~986 tokens
    DevOps & CloudAuto-check: notes
  • Megalinter Check

    nvuillam/npm-groovy-lint

    Collect MegaLinter lint errors for the current repository. An agent skill from nvuillam/npm-groovy-lint.

    248 GitHub starsUsed in 1 repo~3.9k tokens
    DevOps & CloudAuto-check: notes
  • Migrate To Teamcity

    JetBrains/teamcity-cli

    Official

    Migrating CI/CD pipelines to TeamCity. An agent skill from JetBrains/teamcity-cli.

    125 GitHub stars~1.3k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • CI CD

    EliasOulkadi/shokunin

    Design CI/CD pipelines for GitHub Actions, GitLab CI, and CircleCI with matrix builds, test sharding, caching, Docker layer caching, OIDC auth, deployment strategies (rolling, blue-green, canary)…

    114 GitHub stars~3.4k tokensUpdated 3 days ago
    DevOps & CloudAuto-check: notes
  • CI CD

    ahmedasmar/devops-claude-skills

    CI/CD pipeline design, optimization, DevSecOps security scanning, and troubleshooting.

    203 GitHub stars~3.5k tokensUpdated 6 mo ago
    DevOps & CloudAuto-check passed
  • Tirith Policies

    StackGuardian/tirith

    Write, validate, run and debug Tirith IaC governance policies, install Tirith, and add it to a CI pipeline (GitHub Actions, GitLab CI, Bitbucket Pipelines, Jenkins, Azure DevOps, CircleCI or any…

    170 GitHub stars~1.8k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from shawnpang/startup-founder-skills

All 50 skills in this repo
  • Contract Review

    shawnpang/startup-founder-skills

    When the user needs to review an existing contract, assess risk in proposed terms, or evaluate a contract before signing.

    341 GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed
  • Accelerator Application

    shawnpang/startup-founder-skills

    When the user wants to apply to startup accelerators, incubators, or fellowship programs.

    341 GitHub stars~2.7k tokensUpdated 6 mo ago
    Auto-check passed
  • Architecture Design

    shawnpang/startup-founder-skills

    When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure topology, database selection, or dependency analysis.

    341 GitHub stars~2.1k tokensUpdated 6 mo ago
    Auto-check passed
  • Board Update

    shawnpang/startup-founder-skills

    When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to stakeholders.

    341 GitHub stars~2.3k tokensUpdated 6 mo ago
    Auto-check passed
  • Churn Analysis

    shawnpang/startup-founder-skills

    When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores, design save plays, or create win-back campaigns.

    341 GitHub stars~2.3k tokensUpdated 6 mo ago
    Auto-check passed
  • Code Review

    shawnpang/startup-founder-skills

    When the user asks for a code review, shares code for feedback, or says "review this", "check my code", "what's wrong with this".

    341 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed

Categories

Questions about Cicd Setup

What does Cicd Setup do?

When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI", "automate deployment", "add tests to pipeline", "fix my build". Cicd Setup is an agent skill from shawnpang/startup-founder-skills. When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI", "automate deployment", "add tests to pipeline", "fix my build".

When should I use Cicd Setup?

Cicd Setup fits situations like: needs to set up; improve CI/CD pipelines — GitHub Actions; deployment automation; automate deployment.

How do I install Cicd Setup in Claude Code?

Run `npx skills add shawnpang/startup-founder-skills --skill cicd-setup -a claude-code`. Or copy the skill folder (skills/cicd-setup in shawnpang/startup-founder-skills) into .claude/skills/cicd-setup in your project. Claude Code loads it when a task matches its description.

How do I install Cicd Setup in Codex?

Run `npx skills add shawnpang/startup-founder-skills --skill cicd-setup -a codex`. Or copy the skill folder (skills/cicd-setup in shawnpang/startup-founder-skills) into .agents/skills/cicd-setup in your project. Codex loads it when a task matches its description.

Can I use Cicd Setup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add shawnpang/startup-founder-skills --skill cicd-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cicd-setup, .gemini/skills/cicd-setup, .github/skills/cicd-setup and .opencode/skills/cicd-setup in your project.

What does Cicd Setup need to run?

SKILL.md names no scripts, command-line tools or credentials: Cicd Setup is instructions for the agent only. Our summary lists: Python 3; Node.js.

Does Cicd Setup access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cicd Setup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cicd Setup use?

Cicd Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cicd Setup use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cicd Setup?

Skills that share tags, products or a category with Cicd Setup: Fingerprint CI Gate (liarjsdev/liarjs-skills, 518 stars), Megalinter Check (nvuillam/npm-groovy-lint, 248 stars), Migrate To Teamcity (JetBrains/teamcity-cli, 125 stars) and CI CD (EliasOulkadi/shokunin, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cicd Setup?

shawnpang (a GitHub user) maintains it in shawnpang/startup-founder-skills, which has 341 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on March 16, 2026.

Source: shawnpang/startup-founder-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.