CI-First Verification — Don't Kill the Laptop

The situation

You are one of several agents working concurrently on this machine. Every full build, test suite, typecheck, or repo-wide lint you launch competes for the same CPU, memory, and disk as every other agent's work. A handful of agents each "just running the tests" brings the whole machine to its knees — and most of those runs duplicate verification that CI already does for free on the PR.

The core rule

Before launching any heavy local process, ask: is CI already answering this question? If the branch has a PR, the answer is usually yes. Read the CI result instead of recomputing it locally.

Check CI instead

gh pr checks <number>            # pass/fail summary of all checks on the PR
gh pr checks <number> --watch    # only when you must block on a result
gh run list --branch <branch>    # workflow runs for the branch
gh run view <run-id> --log-failed  # read ONLY the failing steps' logs