[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JATG7SNDHT1QHT8QCWWS3":3,"skill-same:01M71JATG7SNDHT1QHT8QCWWS3":67},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M71JATG7SNDHT1QHT8QCWWS3","quick-fix",null,"Streamlined fast-path for trivial data-only fixes — no TDD, no branching ceremony. Collapses 6 skills into 2 for changes that are purely data with no logic risk. Aborts with fallback to investigate-bug if guardrails trigger.","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.opencode\u002Fskills\u002Fquick-fix\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"fix","quick fix","quick","tdd","logic","changes","investigate","with","trigger","for","fixes","risk","path","fallback","sonnet","branching","data","bug","only","Guardrails","2026-11-10 10:12:30",false,"---\nname: quick-fix\nmodel: sonnet\ndescription: \"Streamlined fast-path for trivial data-only fixes — no TDD, no branching ceremony. Collapses 6 skills into 2 for changes that are purely data with no logic risk. Aborts with fallback to investigate-bug if guardrails trigger.\"\n---\n\n# Quick Fix\n\n> **HARD GATE** — ALL entry criteria must pass before invoking quick-fix. If any guardrail triggers during execution, abort immediately and fall back to `investigate-bug`. Do NOT use quick-fix for logic changes, multi-file edits, or diffs > 5 lines.\n\nFast-track for trivial data-only fixes that do not require the full bug-fix chain.\n\nWhen a bug fix is purely data — an add-missing-key, a typo correction, a config value update — the standard 6-skill chain (investigate-bug → diagnose-root → develop-tdd → kickoff-branch → verify-work → release-branch) is wasteful overhead. Quick-fix collapses it to 2 skills: **quick-fix** then **release-branch**.\n\n## Discovered gate failures (e51s04)\n\nA **Preflight**, **golden suite**, or **baseline red** failure discovered during unrelated work is valid quick-fix entry when the root cause is a data-only gap (missing key, typo, stale config) — **no user-reported bug required**. If guardrails abort (logic change, >1 file, >5 lines), fall back to `fix-bug` instead of narrating and continuing.\n\n## Entry Criteria (ALL must be true)\n\nBefore invoking quick-fix, evaluate every item in this checklist:\n\n1. **Purely data change** — adding a missing key, fixing a typo, updating a config value, correcting a constant\n2. **No logic change** — no function signature, condition, loop, or control flow is modified\n3. **No refactor risk** — the change does not reorganize or rename existing structures\n4. **No API surface change** — no exported symbol, interface, or contract changes\n5. **Verifiable with a single assertion** — one test, one curl, one grep can prove it works\n6. **Affects ≤ 1 file**\n7. **Affects ≤ 5 lines changed**\n\n## Guardrails (HARD ABORT — all must pass)\n\nIf ANY guardrail triggers, **abort immediately** and suggest `investigate-bug` instead:\n\n| Guardrail | Check |\n|-----------|-------|\n| **>1 file** | The fix touches more than one file |\n| **>5 lines** | The diff exceeds 5 lines |\n| **Logic change** | Any function signature, condition, or loop is modified |\n| **Complex verify** | The verify command is more than one pipeline |\n| **Test breakage** | Running `npm test` or equivalent breaks any existing test |\n\n> **Fallback:** If any guardrail triggers, tell the user: *\"This fix exceeds quick-fix guardrails. Use `investigate-bug` for the full TDD bug-fix chain instead.\"*\n\n## Fast-Path Workflow\n\nOnly 2 skills needed for eligible fixes:\n\n```\nquick-fix  →  apply change, run one-line verify, commit with fix:\nrelease-branch  →  merge and ship (existing skill)\n```\n\n**Skipped skills (with justification):**\n\n| Skipped skill | Why skipped |\n|---------------|-------------|\n| `investigate-bug` | Root cause is obvious (data gap, not logic error) |\n| `diagnose-root` | No isolation needed — the data point is the root cause |\n| `develop-tdd` | No logic to test — single assertion proves correctness |\n| `kickoff-branch` | Change is so small it does not warrant a separate worktree |\n\n> Justification is included in the `fix:` commit body so the audit trail is preserved.\n\n## Process\n\n### 1. Evaluate entry criteria\n\nRun the entry criteria checklist above. If any criterion fails → abort, suggest `investigate-bug`.\n\n### 2. Apply the fix\n\nMake the data change — add the missing key, fix the typo, update the value. Keep it to ≤5 lines in 1 file.\n\n### 3. Verify\n\nRun the single-assertion verify command. Example:\n\n```bash\ngrep -q \"Bosnia\" src\u002Fflags.js && echo \"FIX VERIFIED\" || echo \"FIX FAILED\"\n```\n\n### 4. Commit\n\n```bash\ngit add \u003Cfile>\ngit commit -m \"fix(\u003Cscope>): \u003Cdescription>\"\ngit commit --amend -m \"fix(\u003Cscope>): \u003Cdescription>\n\nSkipped skills (justified for data-only change):\n- investigate-bug: root cause is a data gap, not a logic error\n- diagnose-root: the missing data point is the root cause\n- develop-tdd: single assertion proves correctness\n- kickoff-branch: change is too small for a separate worktree\"\n```\n\n### 5. Release\n\nInvoke `release-branch` to merge and ship.\n\n\n## Example\n\n### Bosnia flag missing from FLAGS dictionary\n\n```gherkin\nGiven a bug where FLAGS dictionary is missing entry \"Bosnia\"\nAnd no logic depends on the missing entry (purely a data gap)\nWhen the agent invokes quick-fix\nThen the missing entry is added to the dictionary\nAnd a one-line verify confirms the key exists: grep -q \"Bosnia\" src\u002Fflags.js\nAnd a fix: commit is created with the skipped-skills rationale in the body\nAnd the change is ready for release-branch\n```\n","# Quick Fix\n\n> **HARD GATE** — ALL entry criteria must pass before invoking quick-fix. If any guardrail triggers during execution, abort immediately and fall back to `investigate-bug`. Do NOT use quick-fix for logic changes, multi-file edits, or diffs > 5 lines.\n\nFast-track for trivial data-only fixes that do not require the full bug-fix chain.\n\nWhen a bug fix is purely data — an add-missing-key, a typo correction, a config value update — the standard 6-skill chain (investigate-bug → diagnose-root → develop-tdd → kickoff-branch → verify-work → release-branch) is wasteful overhead. Quick-fix collapses it to 2 skills: **quick-fix** then **release-branch**.\n\n## Discovered gate failures (e51s04)\n\nA **Preflight**, **golden suite**, or **baseline red** failure discovered during unrelated work is valid quick-fix entry when the root cause is a data-only gap (missing key, typo, stale config) — **no user-reported bug required**. If guardrails abort (logic change, >1 file, >5 lines), fall back to `fix-bug` instead of narrating and continuing.\n\n## Entry Criteria (ALL must be true)\n\nBefore invoking quick-fix, evaluate every item in this checklist:\n\n1. **Purely data change** — adding a missing key, fixing a typo, updating a config value, correcting a constant\n2. **No logic change** — no function signature, condition, loop, or control flow is modified\n3. **No refactor risk** — the change does not reorganize or rename existing structures\n4. **No API surface change** — no exported symbol, interface, or contract changes\n5. **Verifiable with a single assertion** — one test, one curl, one grep can prove it works\n6. **Affects ≤ 1 file**\n7. **Affects ≤ 5 lines changed**\n\n## Guardrails (HARD ABORT — all must pass)\n\nIf ANY guardrail triggers, **abort immediately** and suggest `investigate-bug` instead:\n\n| Guardrail | Check |\n|-----------|-------|\n| **>1 file** | The fix touches more than one file |\n| **>5 lines** | The diff exceeds 5 lines |\n| **Logic change** | Any function signature, condition, or loop is modified |\n| **Complex verify** | The verify command is more than one pipeline |\n| **Test breakage** | Running `npm test` or equivalent breaks any existing test |\n\n> **Fallback:** If any guardrail triggers, tell the user: *\"This fix exceeds quick-fix guardrails. Use `investigate-bug` for the full TDD bug-fix chain instead.\"*\n\n## Fast-Path Workflow\n\nOnly 2 skills needed for eligible fixes:\n\n```\nquick-fix  →  apply change, run one-line verify, commit with fix:\nrelease-branch  →  merge and ship (existing skill)\n```\n\n**Skipped skills (with justification):**\n\n| Skipped skill | Why skipped |\n|---------------|-------------|\n| `investigate-bug` | Root cause is obvious (data gap, not logic error) |\n| `diagnose-root` | No isolation needed — the data point is the root cause |\n| `develop-tdd` | No logic to test — single assertion proves correctness |\n| `kickoff-branch` | Change is so small it does not warrant a separate worktree |\n\n> Justification is included in the `fix:` commit body so the audit trail is preserved.\n\n## Process\n\n### 1. Evaluate entry criteria\n\nRun the entry criteria checklist above. If any criterion fails → abort, suggest `investigate-bug`.\n\n### 2. Apply the fix\n\nMake the data change — add the missing key, fix the typo, update the value. Keep it to ≤5 lines in 1 file.\n\n### 3. Verify\n\nRun the single-assertion verify command. Example:\n\n```bash\ngrep -q \"Bosnia\" src\u002Fflags.js && echo \"FIX VERIFIED\" || echo \"FIX FAILED\"\n```\n\n### 4. Commit\n\n```bash\ngit add \u003Cfile>\ngit commit -m \"fix(\u003Cscope>): \u003Cdescription>\"\ngit commit --amend -m \"fix(\u003Cscope>): \u003Cdescription>\n\nSkipped skills (justified for data-only change):\n- investigate-bug: root cause is a data gap, not a logic error\n- diagnose-root: the missing data point is the root cause\n- develop-tdd: single assertion proves correctness\n- kickoff-branch: change is too small for a separate worktree\"\n```\n\n### 5. Release\n\nInvoke `release-branch` to merge and ship.\n\n\n## Example\n\n### Bosnia flag missing from FLAGS dictionary\n\n```gherkin\nGiven a bug where FLAGS dictionary is missing entry \"Bosnia\"\nAnd no logic depends on the missing entry (purely a data gap)\nWhen the agent invokes quick-fix\nThen the missing entry is added to the dictionary\nAnd a one-line verify confirms the key exists: grep -q \"Bosnia\" src\u002Fflags.js\nAnd a fix: commit is created with the skipped-skills rationale in the body\nAnd the change is ready for release-branch\n```\n",{"name":5,"model":33,"description":7},"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa",".opencode\u002Fskills\u002Fquick-fix",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":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add danielvm-git\u002Fbigpowers --skill quick-fix",{"tool":59,"command":60},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill quick-fix",{"tool":62,"command":63},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill quick-fix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fquick-fix\u002FSKILL.md",true,[],[68,87,94,123,146,166],{"skillNo":69,"name":70,"nameZh":6,"description":71,"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":39},"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",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[80,81,82,83,84,31,85,28,86],"fixture","open","verify","skill verify fail open fixture","skill verify","run","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":39},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[93,31],"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":39},"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":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000002","文档处理",[104,105,106,107,108,109,110,111,112,113,114,115,116,117,33,118,119,120,121,122],"write","write document","document","documents","actionable","technical","methodology","high","bmad","standard","use","when","minimal","bold","integrity","organize","sync","directory","guides",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":39},"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",[],[130,131,132,113,133,114,134,135,136,137,33,138,139,140,141,142,143,115,144,145],"observability","wire observability","readiness","commands","development","as","logging","add","instrumentation","at","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":39},"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",[],[153,154,155,156,157,158,159,160,161,162,26,113,163,28,130,33,164,165],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","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":39},"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":77,"taxonomyTypeDesc":78},"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,33,193,194,195,196,197,198,199,144,200,201],"dashboard","visual","visual dashboard","status","artifacts","http","plans","planning","panel","start","release","opencode","plan","browser","api","architecture","project status","http api"]