[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F6Z6CBMB38TYQ90356MSX3":3,"skill-same:01M7F6Z6CBMB38TYQ90356MSX3":45},{"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},"01M7F6Z6CBMB38TYQ90356MSX3","babysit",null,"Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in \u002Fbabysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.","thoriqakbar0\u002Fpstack","thoriqakbar0","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F41317726?v=4","01M79VA5KRJ0JGV5QVY39PZ5R3","thoriq","01M7F6YHPQFXN84EM04GNWA3T6",0,"MIT","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fbabysit\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: babysit\ndescription: Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in \u002Fbabysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.\n---\n\n# Babysit a PR\n\nOn Codex, read the [platform mapping](..\u002Fpoteto-mode\u002Freferences\u002Fcodex-tools.md), including its per-skill notes, before following this skill.\n\nOn GitHub Copilot, read the [platform mapping](..\u002Fpoteto-mode\u002Freferences\u002Fcopilot-tools.md), including its per-skill notes, before following this skill.\n\nOn Muse, read the [platform mapping](..\u002Fpoteto-mode\u002Freferences\u002Fmuse-tools.md), including its per-skill notes, before following this skill.\n\nClaude Code analog of Cursor's built-in `\u002Fbabysit`. The implementation is a loop over `gh` CLI plus the Claude Code `loop` skill for pacing.\n\nInside poteto-mode, the **Babysit** playbook ([`..\u002Fpoteto-mode\u002Fplaybooks\u002Fbabysit.md`](..\u002Fpoteto-mode\u002Fplaybooks\u002Fbabysit.md)) supersedes this skill: it owns mode declaration, the merge frontier, stack safety, and the `watch-pr` watcher. This skill stays the standalone `\u002Fbabysit` entry point for a single PR outside a poteto-mode run.\n\n## When to use\n\n- There's an open PR and the user explicitly wants it kept green, and you are not already inside a poteto-mode run (the playbook owns that case).\n- The user invokes `\u002Fbabysit` directly.\n- A subagent that opens a PR does NOT babysit — return to the parent and let the parent decide.\n\n## Steps\n\n1. **Fetch PR state.**\n\n   ```bash\n   gh pr view \u003Cnumber> --json number,title,state,mergeable,reviewDecision,statusCheckRollup,mergeStateStatus,comments,reviews\n   ```\n\n2. **Triage in priority order.**\n   - Merge conflicts (`mergeStateStatus == DIRTY`): run the **fix-merge-conflicts** skill. Force-push only if the branch is yours and not shared.\n   - Failing checks (`statusCheckRollup` entries with `conclusion: FAILURE`): run the **fix-ci** skill. Root-cause the failure; fix the underlying code or test; commit; push.\n   - Review comments: run the **get-pr-comments** skill for the summary, then act only on feedback you actually agree with. When a comment has a single mechanical answer — a rename, a guard clause, a formatting nit — make the edit and quote the comment in the commit message. When it hinges on a judgement call, or you can't tell what's being asked, don't guess: leave it and reply with what you would have done.\n   - Review-bot comments (Bugbot and similar automation): classify fix\u002Fdismiss\u002Fask before acting, per [`bugbot-triage.md`](..\u002Fpoteto-mode\u002Freferences\u002Fbugbot-triage.md). Ask by default on security, data, and high-severity findings.\n\n3. **Loop.** Use the Claude Code `loop` skill to pace re-checks. Pick the interval from what you're watching:\n   - Active CI run: poll `gh pr checks --watch` (it blocks until checks finish, so no separate loop interval needed).\n   - Awaiting reviewer: 20–30 min heartbeat.\n   - Idle but want to catch new comments: hourly.\n\n4. **When to stop.**\n   - Build is green, every comment resolved, branch merges cleanly → call it ready.\n   - You've run three rounds of fix → push → recheck and it still isn't fully green → stop, summarise what's still broken, and hand control back.\n   - The next fix would force a design choice → pause and put it to the user with `AskUserQuestion`.\n\n5. **Report.** Summarize fixes applied, comments addressed, comments deferred (with reason), current PR status. Cite each commit by SHA.\n\n## Hard rules\n\n- Don't rewrite history on a branch others may have pulled. If a rebase or force-push looks necessary, clear it with the user first.\n- Don't tweak a test's expected values just to get a pass. Only change an assertion when the behaviour genuinely changed and the assertion was pinned to the old behaviour.\n- Never skip hooks (`--no-verify`).\n- Never bypass a failing check by marking it as not required.\n- `gh pr ready` only when all checks are green and no unresolved review comments remain.\n\n## Cross-refs\n\n- Opening a PR does not start a babysit; inside poteto-mode the Babysit playbook owns the request and starts only when asked.\n- Use `interrogate` before opening if the diff is contested; once open, babysit takes over.\n- Use `unslop` on any prose you write here (PR comments, commit messages, status reports).\n\n## Provenance\n\nThis is a Claude Code analog of Cursor's `\u002Fbabysit`, not a port — Cursor's implementation is closed source. The skill is independently authored, with its own prose and structure; the workflow is informed by Cursor's public `\u002Fbabysit` behavior. The only overlap with other PR tools is the `gh` CLI commands it runs, which are functional invocations rather than copied text.\n","# Babysit a PR\n\nOn Codex, read the [platform mapping](..\u002Fpoteto-mode\u002Freferences\u002Fcodex-tools.md), including its per-skill notes, before following this skill.\n\nOn GitHub Copilot, read the [platform mapping](..\u002Fpoteto-mode\u002Freferences\u002Fcopilot-tools.md), including its per-skill notes, before following this skill.\n\nOn Muse, read the [platform mapping](..\u002Fpoteto-mode\u002Freferences\u002Fmuse-tools.md), including its per-skill notes, before following this skill.\n\nClaude Code analog of Cursor's built-in `\u002Fbabysit`. The implementation is a loop over `gh` CLI plus the Claude Code `loop` skill for pacing.\n\nInside poteto-mode, the **Babysit** playbook ([`..\u002Fpoteto-mode\u002Fplaybooks\u002Fbabysit.md`](..\u002Fpoteto-mode\u002Fplaybooks\u002Fbabysit.md)) supersedes this skill: it owns mode declaration, the merge frontier, stack safety, and the `watch-pr` watcher. This skill stays the standalone `\u002Fbabysit` entry point for a single PR outside a poteto-mode run.\n\n## When to use\n\n- There's an open PR and the user explicitly wants it kept green, and you are not already inside a poteto-mode run (the playbook owns that case).\n- The user invokes `\u002Fbabysit` directly.\n- A subagent that opens a PR does NOT babysit — return to the parent and let the parent decide.\n\n## Steps\n\n1. **Fetch PR state.**\n\n   ```bash\n   gh pr view \u003Cnumber> --json number,title,state,mergeable,reviewDecision,statusCheckRollup,mergeStateStatus,comments,reviews\n   ```\n\n2. **Triage in priority order.**\n   - Merge conflicts (`mergeStateStatus == DIRTY`): run the **fix-merge-conflicts** skill. Force-push only if the branch is yours and not shared.\n   - Failing checks (`statusCheckRollup` entries with `conclusion: FAILURE`): run the **fix-ci** skill. Root-cause the failure; fix the underlying code or test; commit; push.\n   - Review comments: run the **get-pr-comments** skill for the summary, then act only on feedback you actually agree with. When a comment has a single mechanical answer — a rename, a guard clause, a formatting nit — make the edit and quote the comment in the commit message. When it hinges on a judgement call, or you can't tell what's being asked, don't guess: leave it and reply with what you would have done.\n   - Review-bot comments (Bugbot and similar automation): classify fix\u002Fdismiss\u002Fask before acting, per [`bugbot-triage.md`](..\u002Fpoteto-mode\u002Freferences\u002Fbugbot-triage.md). Ask by default on security, data, and high-severity findings.\n\n3. **Loop.** Use the Claude Code `loop` skill to pace re-checks. Pick the interval from what you're watching:\n   - Active CI run: poll `gh pr checks --watch` (it blocks until checks finish, so no separate loop interval needed).\n   - Awaiting reviewer: 20–30 min heartbeat.\n   - Idle but want to catch new comments: hourly.\n\n4. **When to stop.**\n   - Build is green, every comment resolved, branch merges cleanly → call it ready.\n   - You've run three rounds of fix → push → recheck and it still isn't fully green → stop, summarise what's still broken, and hand control back.\n   - The next fix would force a design choice → pause and put it to the user with `AskUserQuestion`.\n\n5. **Report.** Summarize fixes applied, comments addressed, comments deferred (with reason), current PR status. Cite each commit by SHA.\n\n## Hard rules\n\n- Don't rewrite history on a branch others may have pulled. If a rebase or force-push looks necessary, clear it with the user first.\n- Don't tweak a test's expected values just to get a pass. Only change an assertion when the behaviour genuinely changed and the assertion was pinned to the old behaviour.\n- Never skip hooks (`--no-verify`).\n- Never bypass a failing check by marking it as not required.\n- `gh pr ready` only when all checks are green and no unresolved review comments remain.\n\n## Cross-refs\n\n- Opening a PR does not start a babysit; inside poteto-mode the Babysit playbook owns the request and starts only when asked.\n- Use `interrogate` before opening if the diff is contested; once open, babysit takes over.\n- Use `unslop` on any prose you write here (PR comments, commit messages, status reports).\n\n## Provenance\n\nThis is a Claude Code analog of Cursor's `\u002Fbabysit`, not a port — Cursor's implementation is closed source. The skill is independently authored, with its own prose and structure; the workflow is informed by Cursor's public `\u002Fbabysit` behavior. The only overlap with other PR tools is the `gh` CLI commands it runs, which are functional invocations rather than copied text.\n",{"name":5,"description":7},"main","0d3cd5ec21bc09acc255c7f3e790b2b605e08e05","plugins\u002Fpstack\u002Fskills\u002Fbabysit","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0","bismillah","2026-11-10 11:14:55",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add thoriqakbar0\u002Fpstack --skill babysit",{"tool":37,"command":38},"bunx","bunx skills add thoriqakbar0\u002Fpstack --skill babysit",{"tool":40,"command":41},"pnpm","pnpm dlx skills add thoriqakbar0\u002Fpstack --skill babysit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fbabysit\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7F75WF76VEQDWXFYYYM8NTQ","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7F75SBDAE54RR5QXAX4D939","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise update","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fwhat-did-i-get-done\u002FSKILL.md",[],[],{"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":19},"01M7F75QGP7XC377PDZ96CBWVD","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Funslop\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":19},"01M7F75NXH5YRSZ5ZXVTMWM3Y0","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7F75JM31PC9HXGYDQWY6Y1R","thermos","Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug\u002Fsecurity and code-quality branch audits.","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fthermos\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7F75FH0Y9X4MDVXF1QQEM43","thermo-nuclear-review","Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch\u002FPR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.","https:\u002F\u002Fgithub.com\u002Fthoriqakbar0\u002Fpstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fthermo-nuclear-review\u002FSKILL.md",[],[]]