[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78F7313616X1CDRCRW22K0H":3,"skill-same:01M78F7313616X1CDRCRW22K0H":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M78F7313616X1CDRCRW22K0H","pr-fix-protocol",null,"Applies reviewer findings to a PR as verified fixes and drives unresolved review threads to zero. Invoked by PR-loop orchestrators (pr-converge, autoconverge, bugteam, qbug, copilot-review) when a reviewer reports findings; not for ad-hoc 'fix this bug' requests outside a PR loop.","jl-cmd-projects\u002Fclaude-dev-env","jl-cmd-projects","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F338158757?v=4","01M78F4M55P4QY5YPN27XBQA9N","01M78F4M65AGEYC88NV6PW4715",7,"MIT","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fpackages\u002Fclaude-dev-env\u002F.agents\u002Fskills-archived\u002Fpr-fix-protocol\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pr-fix-protocol\ndescription: >-\n  Applies reviewer findings to a PR as verified fixes and drives unresolved\n  review threads to zero. Invoked by PR-loop orchestrators (pr-converge,\n  autoconverge, bugteam, qbug, copilot-review) when a reviewer reports\n  findings; not for ad-hoc 'fix this bug' requests outside a PR loop.\n---\n\n# PR Fix Protocol\n\n**Core principle:** a finding is addressed only when the fix is pushed, the thread carries a reply, and the thread is resolved — as one unit of work. Anything short of all three leaves a convergence gate stalled.\n\n## How callers invoke this\n\n- **Skill-capable contexts** (a lead session that holds the `Skill` tool): `Skill({skill: \"pr-fix-protocol\", args: \"--skill \u003Ccaller> --pr \u003CURL> --worktree \u003Cpath> [findings payload or 'sweep']\"})`.\n- **Fallback** (a subagent or teammate without the `Skill` tool): the caller's spawn prompt says to read `~\u002F.claude\u002Fskills\u002Fpr-fix-protocol\u002FSKILL.md` and apply it with the parameters below.\n\nThe caller passes: its identity, the PR scope, the PR worktree path, this round's findings (or `sweep` for a thread sweep with no fresh findings), and its post-push obligations — which clean-SHA state fields to reset and which reviewers to re-trigger.\n\n## Executor choice\n\n- **Single-PR loops** (no shared `state.json`): the lead spawns `Agent(subagent_type: \"clean-coder\", model: \"sonnet\")` — worker-model routing per [`skills\u002Forchestrator\u002FSKILL.md`](..\u002Forchestrator\u002FSKILL.md#workflow-agent-routing); resolver-supplied sonnet-equivalent on third-party hosts — to write the fix. Stop when `Agent` is unavailable. A spawned clean-coder starts in its own working directory, so its prompt names the PR worktree path and directs it to edit, stage, and commit there.\n- **Multi-PR orchestration** (shared `state.json`): a per-PR clean-coder teammate owns edits, replies, and state writes; the orchestrator holds back from inline edits. The teammate obligations — reply before writing state, which state fields to set, idle handoff — live in the calling skill's multi-PR reference.\n\nRun every git command in the PR worktree. `git add`, `git commit`, and `git push` act on the repo of the current working directory, so a cross-repo PR's fix lands in the PR's repo only when the working directory is its worktree.\n\n## The fix sequence\n\nFollow the shared 13-step sequence in [`_shared\u002Fpr-loop\u002Ffix-protocol.md`](..\u002F..\u002F_shared\u002Fpr-loop\u002Ffix-protocol.md) exactly: read each file:line, capture the pre-fix SHA and contents, write a failing test first where the finding has behavior, apply the fix narrowly, `py_compile`, run the post-fix self-audit, stage by explicit path, make one commit, fast-forward push, then reply and resolve atomically per thread. Its Constraints section — narrow scope, keep the commit hooks, preserve helpers — binds every executor.\n\n**Reply transport:** the GitHub MCP `add_reply_to_pull_request_comment` is primary. For a script-only context or a multi-PR teammate, the fallback is `python \"$HOME\u002F.claude\u002Fskills\u002Fpr-converge\u002Fscripts\u002Fpost_fix_reply.py\" --owner \u003CO> --repo \u003CR> --pr-number \u003CN> --in-reply-to \u003CCOMMENT_ID> --body \"Fixed in \u003CSHA> — \u003Cwhat changed>\"`. Both carry the body shape from [`_shared\u002Fpr-loop\u002Faudit-reply-template.md`](..\u002F..\u002F_shared\u002Fpr-loop\u002Faudit-reply-template.md). For a body-only finding with no inline thread, post a top-level review reply that cites the new HEAD SHA.\n\n**Thread resolution:** call `pull_request_review_write(method=\"resolve_thread\", threadId=\u003CPRRT node id>)` right after each reply. Harvest the thread node ids (`PRRT_…`) from `get_review_comments` at fetch time.\n\n## The unresolved-thread sweep (hard gate)\n\nA caller advances a phase, records a clean SHA, or marks a PR ready only when the PR carries zero unresolved review threads.\n\n```\npull_request_read(method=\"get_review_comments\") → filter threads where is_resolved == false\n```\n\n- The filter is purely `is_resolved == false`. Author, anchor commit, and `is_outdated` play no part in the count.\n- `is_outdated` is informational, not a skip flag. GitHub marks a thread outdated when its anchor line changes, yet the concern can still apply to current HEAD — the fix may have moved rather than landed. Verify each outdated thread against current HEAD like any other.\n- Per unresolved thread: verify the concern against current HEAD. The concern holds → fix (this protocol) → reply → resolve. The concern does not hold on current HEAD → reply with a note that explains why → resolve.\n- Code changed during the sweep → push and hand control back to the caller's re-entry phase. Only resolutions and no code → re-run the sweep and keep the caller's state.\n\n## Post-push obligations\n\nEvery push through this protocol:\n\n1. Re-resolve `current_head` — `git rev-parse HEAD` locally, and the PR `get` call for API-visible state.\n2. Reset the caller-named clean-SHA fields to null (`bugbot_clean_at`, `code_review_clean_at`, `copilot_clean_at` — whichever the caller tracks). A new HEAD invalidates every prior clean.\n3. Re-trigger reviewers per the caller's parameter — for Cursor Bugbot the `reviewer-gates` Bugbot flow, for Copilot the caller's request step. Audit-family callers (`bugteam`, `qbug`) skip re-triggering, since their next loop iteration is the reviewer.\n\n## Gotchas\n\n- **Reply, then resolve, atomic per thread.** Batching every reply ahead of any resolve, or yielding to the orchestrator between the two, leaves threads half-addressed when a run dies mid-loop.\n- **An unchanged HEAD after step 11 means no commit landed.** Exit `stuck — could not address findings` rather than report the findings as fixed.\n- **A resolved thread with no reply reads as dismissed.** Reviewers and the humans reading the PR need the one-paragraph explanation the template carries.\n\n## Folder map\n\n- `SKILL.md` — this file. The step sequence, reply template, and payload shapes live in `_shared\u002Fpr-loop\u002F` (`fix-protocol.md`, `audit-reply-template.md`, `gh-payloads.md`); the reply fallback script lives in `pr-converge\u002Fscripts\u002F`.\n","# PR Fix Protocol\n\n**Core principle:** a finding is addressed only when the fix is pushed, the thread carries a reply, and the thread is resolved — as one unit of work. Anything short of all three leaves a convergence gate stalled.\n\n## How callers invoke this\n\n- **Skill-capable contexts** (a lead session that holds the `Skill` tool): `Skill({skill: \"pr-fix-protocol\", args: \"--skill \u003Ccaller> --pr \u003CURL> --worktree \u003Cpath> [findings payload or 'sweep']\"})`.\n- **Fallback** (a subagent or teammate without the `Skill` tool): the caller's spawn prompt says to read `~\u002F.claude\u002Fskills\u002Fpr-fix-protocol\u002FSKILL.md` and apply it with the parameters below.\n\nThe caller passes: its identity, the PR scope, the PR worktree path, this round's findings (or `sweep` for a thread sweep with no fresh findings), and its post-push obligations — which clean-SHA state fields to reset and which reviewers to re-trigger.\n\n## Executor choice\n\n- **Single-PR loops** (no shared `state.json`): the lead spawns `Agent(subagent_type: \"clean-coder\", model: \"sonnet\")` — worker-model routing per [`skills\u002Forchestrator\u002FSKILL.md`](..\u002Forchestrator\u002FSKILL.md#workflow-agent-routing); resolver-supplied sonnet-equivalent on third-party hosts — to write the fix. Stop when `Agent` is unavailable. A spawned clean-coder starts in its own working directory, so its prompt names the PR worktree path and directs it to edit, stage, and commit there.\n- **Multi-PR orchestration** (shared `state.json`): a per-PR clean-coder teammate owns edits, replies, and state writes; the orchestrator holds back from inline edits. The teammate obligations — reply before writing state, which state fields to set, idle handoff — live in the calling skill's multi-PR reference.\n\nRun every git command in the PR worktree. `git add`, `git commit`, and `git push` act on the repo of the current working directory, so a cross-repo PR's fix lands in the PR's repo only when the working directory is its worktree.\n\n## The fix sequence\n\nFollow the shared 13-step sequence in [`_shared\u002Fpr-loop\u002Ffix-protocol.md`](..\u002F..\u002F_shared\u002Fpr-loop\u002Ffix-protocol.md) exactly: read each file:line, capture the pre-fix SHA and contents, write a failing test first where the finding has behavior, apply the fix narrowly, `py_compile`, run the post-fix self-audit, stage by explicit path, make one commit, fast-forward push, then reply and resolve atomically per thread. Its Constraints section — narrow scope, keep the commit hooks, preserve helpers — binds every executor.\n\n**Reply transport:** the GitHub MCP `add_reply_to_pull_request_comment` is primary. For a script-only context or a multi-PR teammate, the fallback is `python \"$HOME\u002F.claude\u002Fskills\u002Fpr-converge\u002Fscripts\u002Fpost_fix_reply.py\" --owner \u003CO> --repo \u003CR> --pr-number \u003CN> --in-reply-to \u003CCOMMENT_ID> --body \"Fixed in \u003CSHA> — \u003Cwhat changed>\"`. Both carry the body shape from [`_shared\u002Fpr-loop\u002Faudit-reply-template.md`](..\u002F..\u002F_shared\u002Fpr-loop\u002Faudit-reply-template.md). For a body-only finding with no inline thread, post a top-level review reply that cites the new HEAD SHA.\n\n**Thread resolution:** call `pull_request_review_write(method=\"resolve_thread\", threadId=\u003CPRRT node id>)` right after each reply. Harvest the thread node ids (`PRRT_…`) from `get_review_comments` at fetch time.\n\n## The unresolved-thread sweep (hard gate)\n\nA caller advances a phase, records a clean SHA, or marks a PR ready only when the PR carries zero unresolved review threads.\n\n```\npull_request_read(method=\"get_review_comments\") → filter threads where is_resolved == false\n```\n\n- The filter is purely `is_resolved == false`. Author, anchor commit, and `is_outdated` play no part in the count.\n- `is_outdated` is informational, not a skip flag. GitHub marks a thread outdated when its anchor line changes, yet the concern can still apply to current HEAD — the fix may have moved rather than landed. Verify each outdated thread against current HEAD like any other.\n- Per unresolved thread: verify the concern against current HEAD. The concern holds → fix (this protocol) → reply → resolve. The concern does not hold on current HEAD → reply with a note that explains why → resolve.\n- Code changed during the sweep → push and hand control back to the caller's re-entry phase. Only resolutions and no code → re-run the sweep and keep the caller's state.\n\n## Post-push obligations\n\nEvery push through this protocol:\n\n1. Re-resolve `current_head` — `git rev-parse HEAD` locally, and the PR `get` call for API-visible state.\n2. Reset the caller-named clean-SHA fields to null (`bugbot_clean_at`, `code_review_clean_at`, `copilot_clean_at` — whichever the caller tracks). A new HEAD invalidates every prior clean.\n3. Re-trigger reviewers per the caller's parameter — for Cursor Bugbot the `reviewer-gates` Bugbot flow, for Copilot the caller's request step. Audit-family callers (`bugteam`, `qbug`) skip re-triggering, since their next loop iteration is the reviewer.\n\n## Gotchas\n\n- **Reply, then resolve, atomic per thread.** Batching every reply ahead of any resolve, or yielding to the orchestrator between the two, leaves threads half-addressed when a run dies mid-loop.\n- **An unchanged HEAD after step 11 means no commit landed.** Exit `stuck — could not address findings` rather than report the findings as fixed.\n- **A resolved thread with no reply reads as dismissed.** Reviewers and the humans reading the PR need the one-paragraph explanation the template carries.\n\n## Folder map\n\n- `SKILL.md` — this file. The step sequence, reply template, and payload shapes live in `_shared\u002Fpr-loop\u002F` (`fix-protocol.md`, `audit-reply-template.md`, `gh-payloads.md`); the reply fallback script lives in `pr-converge\u002Fscripts\u002F`.\n",{"name":5,"description":7},"main","974284b42eeb4609e94d4ebc1f6e36df400d54ca","packages\u002Fclaude-dev-env\u002F.agents\u002Fskills-archived\u002Fpr-fix-protocol",1,"https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects","2026-11-15 05:02:47",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add jl-cmd-projects\u002Fclaude-dev-env --skill pr-fix-protocol",{"tool":36,"command":37},"bunx","bunx skills add jl-cmd-projects\u002Fclaude-dev-env --skill pr-fix-protocol",{"tool":39,"command":40},"pnpm","pnpm dlx skills add jl-cmd-projects\u002Fclaude-dev-env --skill pr-fix-protocol","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fpackages\u002Fclaude-dev-env\u002F.agents\u002Fskills-archived\u002Fpr-fix-protocol\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M78FER7S09AE87MMJFT1E87E","update","Fast-forwards a local repository's main branch to a remote's main after confirming the repo path and source remote through AskUserQuestion. Use when the user says '\u002Fupdate', 'update main', 'fast-forward main', 'sync main from origin', 'pull latest main into \u003Cpath>', or 'bring main up to date'.","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fskill-archive\u002Fupdate\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M78FENWZS01MB4PMGX6801X6","source-command-sr-loop","Converging cleanup loop: repeat \u002Fsimplify until clean, then repeat \u002Fcode-review --fix until clean","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fskill-archive\u002Fsource-command-sr-loop\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M78FEGZ7JDWEG3RM78M9Y8F8","skill-builder","Skill lifecycle: classify, scaffold, write via the skill-writer-agent, self-audit, compose sub-skills, polish description triggers, enforce deterministic scripts. Triggers: build a skill, new skill workflow, improve this skill, optimize skill description, skill development lifecycle, skill modularity, skill composition, description trigger catalog, deterministic skill scripts.","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fskill-archive\u002Fskill-builder\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M78FEDEYHJYKTER9S566DMEZ","session-tidy","Audit, clean, and consolidate session logs in the Obsidian vault. Fixes format drift, resolves orphaned next-steps, updates stale statuses, and generates project rollup summaries. Use when session logs feel cluttered or before starting a new project milestone. Triggers on '\u002Fsession-tidy', 'tidy sessions', 'clean up session logs', 'session audit'.","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fskill-archive\u002Fsession-tidy\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M78FE8QR789SKBF3A78N2T13","session-log","Logs a session report as an HTML page, tracks vault context, extracts decisions, and outputs a \u002Frename command. Use for \u002Fsession-log, 'journal this session', 'log this work', 'session report', 'summarize\u002Flog\u002Frecord this session', 'save session', 'capture session', or 'document what we did'.","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fskill-archive\u002Fsession-log\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M78FE4JDJHKTJPWRWNQEX2HT","run-claude-dev-env","Build, install, run, and test the claude-dev-env installer. Use when asked to run claude-dev-env, install the Claude Code config into ~\u002F.claude, drive the installer, smoke-test it against a sandbox, or run its test suite.","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fskill-archive\u002Frun-claude-dev-env\u002FSKILL.md",[],[]]