[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DAS653YFZRJ7SCHZ62J44N":3,"skill-same:01M6DAS653YFZRJ7SCHZ62J44N":103},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":13,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6DAS653YFZRJ7SCHZ62J44N","beads-worker",null,"Use when implementing one cohesive Beads delivery package in a dedicated worker worktree after a coordinator or operator provides ISSUE_ID and WORKTREE_PATH.","tzeusy-org\u002Fai-bootstrap","tzeusy-org","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141543652?v=4","01M6DAM1AP09H27BYGFY9QCNPB","01M6DAM1F4R187EK11XDN9JZKH",0,"MIT","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-worker\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"worker","beads","beads worker","with","when","package","coordinator","implementing","for","cohesive","codex","id","git worktrees","access","use","gh","pr","push","python3","openai codex","2026-11-10 10:12:30",false,"---\nname: beads-worker\ndescription: Use when implementing one cohesive Beads delivery package in a dedicated worker worktree after a coordinator or operator provides ISSUE_ID and WORKTREE_PATH.\nmetadata:\n  owner: tze\n  authors:\n    - tze\n    - OpenAI Codex\n    - Claude Fable 5.1\n  status: active\n  last_reviewed: \"2026-11-06\"\ncompatibility: Requires a Beads-backed git repository with git worktrees, git, bd, jq, gh, and python3 available, plus authenticated GitHub access and network access for push and PR operations.\n---\n\n# Beads Worker\n\nImplement a cohesive package in its isolated accepted-branch worktree (default\n`agent\u002F\u003CISSUE_ID>`). ISSUE_ID\nis an existing anchor; without a delivery manifest this remains a one-bead job.\nThe same implementation owner retains ordinary test\u002Freview corrections and related\npackages until the accepted outcome is finished or explicitly handed off.\n\nUse when dispatched with `ISSUE_ID`, `WORKTREE_PATH`, `REPO_ROOT` and optional\n`DELIVERY_FILE`: “implement this package”, “correct this existing PR”, “continue\nthis accepted outcome”. Backlog processing without a dispatch uses\n[beads-looper](..\u002Fbeads-looper\u002FSKILL.md) or\n[coordinator](..\u002Fbeads-coordinator\u002FSKILL.md); authoring uses\n[writer](..\u002Fbeads-writer\u002FSKILL.md).\n\n## Contract\n\nRead [shared delivery model](..\u002F..\u002Freferences\u002Fdelivery-model.md) for packages,\nbranch choices, evidence, recovery and per-member acceptance. This worker writes\ncode, commits, pushes and opens\u002Fupdates its authorized PR. Its lifecycle controller\nowns Beads writes; never claim\u002Frelease\u002Fclose or create follow-up issues here.\nA looper applying these phases performs lifecycle updates separately as holder.\n\nDispatch authorizes accepted scope, tests, ordinary corrections, commits and push;\nedit examples are guidance unless explicitly an ownership boundary. Resolve routine\nengineering choices. Stop only for actual scope\u002Ftrust\u002Farchitecture\u002Fauthorization\nchanges or inaccessible external capability under\n[decision autonomy](..\u002F..\u002Freferences\u002Fdecision-autonomy.md). Keep unaffected work going.\nDo not spawn overlapping implementation tracks or commit Dolt-managed `.beads\u002F`.\n\n## Inputs and continuation\n\n| Field | Meaning |\n|---|---|\n| ISSUE_ID | Existing package anchor; branch defaults to agent\u002F\u003Canchor>, or exact validated delivery.branch |\n| WORKTREE_PATH \u002F REPO_ROOT | Isolated worktree and actual shared repository root |\n| DELIVERY_FILE | Optional beads-delivery\u002Fv1 manifest, required for a multi-bead package |\n| Current packet locator | Current instructions, member AC, authority references and recovery state |\n| REVIEW_CORRECTION_MODE=yes | Continue existing PR using EXISTING_PR_NUMBER, REVIEW_BEAD_ID and CORRECTION_THREADS_JSON |\n\nResume the same Claude session\u002FCodex thread for corrections or a related package.\nA new package revalidates cwd\u002Fbranch\u002Fclaims; guidance and relevant content evidence\ncarry over only while their assumptions hold. A fresh session is recovery with an\nexplicit published packet, never evidence of same-owner continuation by itself.\n\n## Bootstrap\n\n1. Set actual process cwd to WORKTREE_PATH; read\n   [runtime contract](references\u002Fruntime-contract.md) for guidance discovery and\n   protected\u002Fshared Git identity rules.\n2. Invoke [assert_worker_context.py](scripts\u002Fassert_worker_context.py) by absolute\n   skill path with `--worktree-path`, `--repo-root`, `--issue-id`, `--current-path`\n   and, for a package, `--delivery-file`. It rejects an unrelated repository,\n   protected\u002Fwrong branch, manifest mismatch or cwd mismatch. Stop and emit\n   `invalid-runtime-context` if it fails.\n3. Read target AGENTS\u002FCLAUDE and\n   [craft-and-care gate](..\u002F..\u002Freferences\u002Fcraft-and-care-gate.md); reuse unchanged\n   guidance on continuation. Read the concise current operative packet and exact\n   referenced contracts\u002Fsource. Fetch projected current fields only as needed;\n   do not load every member's historical notes or inline archives.\n\n## Implement and verify\n\nInspect the actual source before relying on planning assumptions. Implement logical\ncommits on the package branch, marking member IDs for traceability. Several related\ncorrections can share fixtures\u002Ftests, owner and PR; unrelated outcomes stay separate.\nPreserve each member's actual acceptance and hard gates. Do not silently replace\nan accepted feature with foundation-only scope.\n\nExtend nearest relevant checks under\n[test growth](..\u002F..\u002Freferences\u002Ftest-growth-gate.md). Run scoped checks while iterating;\nthe full required gate runs on the landing tree in the repository-assigned tier\nunder [token efficiency](..\u002F..\u002Freferences\u002Ftoken-efficiency.md). Reuse unchanged\ncontent evidence; refresh affected assumptions and time-sensitive runtime facts.\nNo local duplicate of a required hosted gate is mandated here. No lighter check\nsubstitutes for a repo-required one. Finish applicable craft review before handoff.\n\nOrdinary failing tests\u002FCI and review findings stay with this owner. Correct and\npush to the same PR, then send changed content and tests directly to the independent\nreviewer. The controller receives state-change receipts, not permissions per hunk.\nIf a shared prerequisite\u002Fauthority boundary is missing, name exactly its dependent\nwork and resume event; never create a second substrate implementation privately.\n\n## Publish and handoff\n\nPrefer one PR per cohesive package, targeting the approved integration base.\nPush the exact accepted implementation branch and use `gh pr create --body-file` with actual newlines.\nPR maps every member to acceptance\u002Fevidence and explicitly names partial scope.\nOnly the lifecycle controller sets anchor `external_ref` and one review relation.\n\nIn correction mode update EXISTING_PR_NUMBER; do not create a new PR\u002Freview record.\nUse ordinary push for appended commits; `--force-with-lease` only for a justified\nhistory rewrite. Verify PR head and base after pushing. Never put runtime session\nURLs or session-attribution trailers in commits\u002FPRs.\n\nA direct-merge candidate is only a repository-permitted trivial change with an\nindependent verdict and the required local gate; a merge queue\u002Frequired review\ncannot be bypassed by calling it direct. When policy is unknown, use the PR path.\nAn intermediate integration branch is accumulation, never proof of main delivery.\n\nOn push\u002FPR failure follow [runtime failure routing](references\u002Fruntime-contract.md):\none justified local retry, then a precise external-blocker receipt. Preserve useful\ncommits, remote branch and dirty\u002Flocal-only work. Never delete a worktree because\nreview begins. Session preemption\u002Frecovery publishes packet\u002Fclaims\u002Fhead\u002Ffindings and\nexplicit handoff rather than reallocating ordinary corrections.\n\n## Report\n\nUse [emit_worker_report.py](scripts\u002Femit_worker_report.py); field schemas\u002Fexamples\nare in [worker-report.md](references\u002Fworker-report.md). Multi-bead reports include\n`--delivery-file` and complete `--member-results-json` coverage, individually\nsatisfied, partial or blocked with evidence. Ready-for-review does not close any\nmember. Acceptance-inclusive runtime proof may still be unmet after source merge.\n\nStatuses remain `completed-pr-opened`, `completed-direct-merge-candidate`,\n`blocked-awaiting-coordinator`, `invalid-runtime-context`. “Completed” describes\nthis handoff, never the whole owner outcome. Include recovery state and exact resume\nevent when blocked. Current correctness discoveries stay in this package; genuinely\nnew behavior is reported separately after dedupe, without silently expanding scope.\n\nFinish on a report, never a plan or promise. Search\n[known errors](..\u002F..\u002Freferences\u002Fknown-errors.md) before debugging an unfamiliar\ntracker\u002FPR failure and record newly confirmed reusable fixes there.\n","# Beads Worker\n\nImplement a cohesive package in its isolated accepted-branch worktree (default\n`agent\u002F\u003CISSUE_ID>`). ISSUE_ID\nis an existing anchor; without a delivery manifest this remains a one-bead job.\nThe same implementation owner retains ordinary test\u002Freview corrections and related\npackages until the accepted outcome is finished or explicitly handed off.\n\nUse when dispatched with `ISSUE_ID`, `WORKTREE_PATH`, `REPO_ROOT` and optional\n`DELIVERY_FILE`: “implement this package”, “correct this existing PR”, “continue\nthis accepted outcome”. Backlog processing without a dispatch uses\n[beads-looper](..\u002Fbeads-looper\u002FSKILL.md) or\n[coordinator](..\u002Fbeads-coordinator\u002FSKILL.md); authoring uses\n[writer](..\u002Fbeads-writer\u002FSKILL.md).\n\n## Contract\n\nRead [shared delivery model](..\u002F..\u002Freferences\u002Fdelivery-model.md) for packages,\nbranch choices, evidence, recovery and per-member acceptance. This worker writes\ncode, commits, pushes and opens\u002Fupdates its authorized PR. Its lifecycle controller\nowns Beads writes; never claim\u002Frelease\u002Fclose or create follow-up issues here.\nA looper applying these phases performs lifecycle updates separately as holder.\n\nDispatch authorizes accepted scope, tests, ordinary corrections, commits and push;\nedit examples are guidance unless explicitly an ownership boundary. Resolve routine\nengineering choices. Stop only for actual scope\u002Ftrust\u002Farchitecture\u002Fauthorization\nchanges or inaccessible external capability under\n[decision autonomy](..\u002F..\u002Freferences\u002Fdecision-autonomy.md). Keep unaffected work going.\nDo not spawn overlapping implementation tracks or commit Dolt-managed `.beads\u002F`.\n\n## Inputs and continuation\n\n| Field | Meaning |\n|---|---|\n| ISSUE_ID | Existing package anchor; branch defaults to agent\u002F\u003Canchor>, or exact validated delivery.branch |\n| WORKTREE_PATH \u002F REPO_ROOT | Isolated worktree and actual shared repository root |\n| DELIVERY_FILE | Optional beads-delivery\u002Fv1 manifest, required for a multi-bead package |\n| Current packet locator | Current instructions, member AC, authority references and recovery state |\n| REVIEW_CORRECTION_MODE=yes | Continue existing PR using EXISTING_PR_NUMBER, REVIEW_BEAD_ID and CORRECTION_THREADS_JSON |\n\nResume the same Claude session\u002FCodex thread for corrections or a related package.\nA new package revalidates cwd\u002Fbranch\u002Fclaims; guidance and relevant content evidence\ncarry over only while their assumptions hold. A fresh session is recovery with an\nexplicit published packet, never evidence of same-owner continuation by itself.\n\n## Bootstrap\n\n1. Set actual process cwd to WORKTREE_PATH; read\n   [runtime contract](references\u002Fruntime-contract.md) for guidance discovery and\n   protected\u002Fshared Git identity rules.\n2. Invoke [assert_worker_context.py](scripts\u002Fassert_worker_context.py) by absolute\n   skill path with `--worktree-path`, `--repo-root`, `--issue-id`, `--current-path`\n   and, for a package, `--delivery-file`. It rejects an unrelated repository,\n   protected\u002Fwrong branch, manifest mismatch or cwd mismatch. Stop and emit\n   `invalid-runtime-context` if it fails.\n3. Read target AGENTS\u002FCLAUDE and\n   [craft-and-care gate](..\u002F..\u002Freferences\u002Fcraft-and-care-gate.md); reuse unchanged\n   guidance on continuation. Read the concise current operative packet and exact\n   referenced contracts\u002Fsource. Fetch projected current fields only as needed;\n   do not load every member's historical notes or inline archives.\n\n## Implement and verify\n\nInspect the actual source before relying on planning assumptions. Implement logical\ncommits on the package branch, marking member IDs for traceability. Several related\ncorrections can share fixtures\u002Ftests, owner and PR; unrelated outcomes stay separate.\nPreserve each member's actual acceptance and hard gates. Do not silently replace\nan accepted feature with foundation-only scope.\n\nExtend nearest relevant checks under\n[test growth](..\u002F..\u002Freferences\u002Ftest-growth-gate.md). Run scoped checks while iterating;\nthe full required gate runs on the landing tree in the repository-assigned tier\nunder [token efficiency](..\u002F..\u002Freferences\u002Ftoken-efficiency.md). Reuse unchanged\ncontent evidence; refresh affected assumptions and time-sensitive runtime facts.\nNo local duplicate of a required hosted gate is mandated here. No lighter check\nsubstitutes for a repo-required one. Finish applicable craft review before handoff.\n\nOrdinary failing tests\u002FCI and review findings stay with this owner. Correct and\npush to the same PR, then send changed content and tests directly to the independent\nreviewer. The controller receives state-change receipts, not permissions per hunk.\nIf a shared prerequisite\u002Fauthority boundary is missing, name exactly its dependent\nwork and resume event; never create a second substrate implementation privately.\n\n## Publish and handoff\n\nPrefer one PR per cohesive package, targeting the approved integration base.\nPush the exact accepted implementation branch and use `gh pr create --body-file` with actual newlines.\nPR maps every member to acceptance\u002Fevidence and explicitly names partial scope.\nOnly the lifecycle controller sets anchor `external_ref` and one review relation.\n\nIn correction mode update EXISTING_PR_NUMBER; do not create a new PR\u002Freview record.\nUse ordinary push for appended commits; `--force-with-lease` only for a justified\nhistory rewrite. Verify PR head and base after pushing. Never put runtime session\nURLs or session-attribution trailers in commits\u002FPRs.\n\nA direct-merge candidate is only a repository-permitted trivial change with an\nindependent verdict and the required local gate; a merge queue\u002Frequired review\ncannot be bypassed by calling it direct. When policy is unknown, use the PR path.\nAn intermediate integration branch is accumulation, never proof of main delivery.\n\nOn push\u002FPR failure follow [runtime failure routing](references\u002Fruntime-contract.md):\none justified local retry, then a precise external-blocker receipt. Preserve useful\ncommits, remote branch and dirty\u002Flocal-only work. Never delete a worktree because\nreview begins. Session preemption\u002Frecovery publishes packet\u002Fclaims\u002Fhead\u002Ffindings and\nexplicit handoff rather than reallocating ordinary corrections.\n\n## Report\n\nUse [emit_worker_report.py](scripts\u002Femit_worker_report.py); field schemas\u002Fexamples\nare in [worker-report.md](references\u002Fworker-report.md). Multi-bead reports include\n`--delivery-file` and complete `--member-results-json` coverage, individually\nsatisfied, partial or blocked with evidence. Ready-for-review does not close any\nmember. Acceptance-inclusive runtime proof may still be unmet after source merge.\n\nStatuses remain `completed-pr-opened`, `completed-direct-merge-candidate`,\n`blocked-awaiting-coordinator`, `invalid-runtime-context`. “Completed” describes\nthis handoff, never the whole owner outcome. Include recovery state and exact resume\nevent when blocked. Current correctness discoveries stay in this package; genuinely\nnew behavior is reported separately after dedupe, without silently expanding scope.\n\nFinish on a report, never a plan or promise. Search\n[known errors](..\u002F..\u002Freferences\u002Fknown-errors.md) before debugging an unfamiliar\ntracker\u002FPR failure and record newly confirmed reusable fixes there.\n",{"name":5,"metadata":43,"description":7,"compatibility":50},{"owner":44,"status":45,"authors":46,"last_reviewed":49},"tze","active",[44,47,48],"OpenAI Codex","Claude Fable 5.1","2026-11-06","Requires a Beads-backed git repository with git worktrees, git, bd, jq, gh, and python3 available, plus authenticated GitHub access and network access for push and PR operations.","main","ac0f8a90dbdbae93825f4db9614ade0d6872c26d","skills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-worker","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap","https:\u002F\u002Fgithub.com\u002Ftzeusy-org","2026-11-10 23:17:25",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add tzeusy-org\u002Fai-bootstrap --skill beads-worker",{"tool":63,"command":64},"bunx","bunx skills add tzeusy-org\u002Fai-bootstrap --skill beads-worker",{"tool":66,"command":67},"pnpm","pnpm dlx skills add tzeusy-org\u002Fai-bootstrap --skill beads-worker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-worker\u002FSKILL.md",true,[71,77,81,85,91,95,99],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"agents\u002Fopenai.yaml","REFERENCE","参考文档",332,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-worker\u002Fagents\u002Fopenai.yaml",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fruntime-contract.md",5852,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-worker\u002Freferences\u002Fruntime-contract.md",{"path":82,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fworker-report.md",5176,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-worker\u002Freferences\u002Fworker-report.md",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fassert_worker_context.py","SCRIPT","脚本",5018,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-worker\u002Fscripts\u002Fassert_worker_context.py",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Femit_worker_report.py",10344,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-worker\u002Fscripts\u002Femit_worker_report.py",{"path":96,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":97,"sourceHtmlUrl":98},"tests\u002Ftest_skill_package.py",3372,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-worker\u002Ftests\u002Ftest_skill_package.py",{"path":100,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":101,"sourceHtmlUrl":102},"tests\u002Ftest_worker_helpers.py",23412,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-worker\u002Ftests\u002Ftest_worker_helpers.py",[104,128,155,170,188,199],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":38},"01M6DAZD21TWH2ET70V9FF75CQ","user-run","Use when a step needs privileges this session lacks (docker, sudo, another user's checkout or secrets, host access) and the owner must run it as tze. Writes a reviewable \u002Fhome\u002Forca\u002F.tmp\u002F\u003Cslug>\u002Frun.sh that impersonates tze (USER_TO_IMPERSONATE overrides), tees timestamped logs plus latest.log and collects artifacts there; Claude presents it with a risk and time brief, then continues from the logs. Triggers: \"I'll run it for you\", \"permission denied on docker.sock\", \"needs sudo\", \"sudo: a password is required\", \"run as tze\", \"\u002Fuser-run\".","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fuser-run\u002FSKILL.md",[],[111,112,113,114,115,32,116,117,118,119,45,120,121,122,123,124,31,125,126,127],"user run","user","run","docker","logs","host","as","triggers","permission","time","log","artifacts","session","password","secrets","risk","brief",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":144,"publishedAt":38},"01M6DAZAHTCBAD2WF0GAHWPST8","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fth-workflow\u002Fsubskills\u002Frequesting-code-review\u002FSKILL.md",[134,139],{"categoryNo":135,"categoryName":136,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[145,146,147,148,149,150,45,151,152,32,153,154],"requesting code review","code","review","code review","work","requirements","upstream","superpowers","verify","tasks",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":163,"publishedAt":38},"01M6DAZ7CJ82D81XZB2YHVVY48","receiving-code-review","Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fth-workflow\u002Fsubskills\u002Freceiving-code-review\u002FSKILL.md",[161,162],{"categoryNo":135,"categoryName":136,"taxonomyType":137,"taxonomyTypeDesc":138},{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},[164,146,147,148,45,151,165,152,32,166,167,168,169],"receiving code review","implementation","code review feedback","technical","feedback","verification",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":38},"01M6DAZ4ER76ADXJ9KRFP7V3Q9","finishing-a-development-branch","Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fth-workflow\u002Fsubskills\u002Ffinishing-a-development-branch\u002FSKILL.md",[],[177,178,179,180,32,181,149,182,183,34,152,184,185,186,45,151,187,165],"branch","development","finishing a development branch","integrate","decide","how","cleanup","merge","tests","structured","options",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":38},"01M6DAYZFWWW2YPKP89QNQR96H","executing-plans","Use when you have a written implementation plan to execute in a separate session with review checkpoints","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fth-workflow\u002Fsubskills\u002Fexecuting-plans\u002FSKILL.md",[],[195,196,197,147,198,45,151,165,152,32,123],"plans","executing plans","plan","execute",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":205,"publishedAt":38},"01M6DAYWM2YQHYCK7C35K1D29J","dispatching-parallel-agents","Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fth-workflow\u002Fsubskills\u002Fdispatching-parallel-agents\u002FSKILL.md",[],[206,207,208,32,152,151,209,45,210,154,211],"parallel agents","parallel","dispatching parallel agents","state","dependencies","shared"]