[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KKQEH641F4JHBTQHHTGV3F":3,"skill-same:01M6KKQEH641F4JHBTQHHTGV3F":75},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6KKQEH641F4JHBTQHHTGV3F","pr-review-to-merge",null,"Own an authorized pull request or ordered stack from review through verified merge, including fixes, current-head bot follow-up, CI, thread resolution, and durable continuation.","open-hax\u002Fknoxx","open-hax","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F243925769?v=4","01M6HV3FN9ZYTQ1W5DA8GQGZG5","OpenHax","01M6KKNN8DPM34X4ZX5ND3F5Y4",3,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Fopen-hax\u002Fknoxx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpr-review-to-merge\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"review","pr review to merge","pr","pr review","merge","workflow","pull request","pull","ci","open","stack","up","resolution","head","follow-up","verified","thread","fixes","request","bot","2026-11-10 10:12:30",false,"---\nname: pr-review-to-merge\ndescription: Own an authorized pull request or ordered stack from review through verified merge, including fixes, current-head bot follow-up, CI, thread resolution, and durable continuation.\nlicense: GPL-3.0-or-later\nmetadata:\n  origin: User-requested workflow extracted from open-hax\u002Fknoxx PR 305\n---\n\n# PR review to merge\n\n## Use this skill when\n\n- The user authorizes merging a PR or advancing an ordered PR stack.\n- The user asks you to resume an already authorized review-and-merge workflow.\n\n## Do not use this skill when\n\n- The request is only to review, split, task out, or prepare draft PRs. Those\n  actions do not grant merge authorization.\n- The user pauses or cancels merging, or the next PR is outside the authorized scope.\n\nFollow the active harness, user instructions, project AGENTS.md, and applicable\ncanonical principles. Existing session authorization persists; do not ask again\nmerely because a turn ended, a reviewer replied, or a quota reset is needed.\n\nFor PRs that change deployment qualification, also apply the repository's\npromotion workflow. This skill still owns their review and merge; it does not\nreplace any required deployment qualification or promotion gate.\n\n## Inputs and durable state\n\nRecord the authorized scope, repository, ordered PR\u002Ftask URLs, intended bases,\nmerge method, and required reviewers. For each PR retain its current head and\nbase SHAs, current-head review evidence, check results, unresolved thread URLs,\nblockers, and the next concrete action. Use the project's existing tracker and\nreceipt location; do not create a competing queue or record credentials.\n\n## Procedure\n\n1. **Select one active PR.** Inspect live heads, bases, branch rules, required\n   checks, review state, and dependency order. Keep later stack layers draft.\n   Make the active PR ready for review once its actual prerequisites and base\n   integration are present. Parallel workers may prepare independent fixes;\n   one coordinator owns branch propagation, external review requests and merge.\n   Inspect `autoMergeRequest` and ready-triggered repository automation. If a bot\n   queues auto-merge before the review gate, wait for that job to finish, disable\n   auto-merge on this PR, and verify it is absent before resolving the final\n   conversations. Recheck this after readiness transitions; do not change global\n   repository settings or assume a green bot status means its review completed.\n2. **Make the active change mergeable.** Reproduce failures and repair code,\n   tests, build configuration and integration conflicts within the authorized\n   scope. Bring real prerequisites into the active dependency chain or repair\n   the split boundary. A green cumulative tree does not prove an earlier layer\n   builds. Preserve unrelated work; stage explicit paths, never amend or force\n   push, and propagate stack changes with ordinary commits\u002Fmerges.\n3. **Close the review loop.** Read every actionable bot thread, including older\n   threads still relevant to the current diff. Fix valid findings and add the\n   appropriate regression evidence. Reply in each thread with the fix commit,\n   exact tested context and result. If you disagree, explain the code path and\n   evidence, request adjudication, and keep it open pending that decision.\n   Linking a report to a task is intake, not resolution.\n4. **Request current-head follow-up.** Supply an author walkthrough where the\n   repository requires it. Request both CodeRabbit and Codex for Knoxx, or all\n   reviewers required by the user's workflow elsewhere. Reuse an in-flight\n   request for the same head; never duplicate it. A request acknowledgment,\n   stale review or rate-limit reply is not completion. After each change,\n   obtain each reviewer's completion for the latest head and relevant base.\n5. **Resolve verified threads.** Resolve a finding only after the fix and\n   relevant checks demonstrate it is addressed, or the reviewer adjudicates\n   the documented disagreement. Reply with evidence before resolving. Do not\n   resolve an actionable finding merely because it is outdated, copied to a\n   task, or inconvenient. Inspect all conversations again after follow-up.\n6. **Recheck the merge gate.** Fetch fresh remote state. Require no actionable\n   findings, completion by every required reviewer on the current head, all\n   required checks passing with applicable suites actually exercised, all\n   review conversations resolved, branch protection satisfied, and no unresolved\n   prerequisite or integration blocker. Missing\u002Fpending evidence is not a pass.\n   Do not weaken checks, suppress failures, change protection, use administrator\n   bypass, or merge an unqualified layer to advance the queue.\n7. **Merge the verified head.** Use an API\u002FCLI operation that asserts the exact\n   reviewed head SHA and obeys the repository's merge method and protections.\n   If the head\u002Fbase changes or merge is refused, refresh evidence and return to\n   the relevant gate. Queuing auto-merge is still pending work: observe the\n   actual GitHub merged state and merge commit before declaring completion.\n   Check actual PR state during review waits too. If another actor or automation\n   merges early, record the missing evidence, finish the outstanding review and\n   land any required follow-up before advancing. Do not report that the intended\n   review gate passed merely because the PR merged.\n8. **Advance the stack.** Record the merged PR and commit, retarget the next\n   authorized layer to the correct surviving base, check its actual diff and\n   dependencies, propagate changes without rewriting history, and repeat.\n   A squash merge can leave predecessor commits in descendant history; repair\n   that ancestry\u002Fdiff with an ordinary integration commit before review.\n\n## Quotas and continuation\n\nA quota, pending CI run, or unavailable reviewer is a durable wait state, not\ncompletion. Record its evidence, next eligible retry time, and the next action.\nUse an available supported continuation mechanism when the user has authorized\ncontinued work; keep its objective **fix, review, verify, merge, and advance**.\nNever reduce the objective to collecting review comments or reporting status.\nOn waking, inspect current state first and resume the owning loop. Back off on\nunchanged waits and notify only on meaningful progress, merge, failure or a\nrequired user decision. If no continuation can actually be scheduled, state\nthat limitation and preserve a resumable handoff; do not promise background work.\n\n## Completion and output\n\nAn individual merge task is complete only after GitHub confirms that PR merged\nand the required review\u002Ffix loop is closed, including any early-merge recovery.\nAn authorized stack is complete only after every in-scope PR merged, unless the\nuser changes the scope. A draft, review request, green suite, resolved-thread\nlist, or enabled auto-merge is an intermediate state. Report merged PR\u002Fcommit\nlinks and the next active PR, or the exact blocker and continuation state.\n\n## Provenance and compatibility\n\nThis native skill was explicitly requested during the Knoxx PR #305 decomposition\nafter review collection had not yet delivered the authorized merge outcome. It\ndoes not grant merge authorization by itself. Its activation\u002Fgovernance data is\nin [CONTRACT.edn](CONTRACT.edn).\n\nThe canonical local catalog is `~\u002F.agents\u002Fskills\u002Fpr-review-to-merge\u002F`. A project\nmay carry a versioned copy for a self-contained checkout; keep that copy equal\nto the canonical skill rather than editing two independent policies. OpenCode\nmay discover a project link under `.opencode\u002Fskill\u002Fpr-review-to-merge\u002F`; legacy\nPi and Codex discovery directories may link to the canonical catalog. Installation\ndoes not imply that an already-running harness has reloaded its skill list.\n","# PR review to merge\n\n## Use this skill when\n\n- The user authorizes merging a PR or advancing an ordered PR stack.\n- The user asks you to resume an already authorized review-and-merge workflow.\n\n## Do not use this skill when\n\n- The request is only to review, split, task out, or prepare draft PRs. Those\n  actions do not grant merge authorization.\n- The user pauses or cancels merging, or the next PR is outside the authorized scope.\n\nFollow the active harness, user instructions, project AGENTS.md, and applicable\ncanonical principles. Existing session authorization persists; do not ask again\nmerely because a turn ended, a reviewer replied, or a quota reset is needed.\n\nFor PRs that change deployment qualification, also apply the repository's\npromotion workflow. This skill still owns their review and merge; it does not\nreplace any required deployment qualification or promotion gate.\n\n## Inputs and durable state\n\nRecord the authorized scope, repository, ordered PR\u002Ftask URLs, intended bases,\nmerge method, and required reviewers. For each PR retain its current head and\nbase SHAs, current-head review evidence, check results, unresolved thread URLs,\nblockers, and the next concrete action. Use the project's existing tracker and\nreceipt location; do not create a competing queue or record credentials.\n\n## Procedure\n\n1. **Select one active PR.** Inspect live heads, bases, branch rules, required\n   checks, review state, and dependency order. Keep later stack layers draft.\n   Make the active PR ready for review once its actual prerequisites and base\n   integration are present. Parallel workers may prepare independent fixes;\n   one coordinator owns branch propagation, external review requests and merge.\n   Inspect `autoMergeRequest` and ready-triggered repository automation. If a bot\n   queues auto-merge before the review gate, wait for that job to finish, disable\n   auto-merge on this PR, and verify it is absent before resolving the final\n   conversations. Recheck this after readiness transitions; do not change global\n   repository settings or assume a green bot status means its review completed.\n2. **Make the active change mergeable.** Reproduce failures and repair code,\n   tests, build configuration and integration conflicts within the authorized\n   scope. Bring real prerequisites into the active dependency chain or repair\n   the split boundary. A green cumulative tree does not prove an earlier layer\n   builds. Preserve unrelated work; stage explicit paths, never amend or force\n   push, and propagate stack changes with ordinary commits\u002Fmerges.\n3. **Close the review loop.** Read every actionable bot thread, including older\n   threads still relevant to the current diff. Fix valid findings and add the\n   appropriate regression evidence. Reply in each thread with the fix commit,\n   exact tested context and result. If you disagree, explain the code path and\n   evidence, request adjudication, and keep it open pending that decision.\n   Linking a report to a task is intake, not resolution.\n4. **Request current-head follow-up.** Supply an author walkthrough where the\n   repository requires it. Request both CodeRabbit and Codex for Knoxx, or all\n   reviewers required by the user's workflow elsewhere. Reuse an in-flight\n   request for the same head; never duplicate it. A request acknowledgment,\n   stale review or rate-limit reply is not completion. After each change,\n   obtain each reviewer's completion for the latest head and relevant base.\n5. **Resolve verified threads.** Resolve a finding only after the fix and\n   relevant checks demonstrate it is addressed, or the reviewer adjudicates\n   the documented disagreement. Reply with evidence before resolving. Do not\n   resolve an actionable finding merely because it is outdated, copied to a\n   task, or inconvenient. Inspect all conversations again after follow-up.\n6. **Recheck the merge gate.** Fetch fresh remote state. Require no actionable\n   findings, completion by every required reviewer on the current head, all\n   required checks passing with applicable suites actually exercised, all\n   review conversations resolved, branch protection satisfied, and no unresolved\n   prerequisite or integration blocker. Missing\u002Fpending evidence is not a pass.\n   Do not weaken checks, suppress failures, change protection, use administrator\n   bypass, or merge an unqualified layer to advance the queue.\n7. **Merge the verified head.** Use an API\u002FCLI operation that asserts the exact\n   reviewed head SHA and obeys the repository's merge method and protections.\n   If the head\u002Fbase changes or merge is refused, refresh evidence and return to\n   the relevant gate. Queuing auto-merge is still pending work: observe the\n   actual GitHub merged state and merge commit before declaring completion.\n   Check actual PR state during review waits too. If another actor or automation\n   merges early, record the missing evidence, finish the outstanding review and\n   land any required follow-up before advancing. Do not report that the intended\n   review gate passed merely because the PR merged.\n8. **Advance the stack.** Record the merged PR and commit, retarget the next\n   authorized layer to the correct surviving base, check its actual diff and\n   dependencies, propagate changes without rewriting history, and repeat.\n   A squash merge can leave predecessor commits in descendant history; repair\n   that ancestry\u002Fdiff with an ordinary integration commit before review.\n\n## Quotas and continuation\n\nA quota, pending CI run, or unavailable reviewer is a durable wait state, not\ncompletion. Record its evidence, next eligible retry time, and the next action.\nUse an available supported continuation mechanism when the user has authorized\ncontinued work; keep its objective **fix, review, verify, merge, and advance**.\nNever reduce the objective to collecting review comments or reporting status.\nOn waking, inspect current state first and resume the owning loop. Back off on\nunchanged waits and notify only on meaningful progress, merge, failure or a\nrequired user decision. If no continuation can actually be scheduled, state\nthat limitation and preserve a resumable handoff; do not promise background work.\n\n## Completion and output\n\nAn individual merge task is complete only after GitHub confirms that PR merged\nand the required review\u002Ffix loop is closed, including any early-merge recovery.\nAn authorized stack is complete only after every in-scope PR merged, unless the\nuser changes the scope. A draft, review request, green suite, resolved-thread\nlist, or enabled auto-merge is an intermediate state. Report merged PR\u002Fcommit\nlinks and the next active PR, or the exact blocker and continuation state.\n\n## Provenance and compatibility\n\nThis native skill was explicitly requested during the Knoxx PR #305 decomposition\nafter review collection had not yet delivered the authorized merge outcome. It\ndoes not grant merge authorization by itself. Its activation\u002Fgovernance data is\nin [CONTRACT.edn](CONTRACT.edn).\n\nThe canonical local catalog is `~\u002F.agents\u002Fskills\u002Fpr-review-to-merge\u002F`. A project\nmay carry a versioned copy for a self-contained checkout; keep that copy equal\nto the canonical skill rather than editing two independent policies. OpenCode\nmay discover a project link under `.opencode\u002Fskill\u002Fpr-review-to-merge\u002F`; legacy\nPi and Codex discovery directories may link to the canonical catalog. Installation\ndoes not imply that an already-running harness has reloaded its skill list.\n",{"name":5,"license":44,"metadata":45,"description":7},"GPL-3.0-or-later",{"origin":46},"User-requested workflow extracted from open-hax\u002Fknoxx PR 305","main","9d3f44af3d88409740c455c53a771424495eb2cf",".agents\u002Fskills\u002Fpr-review-to-merge",1,"https:\u002F\u002Fgithub.com\u002Fopen-hax\u002Fknoxx","https:\u002F\u002Fgithub.com\u002Fopen-hax","tooling for opencode","2026-11-11 04:15:54",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add open-hax\u002Fknoxx --skill pr-review-to-merge",{"tool":61,"command":62},"bunx","bunx skills add open-hax\u002Fknoxx --skill pr-review-to-merge",{"tool":64,"command":65},"pnpm","pnpm dlx skills add open-hax\u002Fknoxx --skill pr-review-to-merge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopen-hax\u002Fknoxx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpr-review-to-merge\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"CONTRACT.edn","OTHER","其他",1250,"https:\u002F\u002Fgithub.com\u002Fopen-hax\u002Fknoxx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpr-review-to-merge\u002FCONTRACT.edn",[76],{"skillNo":77,"name":5,"nameZh":6,"description":6,"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":39},"01M6KKQM2JFTYK4NMXQJ2GF67Z","https:\u002F\u002Fgithub.com\u002Fopen-hax\u002Fknoxx\u002Fblob\u002Fmain\u002F.opencode\u002Fskill\u002Fpr-review-to-merge\u002FSKILL.md",[],[19,23,22,21,20]]