[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARSX01KGR8QJASECTKT8RH":3,"skill-same:01M7ARSX01KGR8QJASECTKT8RH":62},{"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":6,"updatedAt":29,"install":30,"resources":43},"01M7ARSX01KGR8QJASECTKT8RH","babysit-pr",null,"Babysit a PR to ready: review, repairs, CI, and a current-head verdict. Merging belongs to ship.","gutierrezje\u002Fjstack","gutierrezje","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F32502846?v=4","01M7ARSJH934J0XXNJC02Y6PB0","Jesus E. Gutierrez","01M7ARSJJ8PN0AGVX140JK202H",0,"MIT","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Fbabysit-pr\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: babysit-pr\ndescription: \"Babysit a PR to ready: review, repairs, CI, and a current-head verdict. Merging belongs to ship.\"\n---\n\n# Babysit PR\n\nCarry the PR through review, in-scope repairs, required QA, and hosted checks to\na verdict supported by evidence for its current head. `$open-pr` prepares the\nreview presentation; Babysit owns the review and repair cycle.\n\n## User authorization\n\nAn explicit user invocation of `$babysit-pr`, or a direct user request to\nbabysit, shepherd, or finish a PR, authorizes the complete repair loop:\n\n- read the repository and live PR state;\n- make the smallest local changes needed to resolve substantiated blockers;\n- commit those verified, in-scope repairs;\n- non-force push those repairs to the PR's existing head branch and monitor the\n  new head;\n- resolve review threads whose concern is cleared on the current head; and\n- mark that PR ready for review after its current head earns `READY`.\n\nAutomatic model selection of this skill does not grant push authority. An\nexplicit read-only or review-only request also narrows the authorization.\nRequire separate approval for force pushes, rebases that rewrite the remote\nbranch, retargeting or replacing the PR branch, materially broader changes,\npublic replies, closing or reopening the PR, other lifecycle changes, and merge.\n\nStay in the current Codex task. Do not create, message, monitor, or manage other\nuser-visible tasks unless the user explicitly asks. Consume existing reviewer or\nhandoff results as evidence, and do not start a duplicate reviewer for a frozen\nscope that already has an adequate completed or running review.\n\nWhen selected QA requires video, follow the\n[video evidence contract](..\u002Fjesus-mode\u002Freferences\u002Fvideo-evidence.md). Keep\noptional demonstration clips separate from required acceptance evidence.\n\nTrack repairs, reviews, QA, and verification using the\n[model contributions contract](..\u002Fopen-pr\u002FSKILL.md#model-contributions).\nBefore issuing a verdict, refresh the PR's model contributions record when body\nedits are authorized; otherwise include the proposed update in the handoff.\n\n## Workflow\n\n1. Capture repository and PR identity, base and head SHAs, worktree state,\n   linked acceptance criteria, changed user journeys, checks, mergeability,\n   draft state, and review threads. Use the\n   [GitHub transport contract](..\u002Fjesus-mode\u002Freferences\u002Fcodex-compatibility.md#github-transport).\n   Keep issue numbers, PR numbers, and branch names distinct. Refresh the\n   snapshot after every push.\n2. Read existing review receipts and apply the\n   [DiffOwl coverage contract](..\u002Fjesus-mode\u002Freferences\u002Fdiffowl.md), the authority\n   for full reviews, repair coverage, reuse, and independent review. Inspect\n   comments with their threads, replies, resolution state, and current code;\n   group duplicate findings and treat each as a claim to verify.\n3. When findings need disposition or a repair is required, follow\n   [repairs and review threads](references\u002Frepairs.md). Continue until the\n   substantiated blockers are resolved or a specific authority or dependency\n   prevents further progress.\n4. For changed user-visible journeys, follow\n   [real-surface QA](references\u002Freal-surface-qa.md). Otherwise record why that QA\n   does not apply. Missing required evidence remains a gap.\n5. Verify hosted checks as described below. Fix in-scope failures and refresh\n   affected evidence after repairs.\n6. Before issuing a verdict or changing draft state, follow\n   [acceptance](references\u002Facceptance.md). Recheck the live PR and return the\n   shared coverage receipt plus current QA, checks, feedback, and mergeability.\n\n## Hosted checks\n\nUse `gh pr checks \u003Cnumber>` or the equivalent platform view as the source of truth\nfor the entire PR-attached check set. Enumerate every check at the current head,\nuse native wait\u002Fwatch or product automation for unsettled checks, and classify\neach failure with platform evidence. Separate branch-caused failures from\ninfrastructure or provider flakes; do not dismiss a failure as a flake without\nevidence or an authorized resolution. Never encode a fixed polling loop or stale\ncheck list in the workflow.\n\n## Completion\n\nFinish with `READY` only when acceptance passes for the current head and the PR\nis open for review. Use `NOT READY` for established blockers and `INCONCLUSIVE`\nfor missing or unsettled evidence. Keep working while useful, authorized repairs\nor pending checks can resolve the verdict. When blocked, report the exact missing\nauthority, dependency, or evidence and the completed work.\n","# Babysit PR\n\nCarry the PR through review, in-scope repairs, required QA, and hosted checks to\na verdict supported by evidence for its current head. `$open-pr` prepares the\nreview presentation; Babysit owns the review and repair cycle.\n\n## User authorization\n\nAn explicit user invocation of `$babysit-pr`, or a direct user request to\nbabysit, shepherd, or finish a PR, authorizes the complete repair loop:\n\n- read the repository and live PR state;\n- make the smallest local changes needed to resolve substantiated blockers;\n- commit those verified, in-scope repairs;\n- non-force push those repairs to the PR's existing head branch and monitor the\n  new head;\n- resolve review threads whose concern is cleared on the current head; and\n- mark that PR ready for review after its current head earns `READY`.\n\nAutomatic model selection of this skill does not grant push authority. An\nexplicit read-only or review-only request also narrows the authorization.\nRequire separate approval for force pushes, rebases that rewrite the remote\nbranch, retargeting or replacing the PR branch, materially broader changes,\npublic replies, closing or reopening the PR, other lifecycle changes, and merge.\n\nStay in the current Codex task. Do not create, message, monitor, or manage other\nuser-visible tasks unless the user explicitly asks. Consume existing reviewer or\nhandoff results as evidence, and do not start a duplicate reviewer for a frozen\nscope that already has an adequate completed or running review.\n\nWhen selected QA requires video, follow the\n[video evidence contract](..\u002Fjesus-mode\u002Freferences\u002Fvideo-evidence.md). Keep\noptional demonstration clips separate from required acceptance evidence.\n\nTrack repairs, reviews, QA, and verification using the\n[model contributions contract](..\u002Fopen-pr\u002FSKILL.md#model-contributions).\nBefore issuing a verdict, refresh the PR's model contributions record when body\nedits are authorized; otherwise include the proposed update in the handoff.\n\n## Workflow\n\n1. Capture repository and PR identity, base and head SHAs, worktree state,\n   linked acceptance criteria, changed user journeys, checks, mergeability,\n   draft state, and review threads. Use the\n   [GitHub transport contract](..\u002Fjesus-mode\u002Freferences\u002Fcodex-compatibility.md#github-transport).\n   Keep issue numbers, PR numbers, and branch names distinct. Refresh the\n   snapshot after every push.\n2. Read existing review receipts and apply the\n   [DiffOwl coverage contract](..\u002Fjesus-mode\u002Freferences\u002Fdiffowl.md), the authority\n   for full reviews, repair coverage, reuse, and independent review. Inspect\n   comments with their threads, replies, resolution state, and current code;\n   group duplicate findings and treat each as a claim to verify.\n3. When findings need disposition or a repair is required, follow\n   [repairs and review threads](references\u002Frepairs.md). Continue until the\n   substantiated blockers are resolved or a specific authority or dependency\n   prevents further progress.\n4. For changed user-visible journeys, follow\n   [real-surface QA](references\u002Freal-surface-qa.md). Otherwise record why that QA\n   does not apply. Missing required evidence remains a gap.\n5. Verify hosted checks as described below. Fix in-scope failures and refresh\n   affected evidence after repairs.\n6. Before issuing a verdict or changing draft state, follow\n   [acceptance](references\u002Facceptance.md). Recheck the live PR and return the\n   shared coverage receipt plus current QA, checks, feedback, and mergeability.\n\n## Hosted checks\n\nUse `gh pr checks \u003Cnumber>` or the equivalent platform view as the source of truth\nfor the entire PR-attached check set. Enumerate every check at the current head,\nuse native wait\u002Fwatch or product automation for unsettled checks, and classify\neach failure with platform evidence. Separate branch-caused failures from\ninfrastructure or provider flakes; do not dismiss a failure as a flake without\nevidence or an authorized resolution. Never encode a fixed polling loop or stale\ncheck list in the workflow.\n\n## Completion\n\nFinish with `READY` only when acceptance passes for the current head and the PR\nis open for review. Use `NOT READY` for established blockers and `INCONCLUSIVE`\nfor missing or unsettled evidence. Keep working while useful, authorized repairs\nor pending checks can resolve the verdict. When blocked, report the exact missing\nauthority, dependency, or evidence and the completed work.\n",{"name":5,"description":7},"main","bbac2ca2c2f494880dc8aa5d58dc4f768501f290","skills\u002Fbabysit-pr","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack","https:\u002F\u002Fgithub.com\u002Fgutierrezje","2026-11-11 14:57:12",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add gutierrezje\u002Fjstack --skill babysit-pr",{"tool":36,"command":37},"bunx","bunx skills add gutierrezje\u002Fjstack --skill babysit-pr",{"tool":39,"command":40},"pnpm","pnpm dlx skills add gutierrezje\u002Fjstack --skill babysit-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Fbabysit-pr\u002FSKILL.md",true,[44,50,54,58],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",260,"https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Fbabysit-pr\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Facceptance.md",2268,"https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Fbabysit-pr\u002Freferences\u002Facceptance.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Freal-surface-qa.md",2278,"https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Fbabysit-pr\u002Freferences\u002Freal-surface-qa.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Frepairs.md",1958,"https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Fbabysit-pr\u002Freferences\u002Frepairs.md",[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7ARWNBDTFSVCHWFQ4BYWQSX","why","Why code is this way: design rationale, regressions, and history from evidence. For runtime: how.","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7ARWKP5P795ZTFRJQJNK9ZK","unslop","Edit prose to remove AI writing patterns when polishing text or asked to make it sound natural.","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7ARWG34VZRC0FZTP4Z1VXFH","typescript-best-practices","Use when writing or reviewing .ts\u002F.tsx code: types, validation boundaries, and API signatures.","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7ARWBBKAMRHVJH929D2TSW1","sync-pstack","Analyze upstream cursor\u002Fplugins pstack changes and guide semantic ports into Codex-native Jstack without overwriting local skills. Use when the user says \"sync pstack\", \"check pstack updates\", or asks to update Jstack from upstream.","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Fsync-pstack\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7ARW853DBZYE9ETT0ZZHP9J","swarm","Fan out N parallel workers, drain them, and return one report. Use for \u002Fswarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Fswarm\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7ARW5Y0CMDJCAJ1P3KKBDV8","statechart","Check a finite TLA+ model and explain its paths and rule failures as a statechart.","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Fstatechart\u002FSKILL.md",[],[]]