CI

ci-verification

Allows running GitHub Actions locally with act to catch failures before they hit the server.

Install

mkdir -p .claude/skills/ci-verification && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15130" && unzip -o skill.zip -d .claude/skills/ci-verification && rm skill.zip

Installs to .claude/skills/ci-verification

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Verify GitHub Actions CI workflows locally using act before pushing or creating pull requests. Use this skill when asked to "run CI", "check CI", "verify CI locally", or when preparing a pull request.
200 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • Run GitHub Actions workflows locally
  • Catch build/test failures before pushing
  • Simulate CI for pull requests
  • List available jobs in workflows
  • Run specific jobs (e.g., e2e)
  • Debug output of CI runs

How it works

The skill uses the `act` CLI tool to run GitHub Actions workflows in local Docker containers, simulating the CI environment.

Inputs & outputs

You give it
GitHub Actions workflow file and optional job name
You get back
Local execution of CI workflow, showing build/test results

When to use ci-verification

  • Testing CI/CD workflows locally
  • Debugging workflow failures
  • Verifying PR readiness

About this skill

CI Verification with act

This project uses act to run GitHub Actions workflows locally before pushing, so build/test failures are caught before CD runs on GitHub.

Prerequisites

  • Docker (OrbStack supported) must be running
  • act must be installed: brew install act
  • ~/.actrc must contain --container-architecture linux/amd64

Environment Setup (OrbStack)

If DOCKER_HOST is not set, export it first:

export DOCKER_HOST="unix://${HOME}/.orbstack/run/docker.sock"

To make this permanent, append to ~/.actrc:

echo "--env DOCKER_HOST=unix://${HOME}/.orbstack/run/docker.sock" >> ~/.actrc

Workflow Files

FileTriggerPurpose
.github/workflows/e2e.ymlpull_request → mainType check + build + E2E tests
.github/workflows/deploy.ymlpush → mainProduction build + GitHub Pages deploy

Commands

List available jobs

act --list

Run PR CI (full: type check → build → E2E)

DOCKER_HOST="unix://${HOME}/.orbstack/run/docker.sock" \
  act pull_request \
  --container-architecture linux/amd64

Run only the e2e job (faster feedback)

DOCKER_HOST="unix://${HOME}/.orbstack/run/docker.sock" \
  act pull_request -j e2e \
  --container-architecture linux/amd64

Debug output

DOCKER_HOST="unix://${HOME}/.orbstack/run/docker.sock" \
  act pull_request -j e2e \
  --container-architecture linux/amd64 \
  -v

Pre-PR Checklist

Before creating a pull request, verify all of the following pass locally:

  1. pnpm build — production build succeeds (no bundler errors)
  2. pnpm exec tsc --noEmit — no TypeScript errors
  3. act pull_request -j e2e ... — CI green locally

Design Rationale

  • The e2e.yml CI workflow runs pnpm build before E2E tests. This ensures bundler errors (e.g. invalid manualChunks format for rolldown) are caught at PR review time, not after merging when deploy.yml runs.
  • deploy.yml runs independently on push to main and is not replicated in CI to avoid redundancy.

Known Pitfalls

IssueRoot CauseFix
manualChunks is not a functionrolldown requires function, not objectUse manualChunks(id) { ... } in vite.config.ts
no DOCKER_HOST warningOrbStack socket not on default pathSet DOCKER_HOST as above
M-series architecture warningsact defaults to host archUse --container-architecture linux/amd64

When not to use it

  • When Docker is not running
  • When `act` is not installed
  • When `~/.actrc` does not contain `--container-architecture linux/amd64`

Prerequisites

Dockeract

Limitations

  • Requires Docker to be running
  • Requires `act` to be installed
  • Requires specific `act` configuration for container architecture

How it compares

This skill enables local CI verification using `act` and Docker, providing faster feedback on workflow failures before committing, unlike relying solely on remote GitHub Actions runs.

Compared to similar skills

ci-verification side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
ci-verification (this skill)05moReviewIntermediate
ci-cd06moReviewIntermediate
e2e-test-service-management06moCautionBeginner
bazel-build-optimization142moNo flagsAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry