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.zipInstalls 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.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
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
actmust be installed:brew install act~/.actrcmust 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
| File | Trigger | Purpose |
|---|---|---|
.github/workflows/e2e.yml | pull_request → main | Type check + build + E2E tests |
.github/workflows/deploy.yml | push → main | Production 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:
pnpm build— production build succeeds (no bundler errors)pnpm exec tsc --noEmit— no TypeScript errorsact pull_request -j e2e ...— CI green locally
Design Rationale
- The
e2e.ymlCI workflow runspnpm buildbefore E2E tests. This ensures bundler errors (e.g. invalidmanualChunksformat for rolldown) are caught at PR review time, not after merging whendeploy.ymlruns. deploy.ymlruns independently on push tomainand is not replicated in CI to avoid redundancy.
Known Pitfalls
| Issue | Root Cause | Fix |
|---|---|---|
manualChunks is not a function | rolldown requires function, not object | Use manualChunks(id) { ... } in vite.config.ts |
no DOCKER_HOST warning | OrbStack socket not on default path | Set DOCKER_HOST as above |
| M-series architecture warnings | act defaults to host arch | Use --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
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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| ci-verification (this skill) | 0 | 5mo | Review | Intermediate |
| ci-cd | 0 | 6mo | Review | Intermediate |
| e2e-test-service-management | 0 | 6mo | Caution | Beginner |
| bazel-build-optimization | 14 | 2mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
ci-cd
ZacharyLuz
Continuous Integration and Continuous Deployment best practices. Use when setting up automated build pipelines, test automation, deployment workflows, or improving release processes.
e2e-test-service-management
raphaelmansuy
Service management for E2E testing in EdgeQuake. Start, stop, and monitor PostgreSQL, backend API, and frontend services. Includes health checks and logging utilities for interactive testing workflows.
bazel-build-optimization
wshobson
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
k8s-helm
rohitg00
Manage Helm charts, releases, and repositories. Use for Helm installations, upgrades, rollbacks, chart development, and release management.
cloudflare-deploy
davila7
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.