[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6R7BVT80AMHTRS7NDGP6FQ3":3,"skill-same:01M6R7BVT80AMHTRS7NDGP6FQ3":68},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6R7BVT80AMHTRS7NDGP6FQ3","cc-update-review",null,"Reviews PRs that modify the Feature Table in CLAUDE.md. Use when a PR adds CC version rows or modifies docs\u002FCLAUDE-feature-table.md.","tim-hub\u002Fpowerball-harness","tim-hub","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2884320?v=4","01M6R7B70M93Y25SH3DV1B4Q26","Tim","01M6R7B74YQWC556YVC0FRVS3T",35,"MIT","https:\u002F\u002Fgithub.com\u002Ftim-hub\u002Fpowerball-harness\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fcc-update-review\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"review","update","cc update review","cc","docs","pr","table","grep","read","use","version","feature","false","reviews","prs","when","2026-11-10 10:12:30",false,"---\nname: cc-update-review\ndescription: \"Reviews PRs that modify the Feature Table in CLAUDE.md. Use when a PR adds CC version rows or modifies docs\u002FCLAUDE-feature-table.md.\"\nwhen_to_use: \"Feature Table PR, CC version PR, CLAUDE.md feature table, cc-update-review\"\nuser-invocable: false\nallowed-tools: [\"Read\", \"Grep\", \"Glob\"]\n---\n\n# CC Update Review Guardrail\n\nA quality guardrail that prevents \"doc-only\" additions to the Feature Table during Claude Code update integration.\nAutomatically classifies whether Feature Table additions are accompanied by implementation, and forces output of implementation proposals when lacking.\n\n## Quick Reference\n\nThis skill is triggered in the following situations:\n\n- When reviewing **CC update integration PRs**\n- When a diff is detected with new rows added to the **Feature Table** (`CLAUDE.md` \u002F `docs\u002FCLAUDE-feature-table.md`)\n- Internal invocation when `\u002Fharness-review` determines a PR is a CC integration PR\n\nSituations where this skill is **not** triggered:\n\n- Normal implementation work (`\u002Fwork`)\n- Changes only to files other than the Feature Table\n- Setup and initialization work\n\n## 3-Category Classification\n\nEach item added to the Feature Table is classified into the following 3 categories.\n\n### (A) Has Implementation\n\n**Definition**: Implementation changes to hooks \u002F scripts \u002F agents \u002F skills \u002F core corresponding to the Feature Table addition are included in the same PR.\n\n**Criteria**:\n- Files related to the feature mentioned in the Feature Table row have been changed\n- There is a diff in hooks.json, skill SKILL.md, agent .md, scripts\u002F*.sh, or core\u002Fsrc\u002F*.ts\n\n**Examples**:\n\n| Feature Table Addition | Corresponding Implementation Change | Classification |\n|-----------------------|-------------------------------------|---------------|\n| `PostCompact hook` | `hooks\u002Fpost-compact-handler.sh` newly created | A |\n| `MCP Elicitation support` | Elicitation event added to `hooks.json` + `elicitation-handler.sh` created | A |\n| `Worker maxTurns limit` | maxTurns field added to `agents\u002Fworker.md` | A |\n\n**Result**: OK. No additional action needed.\n\n---\n\n### (B) Doc-Only\n\n**Definition**: Rows were added only to the Feature Table with no Harness-side implementation changes. Also does not qualify as CC auto-inherited (Category C).\n\n**Criteria**:\n- New rows exist in the Feature Table\n- No related changes to hooks \u002F scripts \u002F agents \u002F skills \u002F core in the same PR\n- The feature is one where Harness should provide its own added value (configuration, workflow integration, guardrails, etc.)\n\n**Examples**:\n\n| Feature Table Addition | Corresponding Implementation Change | Classification |\n|-----------------------|-------------------------------------|---------------|\n| `PreCompact hook` | None (Feature Table only) | B |\n| `Agent Teams` | None (Feature Table only) | B |\n| `Desktop Scheduled Tasks` | None (Feature Table only) | B |\n\n**Result**: NG. Block the PR and require an implementation proposal. Output format described below.\n\n---\n\n### (C) CC Auto-Inherited\n\n**Definition**: Items such as Claude Code core performance improvements, bug fixes, and internal optimizations that require no Harness-side changes.\n\n**Criteria**:\n- A CC core fix with no room for Harness to wrap or extend\n- Performance improvements, memory leak fixes, UI improvements, etc.\n- Internal changes that do not affect Harness workflows\n\n**Examples**:\n\n| Feature Table Addition | Reason | Classification |\n|-----------------------|--------|---------------|\n| `Streaming API memory leak fix` | CC internal memory leak fix. No Harness-side action needed | C |\n| `Compaction image retention` | CC retains images during compaction. No Harness changes needed | C |\n| `Parallel tool call fix` | CC internal parallel execution fix. Benefits are automatic | C |\n\n**Result**: OK. However, \"CC auto-inherited\" must be explicitly noted in the Feature Table column.\n\n## CC Update PR Checklist\n\nVerify the following in order during PR review:\n\n```\n## CC Update Integration Checklist\n\n### 1. Extract Feature Table Diff\n- [ ] List added rows from the diff of `CLAUDE.md` or `docs\u002FCLAUDE-feature-table.md`\n\n### 2. Classify Each Item\n- [ ] Determine A \u002F B \u002F C for each added row\n- [ ] Confirm that Category B items are 0\n\n### 3. Per-Category Verification\n- [ ] (A) Has implementation: Are corresponding implementation files correctly linked?\n- [ ] (B) Doc-only: Has an implementation proposal been provided? (Block PR if not 0)\n- [ ] (C) CC auto-inherited: Is \"CC auto-inherited\" explicitly noted in the Feature Table?\n\n### 4. CHANGELOG Verification\n- [ ] Are Category A items documented in the CHANGELOG in \"Before \u002F After\" format?\n- [ ] Are Category C items documented in the CHANGELOG as CC auto-inherited?\n\n### Classification Results\n\n| # | Feature Table Item | Category | Corresponding File \u002F Notes |\n|---|-------------------|----------|---------------------------|\n| 1 | (item name) | A \u002F B \u002F C | (file path or notes) |\n| 2 | (item name) | A \u002F B \u002F C | (file path or notes) |\n```\n\n## Output Format When Category B Is Detected\n\nWhen 1 or more Category B items are detected, output an implementation proposal in the following format.\n**This output is mandatory and cannot be omitted.**\n\n```\n## Category B Detected: Implementation Proposals\n\n### B-{number}. {Feature Table item name}\n\n**Current state**: Listed in Feature Table only. No Harness-side implementation.\n\n**Harness-specific added value**:\n{Specific explanation of how Harness should leverage this feature}\n\n**Implementation proposal**:\n\n| Target File | Change Description |\n|------------|-------------------|\n| `{file path}` | {specific change description} |\n| `{file path}` | {specific change description} |\n\n**User experience improvement**:\n- Before: {current user experience}\n- After: {user experience after implementation}\n\n**Implementation priority**: {High \u002F Medium \u002F Low}\n**Estimated effort**: {Small \u002F Medium \u002F Large}\n```\n\n### Output Example\n\n```\n## Category B Detected: Implementation Proposals\n\n### B-1. Desktop Scheduled Tasks\n\n**Current state**: Listed in Feature Table only. No Harness-side implementation.\n\n**Harness-specific added value**:\nIntegrate Scheduled Tasks with Harness workflows to automate periodic quality checks,\nstatus syncing, and memory cleanup.\n\n**Implementation proposal**:\n\n| Target File | Change Description |\n|------------|-------------------|\n| `skills\u002Fharness-work\u002Freferences\u002Fscheduled-tasks.md` | Scheduled task templates and guide |\n| `scripts\u002Fsetup-scheduled-tasks.sh` | Initial setup script |\n| `hooks\u002Fhooks.json` | Cron trigger registration |\n\n**User experience improvement**:\n- Before: Users had to manually run periodic tasks\n- After: Harness automatically runs periodic quality checks and notifies with results\n\n**Implementation priority**: Medium\n**Estimated effort**: Medium\n```\n\n## Recommended \"Added Value\" Column\n\nIt is recommended to add the following column to the Feature Table:\n\n| Feature | Skill | Purpose | Added Value |\n|---------|-------|---------|-------------|\n| PostCompact hook | hooks | Context re-injection | A: Has implementation |\n| Streaming leak fix | all | Memory leak fix | C: CC auto-inherited |\n\nThis column makes it possible to verify each item's classification at a glance and prevent Category B items from remaining.\n\n## Related Skills\n\n- `harness-review` - Code review (internally invokes this skill when a CC integration PR is detected)\n- `harness-work` - Implementation work (when working based on Category B implementation proposals)\n- `memory` - SSOT management (recording classification criteria decisions)\n","# CC Update Review Guardrail\n\nA quality guardrail that prevents \"doc-only\" additions to the Feature Table during Claude Code update integration.\nAutomatically classifies whether Feature Table additions are accompanied by implementation, and forces output of implementation proposals when lacking.\n\n## Quick Reference\n\nThis skill is triggered in the following situations:\n\n- When reviewing **CC update integration PRs**\n- When a diff is detected with new rows added to the **Feature Table** (`CLAUDE.md` \u002F `docs\u002FCLAUDE-feature-table.md`)\n- Internal invocation when `\u002Fharness-review` determines a PR is a CC integration PR\n\nSituations where this skill is **not** triggered:\n\n- Normal implementation work (`\u002Fwork`)\n- Changes only to files other than the Feature Table\n- Setup and initialization work\n\n## 3-Category Classification\n\nEach item added to the Feature Table is classified into the following 3 categories.\n\n### (A) Has Implementation\n\n**Definition**: Implementation changes to hooks \u002F scripts \u002F agents \u002F skills \u002F core corresponding to the Feature Table addition are included in the same PR.\n\n**Criteria**:\n- Files related to the feature mentioned in the Feature Table row have been changed\n- There is a diff in hooks.json, skill SKILL.md, agent .md, scripts\u002F*.sh, or core\u002Fsrc\u002F*.ts\n\n**Examples**:\n\n| Feature Table Addition | Corresponding Implementation Change | Classification |\n|-----------------------|-------------------------------------|---------------|\n| `PostCompact hook` | `hooks\u002Fpost-compact-handler.sh` newly created | A |\n| `MCP Elicitation support` | Elicitation event added to `hooks.json` + `elicitation-handler.sh` created | A |\n| `Worker maxTurns limit` | maxTurns field added to `agents\u002Fworker.md` | A |\n\n**Result**: OK. No additional action needed.\n\n---\n\n### (B) Doc-Only\n\n**Definition**: Rows were added only to the Feature Table with no Harness-side implementation changes. Also does not qualify as CC auto-inherited (Category C).\n\n**Criteria**:\n- New rows exist in the Feature Table\n- No related changes to hooks \u002F scripts \u002F agents \u002F skills \u002F core in the same PR\n- The feature is one where Harness should provide its own added value (configuration, workflow integration, guardrails, etc.)\n\n**Examples**:\n\n| Feature Table Addition | Corresponding Implementation Change | Classification |\n|-----------------------|-------------------------------------|---------------|\n| `PreCompact hook` | None (Feature Table only) | B |\n| `Agent Teams` | None (Feature Table only) | B |\n| `Desktop Scheduled Tasks` | None (Feature Table only) | B |\n\n**Result**: NG. Block the PR and require an implementation proposal. Output format described below.\n\n---\n\n### (C) CC Auto-Inherited\n\n**Definition**: Items such as Claude Code core performance improvements, bug fixes, and internal optimizations that require no Harness-side changes.\n\n**Criteria**:\n- A CC core fix with no room for Harness to wrap or extend\n- Performance improvements, memory leak fixes, UI improvements, etc.\n- Internal changes that do not affect Harness workflows\n\n**Examples**:\n\n| Feature Table Addition | Reason | Classification |\n|-----------------------|--------|---------------|\n| `Streaming API memory leak fix` | CC internal memory leak fix. No Harness-side action needed | C |\n| `Compaction image retention` | CC retains images during compaction. No Harness changes needed | C |\n| `Parallel tool call fix` | CC internal parallel execution fix. Benefits are automatic | C |\n\n**Result**: OK. However, \"CC auto-inherited\" must be explicitly noted in the Feature Table column.\n\n## CC Update PR Checklist\n\nVerify the following in order during PR review:\n\n```\n## CC Update Integration Checklist\n\n### 1. Extract Feature Table Diff\n- [ ] List added rows from the diff of `CLAUDE.md` or `docs\u002FCLAUDE-feature-table.md`\n\n### 2. Classify Each Item\n- [ ] Determine A \u002F B \u002F C for each added row\n- [ ] Confirm that Category B items are 0\n\n### 3. Per-Category Verification\n- [ ] (A) Has implementation: Are corresponding implementation files correctly linked?\n- [ ] (B) Doc-only: Has an implementation proposal been provided? (Block PR if not 0)\n- [ ] (C) CC auto-inherited: Is \"CC auto-inherited\" explicitly noted in the Feature Table?\n\n### 4. CHANGELOG Verification\n- [ ] Are Category A items documented in the CHANGELOG in \"Before \u002F After\" format?\n- [ ] Are Category C items documented in the CHANGELOG as CC auto-inherited?\n\n### Classification Results\n\n| # | Feature Table Item | Category | Corresponding File \u002F Notes |\n|---|-------------------|----------|---------------------------|\n| 1 | (item name) | A \u002F B \u002F C | (file path or notes) |\n| 2 | (item name) | A \u002F B \u002F C | (file path or notes) |\n```\n\n## Output Format When Category B Is Detected\n\nWhen 1 or more Category B items are detected, output an implementation proposal in the following format.\n**This output is mandatory and cannot be omitted.**\n\n```\n## Category B Detected: Implementation Proposals\n\n### B-{number}. {Feature Table item name}\n\n**Current state**: Listed in Feature Table only. No Harness-side implementation.\n\n**Harness-specific added value**:\n{Specific explanation of how Harness should leverage this feature}\n\n**Implementation proposal**:\n\n| Target File | Change Description |\n|------------|-------------------|\n| `{file path}` | {specific change description} |\n| `{file path}` | {specific change description} |\n\n**User experience improvement**:\n- Before: {current user experience}\n- After: {user experience after implementation}\n\n**Implementation priority**: {High \u002F Medium \u002F Low}\n**Estimated effort**: {Small \u002F Medium \u002F Large}\n```\n\n### Output Example\n\n```\n## Category B Detected: Implementation Proposals\n\n### B-1. Desktop Scheduled Tasks\n\n**Current state**: Listed in Feature Table only. No Harness-side implementation.\n\n**Harness-specific added value**:\nIntegrate Scheduled Tasks with Harness workflows to automate periodic quality checks,\nstatus syncing, and memory cleanup.\n\n**Implementation proposal**:\n\n| Target File | Change Description |\n|------------|-------------------|\n| `skills\u002Fharness-work\u002Freferences\u002Fscheduled-tasks.md` | Scheduled task templates and guide |\n| `scripts\u002Fsetup-scheduled-tasks.sh` | Initial setup script |\n| `hooks\u002Fhooks.json` | Cron trigger registration |\n\n**User experience improvement**:\n- Before: Users had to manually run periodic tasks\n- After: Harness automatically runs periodic quality checks and notifies with results\n\n**Implementation priority**: Medium\n**Estimated effort**: Medium\n```\n\n## Recommended \"Added Value\" Column\n\nIt is recommended to add the following column to the Feature Table:\n\n| Feature | Skill | Purpose | Added Value |\n|---------|-------|---------|-------------|\n| PostCompact hook | hooks | Context re-injection | A: Has implementation |\n| Streaming leak fix | all | Memory leak fix | C: CC auto-inherited |\n\nThis column makes it possible to verify each item's classification at a glance and prevent Category B items from remaining.\n\n## Related Skills\n\n- `harness-review` - Code review (internally invokes this skill when a CC integration PR is detected)\n- `harness-work` - Implementation work (when working based on Category B implementation proposals)\n- `memory` - SSOT management (recording classification criteria decisions)\n",{"name":5,"description":7,"when_to_use":40,"allowed-tools":41,"user-invocable":36},"Feature Table PR, CC version PR, CLAUDE.md feature table, cc-update-review",[42,43,44],"Read","Grep","Glob","master","cf086c6a667d37610d30a4236b94d8ab02e4efc5",".claude\u002Fskills\u002Fcc-update-review",0,"https:\u002F\u002Fgithub.com\u002Ftim-hub\u002Fpowerball-harness","https:\u002F\u002Fgithub.com\u002Ftim-hub","https:\u002F\u002Ftim.bai.uno","Building things.","2026-08-05 17:45:08",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add tim-hub\u002Fpowerball-harness --skill cc-update-review",{"tool":60,"command":61},"bunx","bunx skills add tim-hub\u002Fpowerball-harness --skill cc-update-review",{"tool":63,"command":64},"pnpm","pnpm dlx skills add tim-hub\u002Fpowerball-harness --skill cc-update-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftim-hub\u002Fpowerball-harness\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fcc-update-review\u002FSKILL.md",true,[],[69,86,94,120,139,145],{"skillNo":70,"name":71,"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":72,"categories":73,"keywords":79,"publishedAt":35},"01M6R7GH70ABV40CS95W4WWMQZ","escape-skill","https:\u002F\u002Fgithub.com\u002Ftim-hub\u002Fpowerball-harness\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskills\u002Fzz-review-escape\u002FSKILL.md",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[80,81,82,83,84,31,85],"escape skill","escape","quoted","path","true","Tools",{"skillNo":87,"name":88,"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":89,"categories":90,"keywords":91,"publishedAt":35},"01M6R7G8A2BQHYTAR39BY7X3GK","zz-review-empty","https:\u002F\u002Fgithub.com\u002Ftim-hub\u002Fpowerball-harness\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskills\u002Fzz-review-empty\u002FSKILL.md",[],[19,92,93,84,31],"zz review empty","empty",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":101,"publishedAt":35},"01M6R7G3XH6C43JKP2RX1SZW6V","harness-schedule-run","Use when running Plans.md tasks on a scheduled cadence (fresh context per wake-up, sprint-contract flow, plateau detection, flock guard). Do NOT load for: single-task work (harness-work), planning, review, release.","https:\u002F\u002Fgithub.com\u002Ftim-hub\u002Fpowerball-harness\u002Fblob\u002Fmaster\u002Fharness\u002Ftemplates\u002Fopencode\u002Fskills\u002Fharness-schedule-run\u002FSKILL.md",[100],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},[102,103,104,105,19,106,107,108,109,110,34,111,112,113,114,115,116,117,118,119],"run","harness schedule run","harness","schedule","tasks","ci","MCP","mem","wake","sprint-contract","Bash","scheduled","cadence","sprint","fresh","worker","up","work",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":35},"01M6R7FY3ZVYDDKXBT3D7QSFFK","harness-work","Use when implementing, executing, or running Plans.md tasks — single task, parallel workers, or full team\u002Fbreezing run. Accepts specific task numbers or ranges. Do NOT load for: planning, review, release, or setup.","https:\u002F\u002Fgithub.com\u002Ftim-hub\u002Fpowerball-harness\u002Fblob\u002Fmaster\u002Fharness\u002Ftemplates\u002Fcodex-skills\u002Fharness-work\u002FSKILL.md",[],[127,104,119,128,34,129,130,131,132,133,134,135,136,112,137,102,106,138,19,27],"harness work","full","implementing","mode","number","breezing","auto","edit","write","team","release","commit",{"skillNo":140,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":144,"publishedAt":35},"01M6R7FGP3R612506A5GKMBF5C","https:\u002F\u002Fgithub.com\u002Ftim-hub\u002Fpowerball-harness\u002Fblob\u002Fmaster\u002Fharness\u002Ftemplates\u002Fcodex-skills\u002Fharness-schedule-run\u002FSKILL.md",[143],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},[103,104,102,105,19,108,106,113,34,111,110,114,115,116,117,109,118,119,112,107],{"skillNo":146,"name":132,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":35},"01M6R7FCDN9AS7RSQFGZWHTF7F","Use when running the full team\u002Fbreezing flow end-to-end — all tasks with parallel workers. Do NOT load for: single-task implementation, planning, review, release, or setup.","https:\u002F\u002Fgithub.com\u002Ftim-hub\u002Fpowerball-harness\u002Fblob\u002Fmaster\u002Fharness\u002Ftemplates\u002Fcodex-skills\u002Fbreezing\u002FSKILL.md",[],[132,134,151,34,152,130,153,154,128,133,135,27,155,112,136,156,137,106,138,19],"running","single-task","websearch","end","parallel","flow"]