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

How to gate agent handoffs on a test command Foremerge runs with Foremerge

Register a trusted check so work counts as done only after Foremerge runs it itself.

Who it is forA developer who wants a finished agent's work verified by a command before other agents treat it as done.

The problemAn agent's own claim that its work passes is not enough for other agents to rely on.

The outcomeAccepted work is verified by a registered check that Foremerge runs, or is recorded as UNVERIFIED with the reason when no check was registered.

What you need first

  • Git and jq installed
  • macOS or Linux, or the Windows binaries from the releases page
  • A Git repository to coordinate, with at least one coding agent or a shell to act as one
  • Rust 1.85+ only if you build from source

Steps

  1. Register a fast check that would catch a broken handoff, such as foremerge checks set test -- cargo test --all-targets, replacing it with your repository's command.
  2. If the repository has nothing meaningful to verify, run foremerge checks policy advisory once instead of registering an always-passing check.
  3. Run foremerge doctor to confirm the registered checks can run in agent worktrees.

Prompt for your agent

In the <repo path> repository, register one check with `foremerge checks set` using the repository's real test command, then run `foremerge doctor`. Expected output: a doctor report stating whether the check can run in this worktree. Verify that the check does not always pass before you rely on it as a gate.

Caveat. The gate decides whether other agents may treat work as done but does not replace CI, and the project is a pre-1.0 local-first MVP.

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