[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CP6ZTFGZ5P2VCBZ295RJR1":3,"skill-same:01M7CP6ZTFGZ5P2VCBZ295RJR1":59},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7CP6ZTFGZ5P2VCBZ295RJR1","review",null,"Review an implemented draft pull request as an agent that did not write it, fix small findings or hand it back, then mark it ready and babysit it to merge. Use when a draft PR waits on review, or when asked to review and land one.","lutzseverino\u002Frepo-canon","lutzseverino","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28309837?v=4","01M77NN0YKH0YYGY7W7ER23MX0","Jasper","01M7CP5B58PDMK3RT3CE7F70Q2",1,"MIT","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: review\ndescription: Review an implemented draft pull request as an agent that did not write it, fix small findings or hand it back, then mark it ready and babysit it to merge. Use when a draft PR waits on review, or when asked to review and land one.\n---\n\nA prompt or brief naming this skill is its invocation.\n\nTake an implemented draft pull request to merge as its independent reviewer.\nRun in a session that wrote none of the change; if you wrote any of it, stop\nand say so, because the review needs a fresh agent. The\n`github-repository-configuration` rules' Review of an implemented pull request\nsection holds what a review must do, and where installed, the\n`factory-workflow` rules hold how an owner gate stops it; this skill supplies\nthe method. Each step that posts names the section of\n`.repo-standards\u002Frules\u002Fcomments.md` to read before posting.\n\nThe review works in **rounds**, one reviewed head each. A round **holds**,\n**hands back**, **fails** or goes to a **grill**, as those rules say.\n\n`node \u003Cthis skill's directory>\u002Fround.mjs \u003Cnumber>`, run from the repository\nroot, prints the PR's `head`, its `round`, whether that head is already\n`reviewed`, whether the review `held`, whether it is a `draft`, the `issues` it\ncloses and every owner `gates` label on the PR or those issues. It counts\nonly the standing reviews of the account you run as, as the rules say: the\nreview held when that account's latest one is a holding review of the head.\nAdd `--issue \u003Cn>` for an issue the PR links without closing. It requires\nNode.js 24 or 26 and uses the GitHub CLI's credential. Exit `1` is an\ninvocation or platform error, including more closing issues or labels than one\nread holds: follow `CONTRIBUTING.md`'s Credentials section for a permission\nrefusal; otherwise fix the cause and run it again.\n\n1. **Read the round.** Run `round.mjs`. When it reports `held yes`, delivery\n   already started, as after a run stopped before step 5 finished, a later\n   babysit round or a cleared gate: go to step 5. When it reports\n   `reviewed yes` and `held no`, read its review and the recorded resolution.\n   An unresolved finding still waits for its implementation or grill. When a\n   grill settled the contract finding without requiring a code change, resume\n   with the inputs below and step 2 on this unchanged head; resolution alone\n   does not make it hold.\n   Read the authoritative implementation contract\n   under `CONTRIBUTING.md`'s Implementation contracts section, the whole issue\n   and its discussion, every earlier round's review and the grill's decision,\n   including acceptance of any contract revision the guide requires. Without\n   a settled contract, retain the contract-finding stop. A PR without an issue\n   takes its decision-bearing body as its contract. Done when you hold the\n   head, the round number, the contract and the issue.\n2. **Review.** Check out the head in a checkout you own and run `code-review`\n   with the merge-base of the PR's base branch as the fixed point and the\n   contract as the spec.\n   Apply `codebase-design`'s [Ownership check](..\u002Fcodebase-design\u002FSKILL.md#ownership-check) through `code-review`'s Standards axis, judging against the recorded contract.\n   Give its Spec axis this task context: also read the\n   contract against the issue, and report where the contract contradicts,\n   drops or invents what the issue and its recorded decisions ask, or leaves it\n   ambiguous. A PR without an issue has no such check. Verify every finding\n   against the source and drop those that do not hold. A defect outside the\n   change's responsibility goes under `CONTRIBUTING.md`'s Findings section, not\n   into this review. Sort each remaining finding as **contract**, **larger**\n   or **small**, by the rules' section. Done when every finding from both axes\n   is dropped with its reason or sorted.\n3. **Fix small findings** when no contract or larger finding stands; otherwise\n   fix nothing and carry every finding into the review. With no fix, retain the\n   current head. Commit the fixes to the\n   PR branch, run the required checks the development guide names, and push.\n   Run `round.mjs` again: its head is the head this round's review covers. Done\n   when the diff from the reviewed head to that head holds only the fixes and\n   the checks pass.\n4. **Post the round's review**, after reading\n   `.repo-standards\u002Frules\u002Fcomments.md#reviews`: the actual Standards and Spec\n   outcomes, the fixes under `Fixed`, and each open finding under `Findings`\n   with its file and line, all in its body, listing only the findings the\n   rules count as open. For a same-head reassessment, explain in `Spec` which\n   contract finding was resolved, link its recorded decision and report the\n   actual reassessment. Record it with\n   `round.mjs \u003Cnumber> --reassess \u003Cfile>`: it updates this account's latest\n   complete non-holding review of this head, preserving the previous assessment\n   as quoted history. The round number and convergence bound stay unchanged.\n   For a new head, post with `round.mjs \u003Cnumber> --post \u003Cfile>`;\n   exit `2` means the file is not a complete review of the current head, so\n   correct it and record again; exit `3` means no review can be posted or\n   reassessed, so reread the round and leave an already holding review intact.\n   Then:\n   - The round **holds**: go to step 5.\n   - A **larger** finding in round 1 **hands back**: leave the PR a draft and\n     end the run, reporting the hand-back with the review's link, so `implement`\n     can take it on the same PR.\n   - A **larger** finding in a later round **fails**: leave the PR a draft and\n     end the run, reporting that the rounds did not converge and why.\n   - A **contract** finding: post the question a grill must settle as\n     `.repo-standards\u002Frules\u002Fcomments.md#owner-questions` says, move the issue\n     to `state:grill`, leave the PR a draft and stop under\n     `CONTRIBUTING.md`'s owner-question handoff.\n5. **Deliver.** Mark the PR ready with `round.mjs \u003Cnumber> --ready`; exit `2`\n   means the review has not held, so return to step 1. Then run `babysit` on\n   the PR, posting each internal review round it calls for with\n   `round.mjs --post`, in the same shape as step 4. Before each of babysit's\n   merge attempts, run `round.mjs` again. When it reports a gate, stop at\n   ready-to-merge as the `factory-workflow` rules say: leave the PR open, move\n   its issue, if it has one, to `state:owner`, and end the run, reporting the\n   gate.\n\n## Reads\n\nPaths are relative to the repository root.\n\n- `CONTRIBUTING.md`: the implementation contract, Findings, Credentials and\n  owner-question handoff the steps name, and the development guide's required\n  checks. When it is missing, take the issue body as the contract, run the\n  checks the repository documents, and hand off to the owner in one PR comment\n  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  review in the shape `round.mjs` accepts and each question as one comment.\n- The installed `github-repository-configuration` and `factory-workflow`\n  rules, and those `babysit` names, which the `repository-standards` skill\n  looks up. When the review section is missing, hold a round only with no open\n  finding, hand back any other finding once and fail on a second round with\n  one; without the factory rules, a gate stops delivery as step 5 says.\n- The `code-review` skill, which runs both axes. When it is missing, review\n  the diff since the merge-base against the repository's documented standards\n  and against the contract yourself, keeping the two axes apart.\n- The `babysit` skill, which delivers the PR: `round.mjs` imports its GitHub\n  CLI connection and its review shape. When it is missing, `round.mjs` cannot\n  start: stop and report that this skill needs it.\n- The `implement` skill, which takes a hand-back on the same PR. When it is\n  missing, report the hand-back with the review's link and stop.\n- The `codebase-design` skill: the check used through Standards above. When\n  missing, report the gap through the contribution guide's Findings route, or\n  in the handoff without the guide; retain the recorded contract as the baseline.\n","A prompt or brief naming this skill is its invocation.\n\nTake an implemented draft pull request to merge as its independent reviewer.\nRun in a session that wrote none of the change; if you wrote any of it, stop\nand say so, because the review needs a fresh agent. The\n`github-repository-configuration` rules' Review of an implemented pull request\nsection holds what a review must do, and where installed, the\n`factory-workflow` rules hold how an owner gate stops it; this skill supplies\nthe method. Each step that posts names the section of\n`.repo-standards\u002Frules\u002Fcomments.md` to read before posting.\n\nThe review works in **rounds**, one reviewed head each. A round **holds**,\n**hands back**, **fails** or goes to a **grill**, as those rules say.\n\n`node \u003Cthis skill's directory>\u002Fround.mjs \u003Cnumber>`, run from the repository\nroot, prints the PR's `head`, its `round`, whether that head is already\n`reviewed`, whether the review `held`, whether it is a `draft`, the `issues` it\ncloses and every owner `gates` label on the PR or those issues. It counts\nonly the standing reviews of the account you run as, as the rules say: the\nreview held when that account's latest one is a holding review of the head.\nAdd `--issue \u003Cn>` for an issue the PR links without closing. It requires\nNode.js 24 or 26 and uses the GitHub CLI's credential. Exit `1` is an\ninvocation or platform error, including more closing issues or labels than one\nread holds: follow `CONTRIBUTING.md`'s Credentials section for a permission\nrefusal; otherwise fix the cause and run it again.\n\n1. **Read the round.** Run `round.mjs`. When it reports `held yes`, delivery\n   already started, as after a run stopped before step 5 finished, a later\n   babysit round or a cleared gate: go to step 5. When it reports\n   `reviewed yes` and `held no`, read its review and the recorded resolution.\n   An unresolved finding still waits for its implementation or grill. When a\n   grill settled the contract finding without requiring a code change, resume\n   with the inputs below and step 2 on this unchanged head; resolution alone\n   does not make it hold.\n   Read the authoritative implementation contract\n   under `CONTRIBUTING.md`'s Implementation contracts section, the whole issue\n   and its discussion, every earlier round's review and the grill's decision,\n   including acceptance of any contract revision the guide requires. Without\n   a settled contract, retain the contract-finding stop. A PR without an issue\n   takes its decision-bearing body as its contract. Done when you hold the\n   head, the round number, the contract and the issue.\n2. **Review.** Check out the head in a checkout you own and run `code-review`\n   with the merge-base of the PR's base branch as the fixed point and the\n   contract as the spec.\n   Apply `codebase-design`'s [Ownership check](..\u002Fcodebase-design\u002FSKILL.md#ownership-check) through `code-review`'s Standards axis, judging against the recorded contract.\n   Give its Spec axis this task context: also read the\n   contract against the issue, and report where the contract contradicts,\n   drops or invents what the issue and its recorded decisions ask, or leaves it\n   ambiguous. A PR without an issue has no such check. Verify every finding\n   against the source and drop those that do not hold. A defect outside the\n   change's responsibility goes under `CONTRIBUTING.md`'s Findings section, not\n   into this review. Sort each remaining finding as **contract**, **larger**\n   or **small**, by the rules' section. Done when every finding from both axes\n   is dropped with its reason or sorted.\n3. **Fix small findings** when no contract or larger finding stands; otherwise\n   fix nothing and carry every finding into the review. With no fix, retain the\n   current head. Commit the fixes to the\n   PR branch, run the required checks the development guide names, and push.\n   Run `round.mjs` again: its head is the head this round's review covers. Done\n   when the diff from the reviewed head to that head holds only the fixes and\n   the checks pass.\n4. **Post the round's review**, after reading\n   `.repo-standards\u002Frules\u002Fcomments.md#reviews`: the actual Standards and Spec\n   outcomes, the fixes under `Fixed`, and each open finding under `Findings`\n   with its file and line, all in its body, listing only the findings the\n   rules count as open. For a same-head reassessment, explain in `Spec` which\n   contract finding was resolved, link its recorded decision and report the\n   actual reassessment. Record it with\n   `round.mjs \u003Cnumber> --reassess \u003Cfile>`: it updates this account's latest\n   complete non-holding review of this head, preserving the previous assessment\n   as quoted history. The round number and convergence bound stay unchanged.\n   For a new head, post with `round.mjs \u003Cnumber> --post \u003Cfile>`;\n   exit `2` means the file is not a complete review of the current head, so\n   correct it and record again; exit `3` means no review can be posted or\n   reassessed, so reread the round and leave an already holding review intact.\n   Then:\n   - The round **holds**: go to step 5.\n   - A **larger** finding in round 1 **hands back**: leave the PR a draft and\n     end the run, reporting the hand-back with the review's link, so `implement`\n     can take it on the same PR.\n   - A **larger** finding in a later round **fails**: leave the PR a draft and\n     end the run, reporting that the rounds did not converge and why.\n   - A **contract** finding: post the question a grill must settle as\n     `.repo-standards\u002Frules\u002Fcomments.md#owner-questions` says, move the issue\n     to `state:grill`, leave the PR a draft and stop under\n     `CONTRIBUTING.md`'s owner-question handoff.\n5. **Deliver.** Mark the PR ready with `round.mjs \u003Cnumber> --ready`; exit `2`\n   means the review has not held, so return to step 1. Then run `babysit` on\n   the PR, posting each internal review round it calls for with\n   `round.mjs --post`, in the same shape as step 4. Before each of babysit's\n   merge attempts, run `round.mjs` again. When it reports a gate, stop at\n   ready-to-merge as the `factory-workflow` rules say: leave the PR open, move\n   its issue, if it has one, to `state:owner`, and end the run, reporting the\n   gate.\n\n## Reads\n\nPaths are relative to the repository root.\n\n- `CONTRIBUTING.md`: the implementation contract, Findings, Credentials and\n  owner-question handoff the steps name, and the development guide's required\n  checks. When it is missing, take the issue body as the contract, run the\n  checks the repository documents, and hand off to the owner in one PR comment\n  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  review in the shape `round.mjs` accepts and each question as one comment.\n- The installed `github-repository-configuration` and `factory-workflow`\n  rules, and those `babysit` names, which the `repository-standards` skill\n  looks up. When the review section is missing, hold a round only with no open\n  finding, hand back any other finding once and fail on a second round with\n  one; without the factory rules, a gate stops delivery as step 5 says.\n- The `code-review` skill, which runs both axes. When it is missing, review\n  the diff since the merge-base against the repository's documented standards\n  and against the contract yourself, keeping the two axes apart.\n- The `babysit` skill, which delivers the PR: `round.mjs` imports its GitHub\n  CLI connection and its review shape. When it is missing, `round.mjs` cannot\n  start: stop and report that this skill needs it.\n- The `implement` skill, which takes a hand-back on the same PR. When it is\n  missing, report the hand-back with the review's link and stop.\n- The `codebase-design` skill: the check used through Standards above. When\n  missing, report the gap through the contribution guide's Findings route, or\n  in the handoff without the guide; retain the recorded contract as the baseline.\n",{"name":5,"description":7},"main","f5a3e334f7bc0fce1854f224a8e78c53f8ea75b9",".agents\u002Fskills\u002Freview",0,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon","https:\u002F\u002Frepo-standards.com\u002Fsources\u002Flutzseverino\u002Frepo-canon\u002F","https:\u002F\u002Fgithub.com\u002Flutzseverino","If Codex could write profile bios, you wouldn't be reading this. Or would you?","2026-11-15 06:12:31",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add lutzseverino\u002Frepo-canon --skill review",{"tool":39,"command":40},"bunx","bunx skills add lutzseverino\u002Frepo-canon --skill review",{"tool":42,"command":43},"pnpm","pnpm dlx skills add lutzseverino\u002Frepo-canon --skill review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"CREDITS.md","REFERENCE","参考文档",99,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freview\u002FCREDITS.md",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"round.mjs","SCRIPT","脚本",11248,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freview\u002Fround.mjs",[60,67,74,81,88,95],{"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},"01M7CP829W88YVACQ3ZFS4KYAK","repository-standards","Look up installed rules before any work in a disposable planning exercise, including tracker work and file changes.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002Fscripts\u002Fsupport\u002Frepository-standards\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},"01M7CP7Y70KNBJBVDNGSQ6RGG4","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.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Ftriage\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},"01M7CP7TWX07ST84HT5XNEYS1J","orchestrate","Turn the owner's feature or problem into an approved plan across tickets, keep its state in the workbench, and run it to an announced close.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Forchestrate\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},"01M7CP7QE6M9W0E24BV0VZV1RS","babysit","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.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fbabysit\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7CP7N4VMT6C4THVN2RBRB5Q","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\u002Frepo-canon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7CP7GN4YYS18YS91N0AN0PK","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\u002Frepo-canon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]