remote-ci-verify

Push a branch and run CI-equivalent pnpm tests on an available SSH remote target.

18|5|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill remote-ci-verify-neko-catpital-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remote-ci-verify
Source: https://github.com/Neko-Catpital-Labs/Invoker/tree/main/skills/remote-ci-verify
Command: npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill remote-ci-verify-neko-catpital-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Local test runs often diverge from the real CI pipeline, so branches pass locally but fail after merge. This Skill pushes your current branch and replays the CI-equivalent test surface (pnpm install, UI build, Playwright setup, test:all) on a clean remote SSH machine, giving pre-merge confidence that mirrors .github/workflows/ci.yml. ## Core Features & Use Cases - Remote CI-equivalent execution: Runs pnpm install --frozen-lockfile, @invoker/ui build, Playwright dependency install, and CI=true pnpm run test:all inside a temporary remote git worktree. - Automatic target selection: Reads SSH targets from the Invoker config, skips targets busy in the Invoker database, and picks the first reachable host. - Configurable overrides: Environment variables control push behavior, target allowlists, test commands, Playwright setup, and worktree cleanup. - Use Case: Before opening a pull request on a pnpm monorepo, run the script to verify your branch against the same steps as the GitHub Actions test-all job on a spare build machine. ## Quick Start Ask the agent to run the remote-ci-verify skill to push the current branch and execute the CI-equivalent test suite on an available SSH target.

Frequently Asked Questions about remote-ci-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run CI-equivalent tests on a remote machine before merging?

Run the run-remote-ci-verify.sh script, which pushes your branch, selects a reachable SSH target from the Invoker config, creates a temporary remote worktree, and executes pnpm install, UI build, Playwright setup, and pnpm run test:all with CI=true.

How does the script choose which SSH target to use?

It reads remoteTargets from the Invoker config file, skips targets whose pool_member_id has active task statuses in the Invoker SQLite database, then picks the first target that answers a batch-mode SSH connectivity check.

Can I skip the git push or change the test command?

Yes. Set CI_VERIFY_PUSH=0 to skip pushing, and override CI_VERIFY_REMOTE_TEST_COMMAND to run a different command such as pnpm run test:all:extended. CI_VERIFY_TARGETS limits which target IDs are considered.

What happens to the remote worktree after the tests finish?

By default the script removes the remote worktree, prunes worktree metadata, and releases the target lock on exit. Set CI_VERIFY_KEEP_REMOTE_WORKTREE=1 to keep the worktree for debugging failed runs.

Why does the script fail with no available SSH target?

This happens when all configured targets are busy in the Invoker database, have unreadable sshKeyPath files, or fail the SSH connectivity check. Verify host, user, and sshKeyPath entries in the Invoker config and confirm network access.