[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2S2J31EW7092VB1ZVTZFQ":3,"skill-same:01M7B2S2J31EW7092VB1ZVTZFQ":50},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7B2S2J31EW7092VB1ZVTZFQ","orch-fix-defect",null,"Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.","lytong760-cell\u002Fcompiler_ko","lytong760-cell","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F289977458?v=4","01M7B1YD239K88PFQRD4PVC9DW","Nguyên Games","01M7B1YD2RM70TZ71QNQ0XTN4R",2,"MIT","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Forch-fix-defect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: orch-fix-defect\ndescription: Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.\nmetadata:\n  origin: ECC\n---\n\n# orch-fix-defect\n\nActor · action · target: **orch · fix · defect**. Thin wrapper over the shared\nengine in [`orch-pipeline`](..\u002Forch-pipeline\u002FSKILL.md).\n\n## When to Use\n\n- Something is **broken**: wrong output, an error, a crash, a regression.\n- Distinguish from siblings:\n  - behavior is correct but you want it different → `orch-change-feature`.\n  - the capability does not exist yet → `orch-add-feature`.\n\n## Operation settings\n\n- **Default size floor:** small (often trivial).\n- **Phase mask:** 0 → (light 2 only if root cause is non-obvious or standard+) →\n  4 → 5 → 6. Research (1) is usually skipped.\n- **First move (phase 4):** reproduce the bug as a **new failing** test\n  (regression test), then fix until it goes green. Proving the bug exists first\n  is what separates a fix from a tweak.\n\n## How It Works\n\n1. Run the `orch-pipeline` engine with the settings above.\n2. If the root cause is unclear, scope it with `code-explorer` before the red\n   test; escalate build breaks to `build-error-resolver` \u002F `\u002Fbuild-fix`.\n3. Stop at **Gate 1** (only if a plan was produced) and **Gate 2** (pre-commit).\n4. Add `security-reviewer` if the defect sits in a security-sensitive path.\n\n## Example\n\n```\norch-fix-defect: poller crashes on empty NWS response\n→ write failing test reproducing the crash → fix to green\n→ code-review → commit  [GATE 2: confirm]   (commit: fix:)\n```\n","# orch-fix-defect\n\nActor · action · target: **orch · fix · defect**. Thin wrapper over the shared\nengine in [`orch-pipeline`](..\u002Forch-pipeline\u002FSKILL.md).\n\n## When to Use\n\n- Something is **broken**: wrong output, an error, a crash, a regression.\n- Distinguish from siblings:\n  - behavior is correct but you want it different → `orch-change-feature`.\n  - the capability does not exist yet → `orch-add-feature`.\n\n## Operation settings\n\n- **Default size floor:** small (often trivial).\n- **Phase mask:** 0 → (light 2 only if root cause is non-obvious or standard+) →\n  4 → 5 → 6. Research (1) is usually skipped.\n- **First move (phase 4):** reproduce the bug as a **new failing** test\n  (regression test), then fix until it goes green. Proving the bug exists first\n  is what separates a fix from a tweak.\n\n## How It Works\n\n1. Run the `orch-pipeline` engine with the settings above.\n2. If the root cause is unclear, scope it with `code-explorer` before the red\n   test; escalate build breaks to `build-error-resolver` \u002F `\u002Fbuild-fix`.\n3. Stop at **Gate 1** (only if a plan was produced) and **Gate 2** (pre-commit).\n4. Add `security-reviewer` if the defect sits in a security-sensitive path.\n\n## Example\n\n```\norch-fix-defect: poller crashes on empty NWS response\n→ write failing test reproducing the crash → fix to green\n→ code-review → commit  [GATE 2: confirm]   (commit: fix:)\n```\n",{"name":5,"metadata":24,"description":7},{"origin":25},"ECC","main","c32dc0b68600587f78aff3310f3bbd4212173ab3",".kilo\u002Fskills\u002Forch-fix-defect",1,"https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko","https:\u002F\u002Fko-lang.ai.studio","https:\u002F\u002Fgithub.com\u002Flytong760-cell","hanaminikata.com","hello ","2026-11-05 18:26:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add lytong760-cell\u002Fcompiler_ko --skill orch-fix-defect",{"tool":42,"command":43},"bunx","bunx skills add lytong760-cell\u002Fcompiler_ko --skill orch-fix-defect",{"tool":45,"command":46},"pnpm","pnpm dlx skills add lytong760-cell\u002Fcompiler_ko --skill orch-fix-defect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Forch-fix-defect\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7B36K22Z7155PTGEGTSDNJ4","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fx-api\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7B36HCAE9ESGBVS6J0FR52F","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7B36DYH4ZFJ3GZHPAEMVQAY","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fworkspace-surface-audit\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7B36A1QXMEZT8VZMFVQNR5E","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7B364EK3N88VQQJ6HFATJQE","windows-desktop-e2e","E2E testing for Windows native desktop apps (WPF, WinForms, Win32\u002FMFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwindows-desktop-e2e\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"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":19},"01M7B360YF7GGNAF21KT4QB5PG","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]