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

How to check another agent's "done" claims before accepting them with Open Steps

Verify each claim from another session against what actually happened, then get a next action.

Who it is forA developer or product lead who gets a "finished" message from another agent session and wants proof before merging or moving on.

The problemAn agent that says it is done may have overstated its results, and checking every claim by hand takes time the person does not have.

The outcomeEach claim is checked against what actually happened, with a plain statement of what to do about any gaps.

What you need first

  • git, to download and update the pack
  • One of Claude Code, Codex CLI, Cursor CLI or Gemini CLI installed
  • gh, GitHub's command-line tool (optional; without it some output says "not checked")

Steps

  1. Run git clone https://github.com/kharmanskyi/open-steps.git
  2. Install the skills for your tool (Claude Code: claude plugin marketplace add ./open-steps && claude plugin install open-steps@open-steps)
  3. Ask the agent to check the other session's pull request with gh pr view and gh pr checks
  4. Read the list of checked claims and the next action it recommends

Prompt for your agent

In the open-steps repo at <repo-path>, use the os-check-work skill to verify the claims in the report from <other-session> about pull request <number>. Expected output: each claim marked against what actually happened, followed by one recommended action. Verify that no claim is accepted without a check.

Caveat. Pull request reads depend on gh being installed and signed in, and without it the output says "not checked" rather than verifying.

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