메뉴
Run this repo's GitHub Actions locally with Agent-CI before pushing CI-sensitive changes.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/SocketDev/socket-btm --skill agent-ci명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | agent-ci |
| description | Run this repo's GitHub Actions locally with Agent-CI before pushing CI-sensitive changes. |
| user-invocable | true |
| allowed-tools | Bash, Read, Edit |
| model | claude-haiku-4-5 |
| context | fork |
| metadata | {"internal":true} |
Run the repo's CI pipeline locally before pushing. CI was green before you started, so any failure the local run surfaces comes from your changes.
RedwoodJS wrote the upstream tool and skill (MIT, https://github.com/redwoodjs/agent-ci). The fleet pins @redwoodjs/agent-ci in the wheelhouse catalog and wires it as the ci:local package script (resolved via node_modules/.bin, never /). Edit only in ; the cascade refreshes downstream copies.
pnpm execnpxsocket-wheelhouse/template/open -a OrbStack; recommended over Docker Desktop). If the daemon is down, agent-ci fails fast with couldn't use a Docker socket at /var/run/docker.sock … missing or a dangling symlink and exit 1 — that's the daemon, not a workflow failure. Start the provider, confirm with docker info, re-run. No daemon and can't start one → fall back to greening-ci (push + watch remote).@redwoodjs/agent-ci is a fleet devDependency (catalog:), provisioned by pnpm install.--github-token for remote reusable workflows — every socket-* repo's ci.yml calls a SocketDev/socket-registry/.github/workflows/… reusable workflow. agent-ci can't fetch it without a token; pass --github-token (no value → auto-resolves via gh auth token). Omitting it makes a remote-reusable CI silently fail to resolve.runs-on: macos-*) run in a throwaway VM and need tart + sshpass on an Apple Silicon host (brew install cirruslabs/cli/tart hudochenkov/sshpass/sshpass). Without both, macOS jobs are skipped with a reason — the rest of the run still proceeds.The blessed entry is the canonical ci:local script — it already carries the full flag set (--all --quiet --pause-on-failure --github-token), and pnpm resolves the agent-ci binary from node_modules/.bin cross-platform:
pnpm run ci:local
--all runs the PR/push workflows for the current branch. --quiet suppresses the live renderer (pipe-safe). --pause-on-failure stops at the first failed step and holds the container open for retry. --github-token (bare → gh auth token) fetches the socket-registry reusable workflow every fleet ci.yml calls. Pipes are safe: when stdout is not a TTY the launcher detaches and the foreground process exits 77 the moment a step pauses, so | tee log and > log.txt work.
There is no --list or dry-run flag — run executes. Args after the subcommand pass through, so a typo'd flag becomes a workflow arg rather than an error.
To resolve the binary from a .mts script (not a package.json script — those resolve node_modules/.bin themselves), use the fleet helper, never a shelled-out which/command -v (which searches the global PATH and resolves the wrong binary — enforced by socket/no-which-for-local-bin):
import { whichSync } from "@socketsecurity/lib-stable/bin/which";
const agentCi = whichSync("agent-ci", {
path: nodeModulesBinDir,
nothrow: true,
});
When a step fails the run pauses (and the run.paused event carries the exact retry_cmd to copy). Fix the code, then retry the paused runner — don't restart the whole pipeline:
node_modules/.bin/agent-ci retry --name <runner-name>
Call the linked binary directly, the fleet form for an ad-hoc bin invocation, same as node_modules/.bin/oxfmt / tsgo in build scripts — never pnpm exec/npx. Re-run from an earlier step with --from-step <N>. Repeat fix → retry until every job passes. Don't push to trigger remote CI when agent-ci can run it locally.
--json event stream, the full requirements rationale, and the agent-ci-vs-remote-CI decision matrix: see reference.md.Use greening-ci-local for the local fix-and-retry loop, and greening-ci when a real runner is required.