[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YCP36DRX5RQ1P2M1MFSH3":3,"skill-same:01M72YCP36DRX5RQ1P2M1MFSH3":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M72YCP36DRX5RQ1P2M1MFSH3","babysit-pr",null,"Monitor a pull request through review and CI. Use when the user asks to monitor, watch, or babysit a PR.","h00mankind\u002Fworkflow","h00mankind","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F105175148?v=4","01M72XXA2JP2H3BBK5GP9AP4P6","h00man","01M72XXA3824K52XFYWJDBFJ06",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Ftstack\u002Fskills\u002Fbabysit-pr\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: babysit-pr\ndescription: Monitor a pull request through review and CI. Use when the user asks to monitor, watch, or babysit a PR.\n---\n\n# Babysit PR\n\nMany repos have AI review bots. They're helpful, even if they are not always\nright.\n\n## Waiting\n\nNever write your own watcher, polling loop, or `sleep` loop. Use one watcher\nper PR: `watch_pull_request` in T3 Code, `pr-wait` everywhere else. Never run\nboth on the same PR. Every watcher on a GitHub account shares one rate limit.\n\n### In T3 Code: `watch_pull_request`\n\nHandle the existing checks and comments first. Then call\n`watch_pull_request` and end your turn. T3 Code wakes you with a message when\na check fails, the required checks pass, someone comments or reviews, or the\nbranch conflicts.\n\n- **Only the thread that owns the PR watches it.** If you are a delegated\n  child task (a reviewer, a Sol round, any `delegate_task` child), never call\n  `watch_pull_request`. The parent owns the PR. Do not watch PRs you are not\n  working on.\n- **A wake is news, not a merge decision.** Check the merge gate yourself.\n- **Unwatch when you hand off.** A watched thread stays in Working and out of\n  the user's inbox. When you stop (ready, blocked, or asking the user a question),\n  call `unwatch_pull_request` first. A merge or close ends the watch on its\n  own.\n- **\"Stopped watching, could not read it\"** usually means GitHub's rate limit\n  is used up. Run `gh api rate_limit --jq .resources.graphql` before you\n  watch again. If `remaining` is near 0, wait for `reset` with one background\n  command, then watch again. Never watch again in a tight loop.\n\n### Everywhere else: `pr-wait`\n\nWait with `scripts\u002Fpr-wait` from this skill's directory (use its absolute\npath).\n\n```bash\npr-wait \u003Cpr> [--repo owner\u002Fname] [--until ready|green|any-change]\n```\n\nIt prints one line per real event. It exits 0 when the `--until` condition is\nmet or the PR merges, 1 when it needs you (a required check failed, conflicts,\nunresolved threads, PR closed), and 2 on bad input.\n\n- `ready` (default): required checks green, Greptile or Macroscope reviewed the\n  head, and no unresolved threads. Use this to babysit.\n- `green`: required checks only. Use it when the repo has no Greptile or\n  Macroscope.\n- `any-change`: exit on the first event.\n\nIn Claude Code, run it with the Monitor tool (`timeout_ms: 3600000`), so each\nline wakes you. Without a monitor, run it as one long command. It ends on its\nown.\n\nStart it again after you push, after you handle an exit 1, and after a resume.\nIt remembers what it already reported, so nothing that arrived in between is\nlost. If it says another pid already watches the PR, do not start a second one.\nKill the old one only if its events do not reach you.\n\nWith either watcher: when an event needs no action, end your turn without a\nmessage. Never post or say \"still waiting\".\n\n## GitHub rate limits\n\n`gh pr create`, `gh pr view`, and `gh pr checks` use GraphQL. When GraphQL is\nused up, the REST limit is separate and usually still has room. Use\n`gh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fpulls\u002F\u003Cn>` to read a PR, and\n`gh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fcommits\u002F\u003Csha>\u002Fcheck-runs` for checks.\n\n## Reviews\n\nOnly act on checks and comments newer than the latest push. Verify every bot\nfinding against the source before changing code. Fix real findings and CI\nfailures, distinguish repository failures from infrastructure flakes, and reply\nwith a written reason when dismissing false positives.\n\nIf the repo has `.macroscope\u002Fcheck-run-agents\u002F*.md`, read those rules before you\nreply to a Macroscope finding. Its findings cite them.\n\nCodeRabbit is advisory. Treat its findings like any other finding, but never\nwait for it and never hold a merge for it.\n\nIf a review bot leaves feedback you believe is not worth addressing, reply with\na written reason and resolve the comment. Use the `leaving-pr-comments` skill\nfor every comment posted on the user's behalf.\n\nScreenshots and videos help as well, when you have a way to upload them.\n\nKeep the PR at the size the user's goal needs. Review loops tend to grow a\nPR one cheap-looking fix at a time. Fix real bugs in the intended case.\nDecline the rest with a written reason, and list them as follow-ups:\nunneeded tests, guards for edge cases that do not matter, extra integration\nor compatibility, and small performance costs. Prefer the fix that deletes or\nnarrows code.\n\n## Base branch and merging\n\nKeep an eye on changes to `main` and rebase when needed. `pr-wait` reports when\nnew base commits touch this PR's files, and when the PR becomes BEHIND or DIRTY.\n`watch_pull_request` reports conflicts only, so check for BEHIND yourself\nbefore you call the PR ready.\nIf an overlapping PR makes this one obsolete, stop monitoring, report it to the\nuser, and ask before closing the PR unless closure was explicitly authorized.\n\nIf nothing has changed, stay quiet rather than posting filler comments. Stop\nwhen `pr-wait` exits 0, or in T3 Code when the merge gate passes on the latest\nhead. Merge only when the user explicitly requested it;\notherwise report that the PR is ready. Right before a merge, run `git fetch` and\ncheck the PR again. Never merge when it is BEHIND or DIRTY, or when base commits\nthat landed after the last green run touch this PR's files. Rebase, push, and\nwait for green again.\n","# Babysit PR\n\nMany repos have AI review bots. They're helpful, even if they are not always\nright.\n\n## Waiting\n\nNever write your own watcher, polling loop, or `sleep` loop. Use one watcher\nper PR: `watch_pull_request` in T3 Code, `pr-wait` everywhere else. Never run\nboth on the same PR. Every watcher on a GitHub account shares one rate limit.\n\n### In T3 Code: `watch_pull_request`\n\nHandle the existing checks and comments first. Then call\n`watch_pull_request` and end your turn. T3 Code wakes you with a message when\na check fails, the required checks pass, someone comments or reviews, or the\nbranch conflicts.\n\n- **Only the thread that owns the PR watches it.** If you are a delegated\n  child task (a reviewer, a Sol round, any `delegate_task` child), never call\n  `watch_pull_request`. The parent owns the PR. Do not watch PRs you are not\n  working on.\n- **A wake is news, not a merge decision.** Check the merge gate yourself.\n- **Unwatch when you hand off.** A watched thread stays in Working and out of\n  the user's inbox. When you stop (ready, blocked, or asking the user a question),\n  call `unwatch_pull_request` first. A merge or close ends the watch on its\n  own.\n- **\"Stopped watching, could not read it\"** usually means GitHub's rate limit\n  is used up. Run `gh api rate_limit --jq .resources.graphql` before you\n  watch again. If `remaining` is near 0, wait for `reset` with one background\n  command, then watch again. Never watch again in a tight loop.\n\n### Everywhere else: `pr-wait`\n\nWait with `scripts\u002Fpr-wait` from this skill's directory (use its absolute\npath).\n\n```bash\npr-wait \u003Cpr> [--repo owner\u002Fname] [--until ready|green|any-change]\n```\n\nIt prints one line per real event. It exits 0 when the `--until` condition is\nmet or the PR merges, 1 when it needs you (a required check failed, conflicts,\nunresolved threads, PR closed), and 2 on bad input.\n\n- `ready` (default): required checks green, Greptile or Macroscope reviewed the\n  head, and no unresolved threads. Use this to babysit.\n- `green`: required checks only. Use it when the repo has no Greptile or\n  Macroscope.\n- `any-change`: exit on the first event.\n\nIn Claude Code, run it with the Monitor tool (`timeout_ms: 3600000`), so each\nline wakes you. Without a monitor, run it as one long command. It ends on its\nown.\n\nStart it again after you push, after you handle an exit 1, and after a resume.\nIt remembers what it already reported, so nothing that arrived in between is\nlost. If it says another pid already watches the PR, do not start a second one.\nKill the old one only if its events do not reach you.\n\nWith either watcher: when an event needs no action, end your turn without a\nmessage. Never post or say \"still waiting\".\n\n## GitHub rate limits\n\n`gh pr create`, `gh pr view`, and `gh pr checks` use GraphQL. When GraphQL is\nused up, the REST limit is separate and usually still has room. Use\n`gh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fpulls\u002F\u003Cn>` to read a PR, and\n`gh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fcommits\u002F\u003Csha>\u002Fcheck-runs` for checks.\n\n## Reviews\n\nOnly act on checks and comments newer than the latest push. Verify every bot\nfinding against the source before changing code. Fix real findings and CI\nfailures, distinguish repository failures from infrastructure flakes, and reply\nwith a written reason when dismissing false positives.\n\nIf the repo has `.macroscope\u002Fcheck-run-agents\u002F*.md`, read those rules before you\nreply to a Macroscope finding. Its findings cite them.\n\nCodeRabbit is advisory. Treat its findings like any other finding, but never\nwait for it and never hold a merge for it.\n\nIf a review bot leaves feedback you believe is not worth addressing, reply with\na written reason and resolve the comment. Use the `leaving-pr-comments` skill\nfor every comment posted on the user's behalf.\n\nScreenshots and videos help as well, when you have a way to upload them.\n\nKeep the PR at the size the user's goal needs. Review loops tend to grow a\nPR one cheap-looking fix at a time. Fix real bugs in the intended case.\nDecline the rest with a written reason, and list them as follow-ups:\nunneeded tests, guards for edge cases that do not matter, extra integration\nor compatibility, and small performance costs. Prefer the fix that deletes or\nnarrows code.\n\n## Base branch and merging\n\nKeep an eye on changes to `main` and rebase when needed. `pr-wait` reports when\nnew base commits touch this PR's files, and when the PR becomes BEHIND or DIRTY.\n`watch_pull_request` reports conflicts only, so check for BEHIND yourself\nbefore you call the PR ready.\nIf an overlapping PR makes this one obsolete, stop monitoring, report it to the\nuser, and ask before closing the PR unless closure was explicitly authorized.\n\nIf nothing has changed, stay quiet rather than posting filler comments. Stop\nwhen `pr-wait` exits 0, or in T3 Code when the merge gate passes on the latest\nhead. Merge only when the user explicitly requested it;\notherwise report that the PR is ready. Right before a merge, run `git fetch` and\ncheck the PR again. Never merge when it is BEHIND or DIRTY, or when base commits\nthat landed after the last green run touch this PR's files. Rebase, push, and\nwait for green again.\n",{"name":5,"description":7},"main","2b813251957e3e80c45cc5f55bf9c228d818d05b","plugins\u002Ftstack\u002Fskills\u002Fbabysit-pr","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow","https:\u002F\u002Fgithub.com\u002Fh00mankind","an ordinary mortal h00man","2026-11-13 01:29:34",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add h00mankind\u002Fworkflow --skill babysit-pr",{"tool":37,"command":38},"bunx","bunx skills add h00mankind\u002Fworkflow --skill babysit-pr",{"tool":40,"command":41},"pnpm","pnpm dlx skills add h00mankind\u002Fworkflow --skill babysit-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Ftstack\u002Fskills\u002Fbabysit-pr\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"scripts\u002Fpr-wait","SCRIPT","脚本",24724,"https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Ftstack\u002Fskills\u002Fbabysit-pr\u002Fscripts\u002Fpr-wait",[52,60,67,75,82,89],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":59},"01M78R7TT830V3BYFNDX1EHF0V","teach","Teach the user a subject, in explain mode (one plain account of code, a change, or a concept, in chat) or course mode (a learning workspace with a mission, lessons, and records over many sessions). Runs only when the user types \u002Fteach.","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fh00man\u002Fskills\u002Fteach\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":59},"01M78R7RSGFF5TFE0JBGY3WKEJ","council","Get a review or a second opinion on existing work from several strong models of different providers. Runs only when the user types \u002Fcouncil.","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fh00man\u002Fskills\u002Fcouncil\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":74},"01M74AAVCZZREXPZEE5HRN5WF5","variant","Builds multiple variants of a component you're working on and helps you iterate and pick one.","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fjakub\u002Fskills\u002Fvariant\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":74},"01M74AAR3M07M86YX2CXPD79EX","teardown","Creates technical illustrations of physical objects and of how things work, such as display pixels or interface layers, with coherent views, fine linework and part fills.","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fjakub\u002Fskills\u002Fteardown\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":74},"01M74AAMKJ8MKP9M99K37A82ZM","state-machine","Renders every state of a component you choose on a throwaway page, with mock data and a switcher, so you can work on each state.","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fjakub\u002Fskills\u002Fstate-machine\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":74},"01M74AAHF2A498F7F2E74696KF","interface-review","Reviews a branch, pull request or uncommitted change for the interface problems it introduced or regressed, across accessibility, layout, writing, typography, color and UI.","https:\u002F\u002Fgithub.com\u002Fh00mankind\u002Fworkflow\u002Fblob\u002Fmain\u002Fplugins\u002Fjakub\u002Fskills\u002Finterface-review\u002FSKILL.md",[],[]]