Send
Make a PR, wait for CI with bounded transport retries, independently review, and merge...
Install
npx skills add yc-software/qm --skill send -g -a claude-code -y- Repository
- yc-software/qm15.6k
- Category
- Git and review
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 1,528 tokens
- Runs scripts
- No, instructions only
What it does
Make a PR, wait for CI with bounded transport retries, independently review, and merge only when all gates pass.
Babysit
Make a pull request for the change we just discussed, file it, babysit CI, fix any issues that come up, and merge once CI is fully green.
Steps
-
Make the PR. Commit the discussed change on a feature branch (create one off the default branch if currently on it). Push it.
-
File it. Open a pull request with a clear title and description covering why and what changed. Use
ghfor GitHub orglabfor GitLab. Detect from the remote. -
Wait for CI in one blocking process, with bounded transport retries. Load the
github-gitlabskill; it reports the directory holding its scripts. For GitHub, capture the PR's full head SHA and use its bundled helper, not baregh pr checks --watch:node <github-gitlab dir>/scripts/watch-ci.mjs --repo OWNER/REPO --pr NUMBER --head REVIEWED_HEAD_SHARun this with
execute, an explicitsandbox_id,background:true, and authorized credentials; subscribe withbackgroundactionwatchand the returnedprocess_id. Keep that sandbox ID throughout the checkout, checks, and push. Keep one watcher per PR; hand off if another agent already owns it. The helper polls internally, retries recognized transport/server errors with bounded backoff, and has a 30-minute overall deadline. Set the background lifetime longer than that. Do not wake the model repeatedly to report pending checks.Read the helper's JSON status, not just the exit code. Pending is not failure; TLS timeouts and connection resets are not logout or permission expiry. Failed checks, auth failures, rate limits, unknown errors, exhausted retries, and deadlines all remain nonzero. Keep
set -e; never mask failure with a success marker or merge. A changed head invalidates successful checks and reviews: restart both on the new SHA. Empty, skipped, or cancelled checks do not count as success.

