[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4MPYTEE2SHYDWRC5KJAVR":3,"skill-same:01M7F4MPYTEE2SHYDWRC5KJAVR":97},{"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},"01M7F4MPYTEE2SHYDWRC5KJAVR","babysit",null,"Babysit an opened pull request through checks and review to merge or its prescribed handoff. Use right after opening a pull request, or when asked to babysit or land one.","lutzseverino\u002Fpostern","lutzseverino","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28309837?v=4","01M77NN0YKH0YYGY7W7ER23MX0","Jasper","01M7F4MESFQZ45SVN7DQD7Y8D4",0,"MIT","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbabysit\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: babysit\ndescription: Babysit an opened pull request through checks and review to merge or its prescribed handoff. Use right after opening a pull request, or when asked to babysit or land one.\n---\n\nA prompt or brief naming this skill is its invocation.\n\nTake the PR through authorized delivery under `CONTRIBUTING.md` and the\n`github-repository-configuration` merge rules. Before each post, read the\n`.repo-standards\u002Frules\u002Fcomments.md` section named by its step.\n\nBefore requesting or waiting, establish your role from `CONTRIBUTING.md`'s\nMerging section and applicable installed rules. Record any prescribed worker\nhandoff on the open PR under `.repo-standards\u002Frules\u002Fcomments.md#delivery-records`\nand stop. The designated merging agent resumes with its review requirements\nand outstanding findings. For an owner-question pause, follow installed\ncontinuation rules before request and wait. For authorized delivery of a\nstopped run's open PR, enter Branch-update recovery first, using this\ninvocation's branch update. Carry the handoff context and follow installed\nrules for retaining its waiting marker and recording the merge outcome.\n\nThe bundled scripts require Node.js 24 or 26. Request and wait read optional\n`.github\u002Fpull-request-reviewer.json` and `.github\u002Ffactory-review-policy.json`\nunder the `github-repository-configuration` rules' Trusted review configuration:\nboth files come from one pinned destination default-branch full SHA, retained\nacross wait polls and head changes. Each outcome identifies repository and revision.\nProposed changes apply only after merging to that default branch. No reviewer\nfile means checks only, unless app-author policy identifies a review skip;\nno policy means configured reviewer behavior, without an owner question.\nInvalid trusted declarations, including a plain human-login policy author,\nrequire the owner handoff (exit `7`, below).\n\nBefore the first wait and each later or resumed head, run\n`node \u003Cthis skill's directory>\u002Frequest.mjs \u003Cnumber>` from the repository root.\nIt applies app-author policy before the rules' review request rule, posting\nany required request under step 4 or reporting why none is needed. Add\n`--fixes-review` when the head fixes a finding requiring a new request.\nExit `0` means the rule was applied, not that review occurred; `1` and `7`\nuse the wait's error and owner-handoff actions below.\n\nRequest and wait read the paginated ready-for-review history when automatic\nopening requests are enabled. They apply the rules' effective request time to\nbounds and head freshness while retaining the original completion and\nunavailability evidence cutoffs. Polls and resumed invocations use platform\ntimestamps, including when the PR has returned to draft.\n\nRequest checks the PR body's own-head file links before any request or policy\nskip. Exit `8` lists links to replace with commit-SHA links; correct the body\nand rerun request before waiting. It never rewrites the body; external\nrepositories and other branches are outside this check.\n\nFor an adoption-summary exemption, request rebuilds pre-commit state in a\ntemporary detached worktree outside the author's checkout at\n`merge-base(\u003CPR base commit>, \u003Chead>)`, restores the exact head tree with\n`git restore --source=\u003Chead> --worktree :\u002F`, runs\n`npm ci --ignore-scripts --prefix .repo-standards\u002Fruntime` there, then runs the\nhead's pinned `.repo-standards\u002Fruntime\u002Fnode_modules\u002F.bin\u002Frepo-standards status --summary`.\nIt removes the temporary worktree on success and failure. Only a complete,\nbyte-exact leading match of that stdout is exempt, including its final newline\nand generated Impact and Migration. Every appended section is checked. Missing\nlocal commits or runtime, failed reconstruction\u002Finstall\u002Fgeneration, and a\nmismatching prefix grant no exemption: the diagnostic explains why the whole\nbody was checked. Link-free bodies need no reconstruction.\n\n1. Run `node \u003Cthis skill's directory>\u002Fwait.mjs \u003Cnumber>` from the repository\n   root in the foreground until it exits. It silently waits for checks and the\n   configured reviewer's review of the head. Use a 600000 ms command timeout\n   where supported and ask for the longest wait whenever it yields.\n   Wait requires positive current-head success for every name in trusted\n   `.github\u002Frequired-checks.json`; no-check timeouts never qualify.\n\n   | Exit | Outcome and action |\n   | --- | --- |\n   | `0` | Checks passed; reviewer reviewed or none configured. Go to step 2. |\n   | `2` | Listed checks failed. Go to step 2. |\n   | `3`, `4` | Checks passed; reviewer did not review this head (`3`: unavailable; `4`: reason in output). Go to step 2; apply the rules for merging without review and record its absence under `.repo-standards\u002Frules\u002Fcomments.md#delivery-records`. |\n   | `5` | Still waiting; rerun wait. |\n   | `6` | Checks passed; app-author policy skipped external review. Go to step 2; after both internal reviews, read `.repo-standards\u002Frules\u002Fcomments.md#reviews`, fill every placeholder in the printed full-head template and post it as a PR review. An unfilled template is not completed evidence. |\n   | `7` | Invalid trusted configuration. Post an owner question under `.repo-standards\u002Frules\u002Fcomments.md#owner-questions`, naming the diagnostic's destination repository, selected revision, declaration, validation problem and needed correction. Follow installed continuation rules, leave the PR open and stop babysitting; no unchanged-configuration retry or merge. |\n   | `1` | For permission refusal, follow `CONTRIBUTING.md`'s Credentials section; otherwise fix the invocation or platform error and rerun. |\n\n2. Verify each failing check and review finding against the source, including\n   findings that arrive on a policy-skipped pull request. Follow the\n   `github-repository-configuration` rules for applicable internal Standards and\n   Spec reviews, posting each round as\n   `.repo-standards\u002Frules\u002Fcomments.md#reviews` says.\n3. Fix the real findings `CONTRIBUTING.md` does not let you decline, and answer\n   every review thread as it requires. Before replying, read\n   `.repo-standards\u002Frules\u002Fcomments.md#review-thread-replies`.\n4. After a fix push, apply the review request rule to the new head using\n   `request.mjs` as above, with app-author policy taking precedence. Post any\n   required request under `.repo-standards\u002Frules\u002Fcomments.md#review-request-comments`.\n   After any push or re-request, return to step 1.\n5. Before each merge attempt, verify merge ownership and any required owner\n   approval against the current head under the applicable installed rules.\n   Read the authoritative implementation contract and any worker handoff and\n   apply the `github-repository-configuration` rules' Designated owner review gate.\n   Read PR comments carrying designation provenance and current-head approval;\n   record approval there under `.repo-standards\u002Frules\u002Fcomments.md#delivery-records`.\n   Missing required approval means the guide's owner-question handoff under\n   `.repo-standards\u002Frules\u002Fcomments.md#owner-questions`; stop with the\n   PR unmerged. Once merge conditions hold on the latest head, run\n   `node \u003Cthis skill's directory>\u002Fmerge.mjs \u003Cnumber> \u003CSHA>`, where `\u003CSHA>` is\n   the full SHA that starts the wait's latest line:\n\n   | Exit | Outcome and action |\n   | --- | --- |\n   | `0` | Merged. Record any installed-rule-required outcome under `.repo-standards\u002Frules\u002Fcomments.md#delivery-records`: delivered head, validation\u002Freview results and printed merge commit SHA. |\n   | `2` | Head changed or current-head validation has not succeeded. Return to step 1. |\n   | `3` | Not merged; owner needed. Hand off under `.repo-standards\u002Frules\u002Fcomments.md#owner-questions`, without retrying merge. |\n   | `4` | Stale base. Enter Branch-update recovery if this invocation has not used its branch update; otherwise record the owner handoff and stop. |\n   | `5` | Current-head policy-skip review missing\u002Fincomplete. Complete both internal reviews, post under `.repo-standards\u002Frules\u002Fcomments.md#reviews` using wait's full-head template, verify other merge conditions and rerun merge. No owner handoff. |\n   | `6` | Configured-reviewer threads remain unresolved. Resolve them on the platform, verify the other gates and rerun merge. Replies alone do not resolve threads. |\n   | `9` | Another open issue\u002FPR has the repository-hold label, or another open PR has the release-hold label. Leave this PR open; retry only after the hold ends. Factory runs end for factory relaunch after the hold; other runs rerun merge after it ends. No owner handoff. |\n   | `1` | For permission refusal, follow `CONTRIBUTING.md`'s Credentials section; otherwise fix the invocation or platform error and rerun. |\n6. Stop.\n\nWait and merge require `.github\u002Frequired-checks.json` from the pinned trusted\ndefault branch; absent, invalid or unreadable declarations refuse delivery.\nCorrect the declaration on that trusted branch through the applicable owner\nprocedure, then invoke again. Local or PR-branch files supply no bootstrap bypass.\nMerge independently checks every declared name for positive current-head success\nand all configured-reviewer threads for resolution, on both freshness paths.\nUnreadable or incomplete check\u002Fthread evidence permits no merge. After slow\ngates it rechecks the head, live destination and current-base ancestry.\n\nThe merge command independently resolves trusted review configuration and checks\nthe platform PR author on every invocation, even without a prior wait. Invalid\ntrusted declarations require its owner-handoff exit `3`; unreadable review\nconfiguration returns `1` and permits no merge. A prior wait result and proposed\nPR-branch policy cannot bypass the outcome check.\nImmediately before its merge write, it reads `labels.hold` and\n`labels.releaseHold` from\n`.scriptorium\u002Fconfig.json` at that same destination default-branch snapshot and\nlists open issues and PRs for the repository hold and open PRs for the release\nhold, excluding only the PR being merged. An absent file or key adds no hold. Unreadable or invalid configuration or issue\u002FPR reads\npermit no merge write and follow the freshness-read failure handling.\n\n## Branch-update recovery\n\nEvery owner handoff in this section and in step 5 posts its question as\n`.repo-standards\u002Frules\u002Fcomments.md#owner-questions` says.\n\nFollow the `github-repository-configuration` rules' Required-check freshness\nsection: strict non-bypassable GitHub enforcement wherever available; only\nrecognized plan-limit 403s for both classic protection and rulesets on a private\nrepository permit merging-agent verification. After slow gates, immediately\nbefore expected-head merge, verify the live default destination, unchanged\nvalidated\u002Freviewed head, successful applicable validation on that exact head\nand current default-tip ancestry. Missing\u002Funreadable evidence, ordinary\npermission refusals, missing workflow and deferred setup grant no exception.\nOnly on this proven plan-limited path does the owner accept the concurrent-base\nrace: another writer may advance the base after verification and merge can succeed. Immediate\nchecks narrow that window without GitHub's atomic protection. Exit `4` means\nstale base, distinct from head change or owner-only failure; no merge succeeded.\n\nThe same section bounds recovery and says what it never does. Preserve committed,\nstaged, unstaged and untracked work and the PR's review and handoff context\nbefore changing history. Fetch origin, resolve its remote default branch again,\nand inspect outgoing history (including each merge parent) and the whole diff.\nRebase or replay only this PR's work onto the refreshed base; keep unrelated\nwork preserved separately. Uncertain ownership or reconstruction conflicts\nrequire the owner handoff.\n\nValidate the integrated change with the repository's required local checks;\nwait for their final successful status before pushing with an explicit lease\nwhen history changed. Before the delivery push, refresh origin and its default\nbranch again and inspect both `git log --stat --patch -m origin\u002FHEAD..HEAD`\nand `git diff origin\u002FHEAD...HEAD`. Revalidate after any further reconstruction.\nA permission refusal ends recovery under Credentials, without another push.\n\nFor the replacement head, repeat applicable internal reviews and owner approval,\nthen request and wait again from step 1 under freshly applied trusted app-author\npolicy. Pending\u002Ffailed checks permit no merge; old-head checks never qualify it.\nRe-establish merge ownership before step 5. Finish each waiting PR's delivery\nbefore the next, refreshing each base independently.\n\nFor either command's exit `7`, follow correction and authorized continuation\nunder the rules' Trusted review configuration section.\n\n## Reads\n\nPaths are relative to the repository root.\n\n- `CONTRIBUTING.md`: the merge conditions and the Merging, Owner questions and\n  Credentials sections the steps name. When it is missing, carry out the\n  steps and the commands' own checks as written, and hand off to the owner in\n  one PR comment for any rule the steps leave to the guide.\n- `.repo-standards\u002Frules\u002Fcomments.md`: the installed comment rules, whose\n  sections the steps name before each post. When it is missing, post each\n  record or question the steps name as one comment, and each review in the\n  shape the wait prints.\n- The installed rules the steps name, such as the\n  `github-repository-configuration` rules, which the `repository-standards`\n  skill looks up. When they are missing, the commands' own behavior stands, no\n  rule prescribes a worker handoff, owner approval or merge outcome record,\n  and `CONTRIBUTING.md` alone sets the merge rules.\n- `.github\u002Frequired-checks.json`: the required-name authority for wait and merge.\n  Missing, invalid or unreadable at the selected trusted commit stops delivery\n  and requires correction on the destination default branch before reinvocation.\n- `.github\u002Fpull-request-reviewer.json`: the optional reviewer declaration.\n  When it is missing at the selected commit, no reviewer is configured.\n- `.github\u002Ffactory-review-policy.json`: the optional app-author review policy.\n  When it is missing at the selected commit, configured reviewer behavior\n  applies.\n- `.github\u002Fworkflows\u002Fpr-metadata.yml`: the workflow whose presence the merge\n  command verifies on the live default branch for plan-limited delivery. When\n  missing or unreadable, that path permits no merge.\n- `.scriptorium\u002Fconfig.json`: its `labels.hold` and `labels.releaseHold`, which the\n  merge command reads. When the file or a key is missing, that hold does not apply.\n- `.repo-standards\u002Fruntime\u002F`: the pinned Repository Standards runtime, its\n  `package-lock.json` and `node_modules\u002F.bin\u002Frepo-standards`, which the\n  request command uses to rebuild an adoption summary. When it is missing, no\n  link is exempt as part of an adoption summary.\n- `vendor\u002Fpostern\u002Fpostern.mjs`, `vendor\u002Fmarked\u002Fmarked.esm.js` and\n  `vendor\u002Fparse5\u002Fparse5.esm.js`: the bundles the commands import, which Repo\n  Canon's adoption installs. When they are missing, the commands cannot start:\n  carry out each step by hand with the GitHub CLI under the same rules, and\n  squash-merge with the subject `\u003Ctitle> (#\u003Cnumber>)` and the PR body passed\n  explicitly.\n","A prompt or brief naming this skill is its invocation.\n\nTake the PR through authorized delivery under `CONTRIBUTING.md` and the\n`github-repository-configuration` merge rules. Before each post, read the\n`.repo-standards\u002Frules\u002Fcomments.md` section named by its step.\n\nBefore requesting or waiting, establish your role from `CONTRIBUTING.md`'s\nMerging section and applicable installed rules. Record any prescribed worker\nhandoff on the open PR under `.repo-standards\u002Frules\u002Fcomments.md#delivery-records`\nand stop. The designated merging agent resumes with its review requirements\nand outstanding findings. For an owner-question pause, follow installed\ncontinuation rules before request and wait. For authorized delivery of a\nstopped run's open PR, enter Branch-update recovery first, using this\ninvocation's branch update. Carry the handoff context and follow installed\nrules for retaining its waiting marker and recording the merge outcome.\n\nThe bundled scripts require Node.js 24 or 26. Request and wait read optional\n`.github\u002Fpull-request-reviewer.json` and `.github\u002Ffactory-review-policy.json`\nunder the `github-repository-configuration` rules' Trusted review configuration:\nboth files come from one pinned destination default-branch full SHA, retained\nacross wait polls and head changes. Each outcome identifies repository and revision.\nProposed changes apply only after merging to that default branch. No reviewer\nfile means checks only, unless app-author policy identifies a review skip;\nno policy means configured reviewer behavior, without an owner question.\nInvalid trusted declarations, including a plain human-login policy author,\nrequire the owner handoff (exit `7`, below).\n\nBefore the first wait and each later or resumed head, run\n`node \u003Cthis skill's directory>\u002Frequest.mjs \u003Cnumber>` from the repository root.\nIt applies app-author policy before the rules' review request rule, posting\nany required request under step 4 or reporting why none is needed. Add\n`--fixes-review` when the head fixes a finding requiring a new request.\nExit `0` means the rule was applied, not that review occurred; `1` and `7`\nuse the wait's error and owner-handoff actions below.\n\nRequest and wait read the paginated ready-for-review history when automatic\nopening requests are enabled. They apply the rules' effective request time to\nbounds and head freshness while retaining the original completion and\nunavailability evidence cutoffs. Polls and resumed invocations use platform\ntimestamps, including when the PR has returned to draft.\n\nRequest checks the PR body's own-head file links before any request or policy\nskip. Exit `8` lists links to replace with commit-SHA links; correct the body\nand rerun request before waiting. It never rewrites the body; external\nrepositories and other branches are outside this check.\n\nFor an adoption-summary exemption, request rebuilds pre-commit state in a\ntemporary detached worktree outside the author's checkout at\n`merge-base(\u003CPR base commit>, \u003Chead>)`, restores the exact head tree with\n`git restore --source=\u003Chead> --worktree :\u002F`, runs\n`npm ci --ignore-scripts --prefix .repo-standards\u002Fruntime` there, then runs the\nhead's pinned `.repo-standards\u002Fruntime\u002Fnode_modules\u002F.bin\u002Frepo-standards status --summary`.\nIt removes the temporary worktree on success and failure. Only a complete,\nbyte-exact leading match of that stdout is exempt, including its final newline\nand generated Impact and Migration. Every appended section is checked. Missing\nlocal commits or runtime, failed reconstruction\u002Finstall\u002Fgeneration, and a\nmismatching prefix grant no exemption: the diagnostic explains why the whole\nbody was checked. Link-free bodies need no reconstruction.\n\n1. Run `node \u003Cthis skill's directory>\u002Fwait.mjs \u003Cnumber>` from the repository\n   root in the foreground until it exits. It silently waits for checks and the\n   configured reviewer's review of the head. Use a 600000 ms command timeout\n   where supported and ask for the longest wait whenever it yields.\n   Wait requires positive current-head success for every name in trusted\n   `.github\u002Frequired-checks.json`; no-check timeouts never qualify.\n\n   | Exit | Outcome and action |\n   | --- | --- |\n   | `0` | Checks passed; reviewer reviewed or none configured. Go to step 2. |\n   | `2` | Listed checks failed. Go to step 2. |\n   | `3`, `4` | Checks passed; reviewer did not review this head (`3`: unavailable; `4`: reason in output). Go to step 2; apply the rules for merging without review and record its absence under `.repo-standards\u002Frules\u002Fcomments.md#delivery-records`. |\n   | `5` | Still waiting; rerun wait. |\n   | `6` | Checks passed; app-author policy skipped external review. Go to step 2; after both internal reviews, read `.repo-standards\u002Frules\u002Fcomments.md#reviews`, fill every placeholder in the printed full-head template and post it as a PR review. An unfilled template is not completed evidence. |\n   | `7` | Invalid trusted configuration. Post an owner question under `.repo-standards\u002Frules\u002Fcomments.md#owner-questions`, naming the diagnostic's destination repository, selected revision, declaration, validation problem and needed correction. Follow installed continuation rules, leave the PR open and stop babysitting; no unchanged-configuration retry or merge. |\n   | `1` | For permission refusal, follow `CONTRIBUTING.md`'s Credentials section; otherwise fix the invocation or platform error and rerun. |\n\n2. Verify each failing check and review finding against the source, including\n   findings that arrive on a policy-skipped pull request. Follow the\n   `github-repository-configuration` rules for applicable internal Standards and\n   Spec reviews, posting each round as\n   `.repo-standards\u002Frules\u002Fcomments.md#reviews` says.\n3. Fix the real findings `CONTRIBUTING.md` does not let you decline, and answer\n   every review thread as it requires. Before replying, read\n   `.repo-standards\u002Frules\u002Fcomments.md#review-thread-replies`.\n4. After a fix push, apply the review request rule to the new head using\n   `request.mjs` as above, with app-author policy taking precedence. Post any\n   required request under `.repo-standards\u002Frules\u002Fcomments.md#review-request-comments`.\n   After any push or re-request, return to step 1.\n5. Before each merge attempt, verify merge ownership and any required owner\n   approval against the current head under the applicable installed rules.\n   Read the authoritative implementation contract and any worker handoff and\n   apply the `github-repository-configuration` rules' Designated owner review gate.\n   Read PR comments carrying designation provenance and current-head approval;\n   record approval there under `.repo-standards\u002Frules\u002Fcomments.md#delivery-records`.\n   Missing required approval means the guide's owner-question handoff under\n   `.repo-standards\u002Frules\u002Fcomments.md#owner-questions`; stop with the\n   PR unmerged. Once merge conditions hold on the latest head, run\n   `node \u003Cthis skill's directory>\u002Fmerge.mjs \u003Cnumber> \u003CSHA>`, where `\u003CSHA>` is\n   the full SHA that starts the wait's latest line:\n\n   | Exit | Outcome and action |\n   | --- | --- |\n   | `0` | Merged. Record any installed-rule-required outcome under `.repo-standards\u002Frules\u002Fcomments.md#delivery-records`: delivered head, validation\u002Freview results and printed merge commit SHA. |\n   | `2` | Head changed or current-head validation has not succeeded. Return to step 1. |\n   | `3` | Not merged; owner needed. Hand off under `.repo-standards\u002Frules\u002Fcomments.md#owner-questions`, without retrying merge. |\n   | `4` | Stale base. Enter Branch-update recovery if this invocation has not used its branch update; otherwise record the owner handoff and stop. |\n   | `5` | Current-head policy-skip review missing\u002Fincomplete. Complete both internal reviews, post under `.repo-standards\u002Frules\u002Fcomments.md#reviews` using wait's full-head template, verify other merge conditions and rerun merge. No owner handoff. |\n   | `6` | Configured-reviewer threads remain unresolved. Resolve them on the platform, verify the other gates and rerun merge. Replies alone do not resolve threads. |\n   | `9` | Another open issue\u002FPR has the repository-hold label, or another open PR has the release-hold label. Leave this PR open; retry only after the hold ends. Factory runs end for factory relaunch after the hold; other runs rerun merge after it ends. No owner handoff. |\n   | `1` | For permission refusal, follow `CONTRIBUTING.md`'s Credentials section; otherwise fix the invocation or platform error and rerun. |\n6. Stop.\n\nWait and merge require `.github\u002Frequired-checks.json` from the pinned trusted\ndefault branch; absent, invalid or unreadable declarations refuse delivery.\nCorrect the declaration on that trusted branch through the applicable owner\nprocedure, then invoke again. Local or PR-branch files supply no bootstrap bypass.\nMerge independently checks every declared name for positive current-head success\nand all configured-reviewer threads for resolution, on both freshness paths.\nUnreadable or incomplete check\u002Fthread evidence permits no merge. After slow\ngates it rechecks the head, live destination and current-base ancestry.\n\nThe merge command independently resolves trusted review configuration and checks\nthe platform PR author on every invocation, even without a prior wait. Invalid\ntrusted declarations require its owner-handoff exit `3`; unreadable review\nconfiguration returns `1` and permits no merge. A prior wait result and proposed\nPR-branch policy cannot bypass the outcome check.\nImmediately before its merge write, it reads `labels.hold` and\n`labels.releaseHold` from\n`.scriptorium\u002Fconfig.json` at that same destination default-branch snapshot and\nlists open issues and PRs for the repository hold and open PRs for the release\nhold, excluding only the PR being merged. An absent file or key adds no hold. Unreadable or invalid configuration or issue\u002FPR reads\npermit no merge write and follow the freshness-read failure handling.\n\n## Branch-update recovery\n\nEvery owner handoff in this section and in step 5 posts its question as\n`.repo-standards\u002Frules\u002Fcomments.md#owner-questions` says.\n\nFollow the `github-repository-configuration` rules' Required-check freshness\nsection: strict non-bypassable GitHub enforcement wherever available; only\nrecognized plan-limit 403s for both classic protection and rulesets on a private\nrepository permit merging-agent verification. After slow gates, immediately\nbefore expected-head merge, verify the live default destination, unchanged\nvalidated\u002Freviewed head, successful applicable validation on that exact head\nand current default-tip ancestry. Missing\u002Funreadable evidence, ordinary\npermission refusals, missing workflow and deferred setup grant no exception.\nOnly on this proven plan-limited path does the owner accept the concurrent-base\nrace: another writer may advance the base after verification and merge can succeed. Immediate\nchecks narrow that window without GitHub's atomic protection. Exit `4` means\nstale base, distinct from head change or owner-only failure; no merge succeeded.\n\nThe same section bounds recovery and says what it never does. Preserve committed,\nstaged, unstaged and untracked work and the PR's review and handoff context\nbefore changing history. Fetch origin, resolve its remote default branch again,\nand inspect outgoing history (including each merge parent) and the whole diff.\nRebase or replay only this PR's work onto the refreshed base; keep unrelated\nwork preserved separately. Uncertain ownership or reconstruction conflicts\nrequire the owner handoff.\n\nValidate the integrated change with the repository's required local checks;\nwait for their final successful status before pushing with an explicit lease\nwhen history changed. Before the delivery push, refresh origin and its default\nbranch again and inspect both `git log --stat --patch -m origin\u002FHEAD..HEAD`\nand `git diff origin\u002FHEAD...HEAD`. Revalidate after any further reconstruction.\nA permission refusal ends recovery under Credentials, without another push.\n\nFor the replacement head, repeat applicable internal reviews and owner approval,\nthen request and wait again from step 1 under freshly applied trusted app-author\npolicy. Pending\u002Ffailed checks permit no merge; old-head checks never qualify it.\nRe-establish merge ownership before step 5. Finish each waiting PR's delivery\nbefore the next, refreshing each base independently.\n\nFor either command's exit `7`, follow correction and authorized continuation\nunder the rules' Trusted review configuration section.\n\n## Reads\n\nPaths are relative to the repository root.\n\n- `CONTRIBUTING.md`: the merge conditions and the Merging, Owner questions and\n  Credentials sections the steps name. When it is missing, carry out the\n  steps and the commands' own checks as written, and hand off to the owner in\n  one PR comment for any rule the steps leave to the guide.\n- `.repo-standards\u002Frules\u002Fcomments.md`: the installed comment rules, whose\n  sections the steps name before each post. When it is missing, post each\n  record or question the steps name as one comment, and each review in the\n  shape the wait prints.\n- The installed rules the steps name, such as the\n  `github-repository-configuration` rules, which the `repository-standards`\n  skill looks up. When they are missing, the commands' own behavior stands, no\n  rule prescribes a worker handoff, owner approval or merge outcome record,\n  and `CONTRIBUTING.md` alone sets the merge rules.\n- `.github\u002Frequired-checks.json`: the required-name authority for wait and merge.\n  Missing, invalid or unreadable at the selected trusted commit stops delivery\n  and requires correction on the destination default branch before reinvocation.\n- `.github\u002Fpull-request-reviewer.json`: the optional reviewer declaration.\n  When it is missing at the selected commit, no reviewer is configured.\n- `.github\u002Ffactory-review-policy.json`: the optional app-author review policy.\n  When it is missing at the selected commit, configured reviewer behavior\n  applies.\n- `.github\u002Fworkflows\u002Fpr-metadata.yml`: the workflow whose presence the merge\n  command verifies on the live default branch for plan-limited delivery. When\n  missing or unreadable, that path permits no merge.\n- `.scriptorium\u002Fconfig.json`: its `labels.hold` and `labels.releaseHold`, which the\n  merge command reads. When the file or a key is missing, that hold does not apply.\n- `.repo-standards\u002Fruntime\u002F`: the pinned Repository Standards runtime, its\n  `package-lock.json` and `node_modules\u002F.bin\u002Frepo-standards`, which the\n  request command uses to rebuild an adoption summary. When it is missing, no\n  link is exempt as part of an adoption summary.\n- `vendor\u002Fpostern\u002Fpostern.mjs`, `vendor\u002Fmarked\u002Fmarked.esm.js` and\n  `vendor\u002Fparse5\u002Fparse5.esm.js`: the bundles the commands import, which Repo\n  Canon's adoption installs. When they are missing, the commands cannot start:\n  carry out each step by hand with the GitHub CLI under the same rules, and\n  squash-merge with the subject `\u003Ctitle> (#\u003Cnumber>)` and the PR body passed\n  explicitly.\n",{"name":5,"description":7},"main","448e2ed8cdf04967d08e8f682dbcb135896c8185",".agents\u002Fskills\u002Fbabysit","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern","https:\u002F\u002Fgithub.com\u002Flutzseverino","If Codex could write profile bios, you wouldn't be reading this. Or would you?","2026-11-15 01:04:49",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add lutzseverino\u002Fpostern --skill babysit",{"tool":37,"command":38},"bunx","bunx skills add lutzseverino\u002Fpostern --skill babysit",{"tool":40,"command":41},"pnpm","pnpm dlx skills add lutzseverino\u002Fpostern --skill babysit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbabysit\u002FSKILL.md",true,[45,51,57,61,65,69,73,77,81,85,89,93],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"body-links.mjs","SCRIPT","脚本",6193,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbabysit\u002Fbody-links.mjs",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"CREDITS.md","REFERENCE","参考文档",270,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbabysit\u002FCREDITS.md",{"path":58,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":59,"sourceHtmlUrl":60},"merge.mjs",14483,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbabysit\u002Fmerge.mjs",{"path":62,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":63,"sourceHtmlUrl":64},"platform.mjs",17575,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbabysit\u002Fplatform.mjs",{"path":66,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":67,"sourceHtmlUrl":68},"pull-request-reviewer.mjs",4308,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbabysit\u002Fpull-request-reviewer.mjs",{"path":70,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":71,"sourceHtmlUrl":72},"request.mjs",3628,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbabysit\u002Frequest.mjs",{"path":74,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":75,"sourceHtmlUrl":76},"required-checks.mjs",5522,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbabysit\u002Frequired-checks.mjs",{"path":78,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":79,"sourceHtmlUrl":80},"review-outcome.mjs",3208,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbabysit\u002Freview-outcome.mjs",{"path":82,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":83,"sourceHtmlUrl":84},"review-policy.mjs",1792,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbabysit\u002Freview-policy.mjs",{"path":86,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":87,"sourceHtmlUrl":88},"reviewer.mjs",4076,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbabysit\u002Freviewer.mjs",{"path":90,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":91,"sourceHtmlUrl":92},"trusted-review-config.mjs",2340,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbabysit\u002Ftrusted-review-config.mjs",{"path":94,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":95,"sourceHtmlUrl":96},"wait.mjs",13068,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbabysit\u002Fwait.mjs",[98,105,112,119,126,133],{"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},"01M7F4S3V789SV39G7XQQ021FS","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7F4RZQ3SV81GM59D7FCZE98","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M7F4RTBB780C72G2GP3GH904","triage","Move issues and external PRs through a state machine of triage roles, sort each request by where its uncertainty lies, and bring its agent brief to acceptance through research and independent review, or through a grilling session with the owner. Also runs unattended as the factory's triage run, which writes nothing and ends with a run result.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":19},"01M7F4RN7REXARMQ18V8WZB29H","to-tickets","Break a specification into independently mergeable tickets, publish them in their responsible repositories with native parent and blocking links, and return the split for independent review.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":19},"01M7F4RH5ZSNGESE2ECB4JH7J7","to-spec","Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fto-spec\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":19},"01M7F4RF1VJMBJFQP4K974PRSZ","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Fpostern\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]