Labsco
google-labs-code logo

local-action-verification

★ 78

by google-labs-code · part of google-labs-code/jules-skills

Set up a repository for local GitHub Actions verification using act, so Jules can validate CI before pushing

🔥🔥🔥✓ VerifiedFreeQuick setup
#automation#devops#git
🧩 One of 2 skills in the google-labs-code/jules-skills package — works on its own, and pairs well with its siblings.

Set up a repository for local GitHub Actions verification using act, so Jules can validate CI before pushing

Inspect the full instructions your agent will receiveExpand

This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.

by google-labs-code

Set up a repository for local GitHub Actions verification using act, so Jules can validate CI before pushing npx skills add https://github.com/google-labs-code/jules-skills --skill local-action-verification Download ZIPGitHub78

Local Action Verification with act

You are setting up a repository so that Jules (or any agent) can run GitHub Actions workflows locally using act to verify code changes pass CI before pushing.

What You're Setting Up

Two scripts and an agents.md section that enable local CI verification:

  • install-act.sh — Installs act if missing (platform-aware, sudo fallback)

  • run-act.sh — Runs act in the background with log polling to avoid agent timeouts

  • AGENTS.md section — Instructions Jules reads to know how to use these scripts

Local CI Verification

Before pushing code or opening a PR, verify changes pass CI locally using act.

Prerequisites

  • Docker must be running
  • If act is not installed, run: bash scripts/act/install-act.sh

How to Verify

  1. Read .github/workflows/ to find the CI workflow and identify the job ID
  2. Run the verification script:
Copy & paste — that's it
bash scripts/act/run-act.sh "push -j "

With matrix: bash scripts/act/run-act.sh "push -j <JOB_ID> --matrix <KEY>:<VALUE>" 3. If the run fails, read the log output, fix the code, and re-run 4. After verification, clean up:

Copy & paste — that's it
rm -f act_output.log
git checkout

Configuration

  • Timeout: ACT_TIMEOUT=900 bash scripts/act/run-act.sh "..." (default: 600s)

  • Poll interval: ACT_POLL=15 bash scripts/act/run-act.sh "..." (default: 10s)

  • Custom image: pass -P ubuntu-latest=node:20-bookworm in the arguments for faster pulls

Copy & paste — that's it

### Step 3: Update .gitignore

Append these entries to `.gitignore` if they don't already exist:

act artifacts

act_output.log .secrets

Copy & paste — that's it

### Step 4: Print next steps for the user

Tell the user:
1. Docker must be installed and running on any machine (or Jules VM) where verification runs
2. `act` will be auto-installed on first use via `scripts/act/install-act.sh`
3. If workflows require secrets, create a `.secrets` file (KEY=VALUE format) — never commit it
4. Commit all generated files

## Resource References

- [Troubleshooting Guide](resources/troubleshooting.md) — Detailed solutions for common issues