Agent Ci
- 1.6k installs
- 725 repo stars
- Updated July 31, 2026
- redwoodjs/agent-ci
agent-ci is an agent skill for run github actions ci locally with agent ci to validate changes before pushing. use when testing, running checks, or validating code changes.
About
The agent-ci skill is designed for run GitHub Actions CI locally with Agent CI to validate changes before pushing. Use when testing, running checks, or validating code changes. Agent CI Run the full CI pipeline locally before pushing. CI was green before you started — any failure is caused by your changes. Invoke when the user testing, running checks, or validating code changes.
- run.start (with schemaVersion: 1, runId).
- job.start, job.finish (status: passed|failed).
- step.start, step.finish (status: passed|failed|skipped).
- run.paused (carries runner + retry_cmd).
- run.finish (status: passed|failed).
Agent Ci by the numbers
- 1,551 all-time installs (skills.sh)
- +92 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #240 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 4, 2026 (Skillselion catalog sync)
agent-ci capabilities & compatibility
- Capabilities
- run.start (with schemaversion: 1, runid) · job.start, job.finish (status: passed|failed) · step.start, step.finish (status: passed|failed|s · run.paused (carries runner + retry_cmd)
- Use cases
- frontend
What agent-ci says it does
Run GitHub Actions CI locally with Agent CI to validate changes before pushing. Use when testing, running checks, or validating code changes.
Run GitHub Actions CI locally with Agent CI to validate changes before pushing. Use when testing, running checks, or validating code changes.
npx skills add https://github.com/redwoodjs/agent-ci --skill agent-ciAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.6k |
|---|---|
| repo stars | ★ 725 |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 31, 2026 |
| Repository | redwoodjs/agent-ci ↗ |
How do I run github actions ci locally with agent ci to validate changes before pushing. use when testing, running checks, or validating code changes?
Run GitHub Actions CI locally with Agent CI to validate changes before pushing. Use when testing, running checks, or validating code changes.
Who is it for?
Developers using agent ci workflows documented in SKILL.md.
Skip if: Skip when the task falls outside agent-ci scope or needs a different stack.
When should I use this skill?
User testing, running checks, or validating code changes.
What you get
Completed agent-ci workflow with documented commands, files, and expected deliverables.
- local CI run log
- paused failure diagnostics
- pre-push validation report
By the numbers
- Skill metadata version 1.0.0
- Requires Node.js 18+ and Docker
- Non-TTY pause exits with code 77
Files
Agent CI
Run the full CI pipeline locally before pushing. CI was green before you started — any failure is caused by your changes.
Run
npx @redwoodjs/agent-ci run --quiet --all --pause-on-failurePipes are safe — pause-on-failure works through | tee log, > log.txt, etc. When stdout isn't a TTY the launcher detaches the run and the foreground process exits 77 the moment a step pauses, freeing the pipe while the container stays paused for retry.
Retry
When a step fails, the run pauses automatically. Fix the issue, then retry:
npx @redwoodjs/agent-ci retry --name <runner-name>To re-run from an earlier step:
npx @redwoodjs/agent-ci retry --name <runner-name> --from-step <N>Repeat until all jobs pass. Do not push to trigger remote CI when agent-ci can run it locally.
Machine-readable output (--json)
For programmatic monitoring, add --json (or set AGENT_CI_JSON=1) to emit an NDJSON event stream on stdout — one JSON object per line. Events:
run.start(withschemaVersion: 1,runId)job.start,job.finish(status: passed|failed)step.start,step.finish(status: passed|failed|skipped)run.paused(carriesrunner+retry_cmd)run.finish(status: passed|failed)diagnostic
--json is decoupled from --quiet, and the diff renderer is auto-suppressed under --json so ANSI sequences don't collide with the stream. Combined with the exit-77 pause signal above, this gives agents a robust contract: parse run.paused events, react, and call retry — no plaintext grep required.
Related skills
Frontend DesignGenerate distinctive, production-grade frontend interfaces and components that avoid generic AI aesthetics.716k165k
Web Design GuidelinesAutomatically audit frontend code against the latest Vercel Web Interface Guidelines for consistency, accessibility, and UX quality.498k29.6k
Lark WhiteboardGenerate valid Lark Whiteboard (Feishu Board) documents with correctly placed connectors, automatic routing, and proper schema compliance directly from agent inst389k16k
Sleek Design Mobile AppsGenerate mobile app screens and UI from plain English descriptions using the Sleek.design API.315k476
Design Taste FrontendOverride generic LLM frontend output with intentional, metric-driven UI/UX taste.301k69.4k
Ui Ux Pro MaxGet instant, high-quality UI/UX decisions, component recommendations, style guidance, and code improvements across web and mobile projects.290k112kHow it compares
Use agent-ci to mirror project GitHub Actions holistically; use single-linter skills when only one local check is needed.
FAQ
What does agent-ci do?
Run GitHub Actions CI locally with Agent CI to validate changes before pushing. Use when testing, running checks, or validating code changes.
When should I use agent-ci?
User testing, running checks, or validating code changes.
Is agent-ci safe to install?
Review the Security Audits panel on this page before installing in production.