DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run faster checks on a small change with First Pass

Switch to quick mode so a small change runs only the checks it can affect.

Who it is forA developer making a small, contained change who does not need the full CI run on every edit.

The problemRunning the full CI suite on every small change is slow, but a change still needs proof that it does not break what it touches.

The outcomeThe change runs format, lint, types, build, its own tests, and every test that reaches what it touched. The rest is left for a full run.

What you need first

  • Claude Code to install the plugin (Cursor and Codex get the rules and skills, but hooks are Claude Code only)
  • A folder that holds your repos, where you start your sessions
  • Git repos with a branch to review, for the review use case (GitHub access is needed to read pull requests, inferred from the README)

Steps

  1. Complete the install and setup steps from /plugin install first-pass@first-pass and /first-pass:setup-first-pass.
  2. Run /first-pass:quick to turn quick mode on.
  3. Make your change and run the checks through the ship-check flow.
  4. Run /first-pass:quick off to return to full CI checks before the final merge.

Prompt for your agent

In the <repo-name> repo, run /first-pass:quick, make the change described here: <change-description>, then run ship-check. Expected output: a report listing each check run and its result, and which checks were left for a full run. Verify that the report says which CI checks were not run.

Caveat. Quick mode leaves the rest of the suite for a full run such as your pull request's CI, so a change is not fully proven until that run passes.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page