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

How to get a cold second review from the other vendor's agent with Sno Station Skills

Have a fresh agent from the other vendor check your change before it lands.

Who it is forA developer who finished a code change in Claude Code or Codex and wants an independent check before merging.

The problemAn agent reviewing its own work misses what it cannot see, so one vendor's review is often not enough.

The outcomeA review from a fresh session with none of the author's conversation, plus a fix loop that runs until the review comes back clean.

What you need first

  • A shell and curl on the machine
  • Claude Code or Codex already installed
  • Optional: both Claude Code and Codex CLIs, so peer review can use the other vendor

Steps

  1. Install the skills with sh -c 'sno_installer_body=$(curl -fsSL https://sno.ai/install) && printf "%s\n" "$sno_installer_body" | sh'
  2. If you add another agent later, run sno setup to connect it.
  3. In your agent, finish a change and say "peer-review this".
  4. Read the findings. The author fixes root causes and the review repeats until it is clean.

Prompt for your agent

In the repo <repo-path>, use the peer-review skill from Sno Station Skills on the latest uncommitted change, preferring the other vendor's CLI in a fresh session. Output the findings list with each finding's trigger, impact and refutation attempt. Verify that the first line of the report states whether the review was same-vendor.

Caveat. The installer is a remote script piped to sh, so read it at sno.ai/install before you run it, and the cross-vendor review needs both CLIs installed.

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