[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HT0SA82WHWDTFM22CTSHV":3,"skill-same:01M71HT0SA82WHWDTFM22CTSHV":65},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M71HT0SA82WHWDTFM22CTSHV","fix-bug",null,"Bug fix orchestrator — active_flow fix_bug; reads specs\u002Fbugs\u002FBUG-*.md; chains investigate-bug, develop-tdd, validate-fix. Use when user reports a defect.","danielvm-git\u002Fbigpowers","danielvm-git","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1020864?v=4","01M71H1N1CTQ529S0KN7KETVG6","Daniel V M","01M71H1N218Y3S8WHCJ58NPRSW",289,"MIT","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.copilot\u002Fskills\u002Ffix-bug\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"fix bug","fix","bug","orchestrator","when","defect","bugs","sonnet","active","reports","use","tdd","user","develop","bug fix","investigate","flow","validate","2026-11-10 10:12:30",false,"---\nname: fix-bug\nmodel: sonnet\ndescription: \"Bug fix orchestrator — active_flow fix_bug; reads specs\u002Fbugs\u002FBUG-*.md; chains investigate-bug, develop-tdd, validate-fix. Use when user reports a defect.\"\n---\n\n# Fix Bug\n\n**Boundary**: Orchestrator flow — chains `investigate-bug` (entry point + RCA via `diagnose-root`) → `develop-tdd` → `validate-fix`. Does not implement RCA or write bug files directly.\n\nOrchestrates **fix_bug** flow without mixing epic build state.\n\n> **HARD GATE** — Set `specs\u002Fstate.yaml` `active_flow: fix_bug` and `bug_cycle.current_step: 1` before starting.\n\n## Discovered gate failures (e51s04)\n\nValid entry **without a user-reported bug** when:\n\n- **Preflight** or **CI** is red at kickoff or verify-work\n- **Golden suite** or project baseline is red (`bash scripts\u002Frun-verification-gates.sh` or equivalent)\n- A reproducible gate failure during unrelated epic work exceeds quick-fix guardrails\n\nCreate `specs\u002Fbugs\u002FBUG-*.md` via `investigate-bug` (or inline in fix-bug step 1) describing the gate failure, then run the standard fix_bug chain.\n\n## Five steps (`bug_cycle` in state.yaml)\n\n| Step | Skill \u002F action |\n|------|----------------|\n| 1 | `investigate-bug` — create BUG-*.md with RCA |\n| 2 | `diagnose-root` — 4-phase root cause analysis |\n| 3 | `develop-tdd` — red-green against bug file verify steps |\n| 4 | `validate-fix` — re-run failing test, full suite, lint |\n| 5 | `release-branch` — PR or solo land the fix |\n\n### Checkpoint \u002F resume\n\nTrack progress via `specs\u002Fstate.yaml` `bug_cycle`:\n- `bug_cycle.current_step`: current step (1–5)\n- `bug_cycle.completed_steps`: completed step numbers\n- `handoff.next_skill`: skill for the current step\n- On resume, read `bug_cycle.current_step` and continue from there\n\n## Process\n\n1. **Step 1 — investigate-bug:** If no `specs\u002Fbugs\u002FBUG-*.md`, run `investigate-bug` first — it handles history check, RCA (via `diagnose-root`), fix approach, and writes the bug file. Increment `bug_cycle.current_step` to 2 on completion.\n2. **Step 2 — diagnose-root:** Run 4-phase RCA (reproduce → isolate → hypothesize → verify). Record findings in the bug file. Increment to step 3.\n3. **Step 3 — develop-tdd:** `develop-tdd` against the bug file's verify steps. Increment to step 4 on all-green.\n4. **Step 4 — validate-fix:** `validate-fix` — re-run failing test, full suite, typecheck, lint. Increment to step 5.\n5. **Step 5 — release-branch:** Land the fix via `release-branch`. Clear `bug_cycle` and `active_flow` when done.\n\n## Bug file SoT\n\nOne markdown file per bug with frontmatter:\n\n```yaml\n---\nbug_id: BUG-001\nstatus: open\nseverity: high\nscope: api\ntitle: Short title\n---\n```\n\n## Verify\n\n→ verify: `test -d specs\u002Fbugs && test -f scripts\u002Frun-skill-verify.sh`\n","# Fix Bug\n\n**Boundary**: Orchestrator flow — chains `investigate-bug` (entry point + RCA via `diagnose-root`) → `develop-tdd` → `validate-fix`. Does not implement RCA or write bug files directly.\n\nOrchestrates **fix_bug** flow without mixing epic build state.\n\n> **HARD GATE** — Set `specs\u002Fstate.yaml` `active_flow: fix_bug` and `bug_cycle.current_step: 1` before starting.\n\n## Discovered gate failures (e51s04)\n\nValid entry **without a user-reported bug** when:\n\n- **Preflight** or **CI** is red at kickoff or verify-work\n- **Golden suite** or project baseline is red (`bash scripts\u002Frun-verification-gates.sh` or equivalent)\n- A reproducible gate failure during unrelated epic work exceeds quick-fix guardrails\n\nCreate `specs\u002Fbugs\u002FBUG-*.md` via `investigate-bug` (or inline in fix-bug step 1) describing the gate failure, then run the standard fix_bug chain.\n\n## Five steps (`bug_cycle` in state.yaml)\n\n| Step | Skill \u002F action |\n|------|----------------|\n| 1 | `investigate-bug` — create BUG-*.md with RCA |\n| 2 | `diagnose-root` — 4-phase root cause analysis |\n| 3 | `develop-tdd` — red-green against bug file verify steps |\n| 4 | `validate-fix` — re-run failing test, full suite, lint |\n| 5 | `release-branch` — PR or solo land the fix |\n\n### Checkpoint \u002F resume\n\nTrack progress via `specs\u002Fstate.yaml` `bug_cycle`:\n- `bug_cycle.current_step`: current step (1–5)\n- `bug_cycle.completed_steps`: completed step numbers\n- `handoff.next_skill`: skill for the current step\n- On resume, read `bug_cycle.current_step` and continue from there\n\n## Process\n\n1. **Step 1 — investigate-bug:** If no `specs\u002Fbugs\u002FBUG-*.md`, run `investigate-bug` first — it handles history check, RCA (via `diagnose-root`), fix approach, and writes the bug file. Increment `bug_cycle.current_step` to 2 on completion.\n2. **Step 2 — diagnose-root:** Run 4-phase RCA (reproduce → isolate → hypothesize → verify). Record findings in the bug file. Increment to step 3.\n3. **Step 3 — develop-tdd:** `develop-tdd` against the bug file's verify steps. Increment to step 4 on all-green.\n4. **Step 4 — validate-fix:** `validate-fix` — re-run failing test, full suite, typecheck, lint. Increment to step 5.\n5. **Step 5 — release-branch:** Land the fix via `release-branch`. Clear `bug_cycle` and `active_flow` when done.\n\n## Bug file SoT\n\nOne markdown file per bug with frontmatter:\n\n```yaml\n---\nbug_id: BUG-001\nstatus: open\nseverity: high\nscope: api\ntitle: Short title\n---\n```\n\n## Verify\n\n→ verify: `test -d specs\u002Fbugs && test -f scripts\u002Frun-skill-verify.sh`\n",{"name":5,"model":26,"description":7},"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa",".copilot\u002Fskills\u002Ffix-bug",24,"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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add danielvm-git\u002Fbigpowers --skill fix-bug",{"tool":57,"command":58},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill fix-bug",{"tool":60,"command":61},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill fix-bug","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.copilot\u002Fskills\u002Ffix-bug\u002FSKILL.md",true,[],[66,87,94,121,144,165],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":77,"publishedAt":37},"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",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[78,79,80,81,82,83,84,85,86],"fixture","open","verify","skill verify fail open fixture","skill verify","path","run","for","never",{"skillNo":88,"name":89,"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":90,"categories":91,"keywords":92,"publishedAt":37},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[93,83],"negative path",{"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":103,"publishedAt":37},"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",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000002","文档处理",[104,105,106,107,108,109,110,111,112,113,29,23,114,115,26,116,117,118,119,120],"write","write document","document","documents","actionable","technical","methodology","high","bmad","standard","minimal","bold","integrity","organize","sync","directory","guides",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":37},"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",[],[128,129,130,113,131,29,132,133,134,135,26,136,137,138,139,140,141,23,142,143],"observability","wire observability","readiness","commands","development","as","logging","add","instrumentation","at","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":145,"name":146,"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":37},"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",[],[151,152,153,154,155,156,157,158,159,160,161,113,162,85,128,26,163,164],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","with","ci pipeline setup","git","workflows",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":182,"publishedAt":37},"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",[171,174,179],{"categoryNo":172,"categoryName":173,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":175,"categoryName":176,"taxonomyType":177,"taxonomyTypeDesc":178},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":180,"categoryName":181,"taxonomyType":177,"taxonomyTypeDesc":178},"01JBSEEDCAT000000000000033","数据分析师",[183,184,185,186,187,188,189,190,191,26,192,193,194,195,196,197,198,142,199,200],"dashboard","visual","visual dashboard","status","artifacts","http","plans","planning","panel","start","release","opencode","plan","browser","api","architecture","project status","http api"]