Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From Sherif's Skills
Like /watch-pr, but with no time budget — keep watching and responding until the PR merges or closes.
How this command is triggered — by the user, by Claude, or both
Slash command
/skills:watch-pr-indefinitely [PR number or URL] (defaults to current branch's PR)The summary Claude sees in its command listing — used to decide when to auto-load this command
Same flow as `/watch-pr` (load the **git** skill, read `references/watch.md` and `references/review-responses.md`, resolve the PR from `$ARGUMENTS` or the current branch, spawn a cheap background watcher, respond to review comments per `references/review-responses.md`). The only difference: **run indefinitely.** Watch until the PR merges or closes, not until a time budget runs out. - Run the watcher with **no `--max-total`** (and no `--max-wait` cap beyond the default), so it never returns `BUDGET SPENT`. - On every non-terminal `>>` verdict (`EVENT` / `QUIET`), relaunch the watcher in th...
Same flow as /watch-pr (load the git skill, read references/watch.md and references/review-responses.md, resolve the PR from $ARGUMENTS or the current branch, spawn a cheap background watcher, respond to review comments per references/review-responses.md).
The only difference: run indefinitely. Watch until the PR merges or closes, not until a time budget runs out.
--max-total (and no --max-wait cap beyond the default), so it never returns BUDGET SPENT.>> verdict (EVENT / QUIET), relaunch the watcher in the background. Keep doing this across turns; do not stop just because the PR went quiet.SETTLED is not a stop condition here: checks finishing and activity dying down still means the PR is open. Re-baseline and keep watching for the next review or push.CLOSED (merged or closed). When that fires, report the final digest and stop.npx claudepluginhub sherifabdlnaby/skills --plugin skills