[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71J1GGZNVMF6VT5MZACXERP":3,"skill-same:01M71J1GGZNVMF6VT5MZACXERP":66},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":65},"01M71J1GGZNVMF6VT5MZACXERP","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",290,"MIT","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.gemini\u002Fextensions\u002Fbigpowers\u002Fskills\u002Ffix-bug\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"fix bug","fix","bug","orchestrator","when","defect","bugs","true","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.\"\ndisable-model-invocation: true\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":27,"description":7,"disable-model-invocation":43},true,"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa",".gemini\u002Fextensions\u002Fbigpowers\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":54,"prompt":64,"zipAvailable":43},[55,58,61],{"tool":56,"command":57},"npx","npx skills add danielvm-git\u002Fbigpowers --skill fix-bug",{"tool":59,"command":60},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill fix-bug",{"tool":62,"command":63},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill fix-bug","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.gemini\u002Fextensions\u002Fbigpowers\u002Fskills\u002Ffix-bug\u002FSKILL.md",[],[67,88,95,122,145,166],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":78,"publishedAt":38},"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",[73],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[79,80,81,82,83,84,85,86,87],"fixture","open","verify","skill verify fail open fixture","skill verify","path","run","for","never",{"skillNo":89,"name":90,"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":91,"categories":92,"keywords":93,"publishedAt":38},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[94,84],"negative path",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":104,"publishedAt":38},"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",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000002","文档处理",[105,106,107,108,109,110,111,112,113,114,30,23,115,116,27,117,118,119,120,121],"write","write document","document","documents","actionable","technical","methodology","high","bmad","standard","minimal","bold","integrity","organize","sync","directory","guides",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":38},"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",[],[129,130,131,114,132,30,133,134,135,136,27,137,138,139,140,141,142,23,143,144],"observability","wire observability","readiness","commands","development","as","logging","add","instrumentation","at","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":38},"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",[],[152,153,154,155,156,157,158,159,160,161,162,114,163,86,129,27,164,165],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","with","ci pipeline setup","git","workflows",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":183,"publishedAt":38},"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",[172,175,180],{"categoryNo":173,"categoryName":174,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":176,"categoryName":177,"taxonomyType":178,"taxonomyTypeDesc":179},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":181,"categoryName":182,"taxonomyType":178,"taxonomyTypeDesc":179},"01JBSEEDCAT000000000000033","数据分析师",[184,185,186,187,188,189,190,191,192,27,193,194,195,196,197,198,199,143,200,201],"dashboard","visual","visual dashboard","status","artifacts","http","plans","planning","panel","start","release","opencode","plan","browser","api","architecture","project status","http api"]