[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JB69VC66D29ZR6HBXJQ6R":3,"skill-same:01M71JB69VC66D29ZR6HBXJQ6R":77},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M71JB69VC66D29ZR6HBXJQ6R","respond-review",null,"Act on a reviewer agent's feedback systematically — categorize findings, apply fixes, verify tests still pass. Use after request-review returns a report, or when user wants to work through code review findings.","danielvm-git\u002Fbigpowers","danielvm-git","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1020864?v=4","01M71H1N1CTQ529S0KN7KETVG6","Daniel V M","01M71H1N218Y3S8WHCJ58NPRSW",292,"MIT","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Frespond-review\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"review","respond review","respond","apply","use","tests","fixes","feedback","returns","sonnet","act","request","work","reviewer","code","when","code review","review findings","code review findings","categorize","2026-11-10 10:12:30",false,"---\nname: respond-review\nmodel: sonnet\ndescription: \"Act on a reviewer agent's feedback systematically — categorize findings, apply fixes, verify tests still pass. Use after request-review returns a report, or when user wants to work through code review findings.\"\n---\n\n# Respond Review\n> **HARD GATE** — **HARD GATE** — Every reviewer comment must be addressed (fix, disagree + document reason, or ask clarification). Do NOT ignore feedback and merge.\n\n\nWork through reviewer findings systematically. Don't apply changes blindly — categorize first, then decide, then fix, then verify.\n\n## Process\n\n### 1. Read the full review report\n\nRead every finding before acting on any of them. Get the full picture first.\n\n### 2. Categorize findings\n\nFor each finding, assign a category:\n\n| Category | Meaning | Action |\n|----------|---------|--------|\n| **must-fix** | Correctness bug, security issue, test failure, CONVENTIONS.md violation | Fix before proceeding |\n| **should-fix** | Code quality issue, naming, clarity — worth fixing but not blocking | Fix if time allows |\n| **consider** | Architectural suggestion, alternative approach — may or may not apply | Discuss with user |\n\nCreate a numbered list of all findings with their categories.\n\n### 3. Confirm with user (for consider-category items)\n\nFor each \"consider\" item, briefly describe the trade-off and ask: \"Apply, skip, or discuss?\"\n\n### 4. Apply must-fix items first\n\nFix every must-fix item. For each one:\n- Describe what you're changing and why\n- Make the change\n- Run the verify command if one exists for this area\n\n### 5. Apply should-fix items\n\nApply should-fix items. If any are large enough to warrant their own commit, note them separately.\n\n### 6. Run the full suite\n\nAfter all changes are applied:\n\n```bash\n\u003Cfull test command>\n\u003Ctypecheck command>\n\u003Clint command>\n```\n\n- [ ] All tests pass\n- [ ] No type errors\n- [ ] No lint violations\n\n### 7. Report\n\nSummarize what was applied and what was skipped:\n\n```\nApplied (must-fix): #1, #2, #3\nApplied (should-fix): #4\nSkipped (consider): #5 — agreed with user to defer\nAll tests pass.\n```\n\nSuggest next skill: `commit-message`.\n","# Respond Review\n> **HARD GATE** — **HARD GATE** — Every reviewer comment must be addressed (fix, disagree + document reason, or ask clarification). Do NOT ignore feedback and merge.\n\n\nWork through reviewer findings systematically. Don't apply changes blindly — categorize first, then decide, then fix, then verify.\n\n## Process\n\n### 1. Read the full review report\n\nRead every finding before acting on any of them. Get the full picture first.\n\n### 2. Categorize findings\n\nFor each finding, assign a category:\n\n| Category | Meaning | Action |\n|----------|---------|--------|\n| **must-fix** | Correctness bug, security issue, test failure, CONVENTIONS.md violation | Fix before proceeding |\n| **should-fix** | Code quality issue, naming, clarity — worth fixing but not blocking | Fix if time allows |\n| **consider** | Architectural suggestion, alternative approach — may or may not apply | Discuss with user |\n\nCreate a numbered list of all findings with their categories.\n\n### 3. Confirm with user (for consider-category items)\n\nFor each \"consider\" item, briefly describe the trade-off and ask: \"Apply, skip, or discuss?\"\n\n### 4. Apply must-fix items first\n\nFix every must-fix item. For each one:\n- Describe what you're changing and why\n- Make the change\n- Run the verify command if one exists for this area\n\n### 5. Apply should-fix items\n\nApply should-fix items. If any are large enough to warrant their own commit, note them separately.\n\n### 6. Run the full suite\n\nAfter all changes are applied:\n\n```bash\n\u003Cfull test command>\n\u003Ctypecheck command>\n\u003Clint command>\n```\n\n- [ ] All tests pass\n- [ ] No type errors\n- [ ] No lint violations\n\n### 7. Report\n\nSummarize what was applied and what was skipped:\n\n```\nApplied (must-fix): #1, #2, #3\nApplied (should-fix): #4\nSkipped (consider): #5 — agreed with user to defer\nAll tests pass.\n```\n\nSuggest next skill: `commit-message`.\n",{"name":5,"model":38,"description":7},"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa",".opencode\u002Fskills\u002Frespond-review",23,"https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers","https:\u002F\u002Fdanielvm-git.github.io\u002Fbigpowers\u002F","https:\u002F\u002Fgithub.com\u002Fdanielvm-git","danielvm.net","2026-11-10 01:18:54",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add danielvm-git\u002Fbigpowers --skill respond-review",{"tool":69,"command":70},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill respond-review",{"tool":72,"command":73},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill respond-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Frespond-review\u002FSKILL.md",true,[],[78,97,104,131,154,175],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":87,"publishedAt":49},"01M71KBG9F8X644MJB16H4V8M7","skill-verify-fail-open-fixture","Negative-path fixture for run-skill-verify.sh — must never PASS.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fskill-verify-fail-open\u002FSKILL.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[88,89,90,91,92,93,94,95,96],"fixture","open","verify","skill verify fail open fixture","skill verify","path","run","for","never",{"skillNo":98,"name":99,"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":100,"categories":101,"keywords":102,"publishedAt":49},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[103,93],"negative path",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":113,"publishedAt":49},"01M71KBBGF7Y4EB4AMHBZ8CJFC","write-document","Write, organize, and sync high-integrity technical documents using the BMAD methodology. Ensures every document is Bold, Minimal, Actionable, and Durable. Use when creating architectural docs, technical guides, or organizing the specs\u002F directory.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-document\u002FSKILL.md",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",[114,115,116,117,118,119,120,121,122,123,33,44,124,125,38,126,127,128,129,130],"write","write document","document","documents","actionable","technical","methodology","high","bmad","standard","minimal","bold","integrity","organize","sync","directory","guides",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":49},"01M71KB8TM089JJD5AY5KAFSDM","wire-observability","Add structured JSON logging, observability commands, and idempotent setup scripts to a project. Use when a project needs production-readiness instrumentation, when user wants structured logging, or as a production-readiness gate at any phase of development.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwire-observability\u002FSKILL.md",[],[138,139,140,123,141,33,142,143,144,145,38,146,147,148,149,150,151,44,152,153],"observability","wire observability","readiness","commands","development","as","logging","add","instrumentation","at","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":49},"01M71KB6CNRANP449DQA3NJZ96","wire-ci","CI pipeline setup with bundled, forge-neutral templates and local validation. Detects the forge from the git remote, generates workflows for supported forges, and skips honestly for the rest. The CI equivalent of wire-observability.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwire-ci\u002FSKILL.md",[],[161,162,163,164,165,166,167,168,169,170,171,123,172,95,138,38,173,174],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","with","ci pipeline setup","git","workflows",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":188,"publishedAt":49},"01M71KB2ZV98P03X88QR8MT9F1","visual-dashboard","Start a browser-based dashboard that visualizes architecture, implementation plans, and project status. Persists artifacts in .bigpowers\u002Fdashboard\u002F. Reads specs\u002Fstate.yaml, release-plan.yaml, epics, and planning-status via HTTP API or opencode panel.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-dashboard\u002FSKILL.md",[181,184,185],{"categoryNo":182,"categoryName":183,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},{"categoryNo":186,"categoryName":187,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[189,190,191,192,193,194,195,196,197,38,198,199,200,201,202,203,204,152,205,206],"dashboard","visual","visual dashboard","status","artifacts","http","plans","planning","panel","start","release","opencode","plan","browser","api","architecture","project status","http api"]