Skip to content
Back to skills

Setting Up Ci

ASecurity

Set up a GitHub Actions CI/CD pipeline with linting, testing, type-checking, and deployment steps.

  • 4 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 10, 2026
devopspythongonodetestinggitapici/cd

Works with

  • api

Security analysis

A92/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned September 10, 2026

npx -y skills add 0xAidan/polymarket-bot-test --skill setting-up-ci --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Setting Up Ci?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Setting Up Ci
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/0xaidan-setting-up-ci/badge)](https://www.skillsdirectory.com/skills/0xaidan-setting-up-ci)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: setting-up-ci
description: Set up a GitHub Actions CI/CD pipeline with linting, testing, type-checking, and deployment steps.
---

# Setup CI (GitHub Actions)

Use this skill when the user asks to set up CI, continuous integration, a build pipeline, or GitHub Actions.

## Steps

1. **Detect the project structure** — check for `package.json` (Node.js), `requirements.txt` / `pyproject.toml` (Python), `go.mod` (Go), or monorepo tools like Turborepo.

2. **Create `.github/workflows/ci.yml`**

   For a Node.js project:

   ```yaml
   name: CI

   on:
     push:
       branches: [main]
     pull_request:
       branches: [main]

   jobs:
     build:
       runs-on: ubuntu-latest
       steps:
         - uses: actions/checkout@v4
         - uses: actions/setup-node@v4
           with:
             node-version: 20
             cache: npm
         - run: npm ci
         - run: npm run lint
         - run: npm run typecheck
         - run: npm test
         - run: npm run build
   ```

3. **Add type-checking** — if `typecheck` script doesn't exist in `package.json`, add `"typecheck": "tsc --noEmit"`.

4. **Add caching** — the `actions/setup-node` `cache` option handles `node_modules`. For monorepos with Turborepo, add remote caching or `actions/cache` for `.turbo`.

5. **Add matrix testing (optional)** — if the user needs to test across Node versions or OS:

   ```yaml
   strategy:
     matrix:
       node-version: [18, 20, 22]
   ```

6. **Add deployment step (optional)** — if requested, add a deploy job that runs only on `main` pushes, gated by the build job succeeding:

   ```yaml
   deploy:
     needs: build
     if: github.ref == 'refs/heads/main'
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
       - run: npm ci && npm run build
       - run: npx vercel deploy --prod --token=${{ secrets.VERCEL_TOKEN }}
   ```

7. **Add status badge** — add the workflow status badge to the project README:

   ```markdown
   ![CI](https://github.com/OWNER/REPO/actions/workflows/ci.yml/badge.svg)
   ```

## Notes

- Keep CI fast — run lint and typecheck in parallel using separate jobs if the pipeline is slow.
- Use `npm ci` (not `npm install`) for deterministic installs.
- Store secrets (API keys, deploy tokens) in GitHub repository settings, never in the workflow file.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.