verify

name	verify
description	Run CI targets locally, push, and watch remote CI checks. Surfaces issues concisely. All output saved to /tmp.
user-invocable	true
argument-hint	["pr_number"]

Run all CI verification steps. Save all output to /tmp/<project-name>/<branch-name>/verify-* files where <project-name> is from the root package.json name field and <branch-name> is the current git branch.

Step 1: Read CI workflow and project info

1. Read package.json to get the project name.
2. Get the current branch name: git branch --show-current
3. Create the output directory: mkdir -p /tmp/<project-name>/<branch-name>
4. Read .github/workflows/ci.yml to extract the list of run: steps (after the install step). These are the local CI targets to execute. This ensures the skill always stays in sync with the actual CI pipeline.

Step 2: Run local CI targets

For each run: step extracted from the workflow (skipping bun install), run it sequentially. Save stdout+stderr to /tmp/<project-name>/<branch-name>/verify-<step-name>.log (derive <step-name> from the step's name: field, lowercased and hyphenated, e.g. "Circular deps" -> "circular-deps").

Stop early if a step fails — do NOT continue to subsequent steps after a failure.

After running all (or stopping on failure), read the log files and report a concise summary:

• Which steps passed / failed
• For failures: extract the key error lines (not the full log)

Step 3: Push and watch remote CI

Only proceed to this step if ALL local steps passed.

1. Push the current branch:

   git push
   

2. Determine the PR number:

   • If $ARGUMENTS is provided, use it as the PR number
   • Otherwise, detect it:

     gh pr view --json number -q .number
     

3. Watch the CI checks, saving output:

   gh pr checks <pr_number> --watch 2>&1 | tee /tmp/<project-name>/<branch-name>/verify-ci-checks.log
   

4. After checks complete, report a concise summary:

   • Which checks passed / failed
   • For failures: show the failing check name and any available error info

Step 4: Final summary

Print a concise summary of all results:

• Local steps: pass/fail for each
• Remote CI: pass/fail for each check
• List all output files saved under /tmp/<project-name>/<branch-name>/verify-*.log
• If there are any failures, surface the key issues clearly