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

How to get a thread woken when a PR checks, comments, or conflicts with P3 Stack

Watch an open pull request so the agent reacts to CI results and review comments.

Who it is forA developer who opened a PR and wants the agent to act on checks and review feedback without polling.

The problemChecking a PR by hand or running polling loops wastes time and misses changes.

The outcomeThe thread wakes when checks finish, someone comments, or the branch conflicts, and the agent handles the event.

What you need first

  • T3 Code installed, since install.sh links skills for it to read
  • git and a shell to run install.sh
  • At least one model provider available through T3 Code's orchestrator_capabilities
  • A git repository to work on

Steps

  1. Install the skills with ./install.sh if you have not already.
  2. Run /p3-mode and choose the opening a PR playbook for your branch.
  3. Have the agent call watch_pull_request on the PR it opened.
  4. When the thread wakes, read the check result or comment and let the agent respond.
  5. Stop watching once the PR is merged or closed.

Prompt for your agent

In the repo at <repo-path>, open a PR for branch <branch>, then call watch_pull_request on it. Expected output: the PR link and a note on each wake event (checks, comment, or conflict). Verify that the thread wakes on a real check completion rather than on a timer.

Caveat. The README does not say which hosting services watch_pull_request supports, so confirm it works with your PR host before relying on it.

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