[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73FF3911F58BTHKFE9NKGJB":3,"skill-same:01M73FF3911F58BTHKFE9NKGJB":48},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M73FF3911F58BTHKFE9NKGJB","remove-dead-code",null,"Safely identifies and removes dead code in TypeScript\u002FJavaScript projects using multi-agent analysis with automatic backup branches. Use when cleaning up unused exports, orphaned files, dead imports, unreachable functions, or unused dependencies.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fremove-dead-code\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: remove-dead-code\ndescription: Safely identifies and removes dead code in TypeScript\u002FJavaScript projects using multi-agent analysis with automatic backup branches. Use when cleaning up unused exports, orphaned files, dead imports, unreachable functions, or unused dependencies.\n---\n\n\u003Cessential_principles>\n\n**Safety-first dead code removal.** Every removal is protected by an automatic backup branch. Multi-agent analysis reduces false positives. No code is deleted without cross-validation.\n\n**1. Backup Before Everything**\n\nBefore any modification, create a timestamped backup branch from the current HEAD. This is non-negotiable. The branch name format is `backup\u002Fdead-code-removal\u002F{timestamp}`.\n\n**2. Parallel Scout + Validator Pattern**\n\nMultiple scout agents analyze different aspects of dead code in parallel. A validator agent then cross-checks all findings against the full codebase before anything is flagged for removal. Only code confirmed dead by both scouts AND validator gets removed.\n\n**3. Conservative by Default**\n\nWhen in doubt, keep the code. False negatives (missing some dead code) are acceptable. False positives (removing live code) are not. Dynamic imports, reflection, test utilities, and public API surface are always treated as potentially live.\n\n**4. Never Remove Without Reporting First**\n\nThe scan workflow produces a report. The user reviews the report. Only then does the remove workflow execute against confirmed items.\n\n\u003C\u002Fessential_principles>\n\n\u003Cintake>\nWhat would you like to do?\n\n1. **Scan** - Analyze codebase for dead code (read-only, produces report)\n2. **Remove** - Remove confirmed dead code (requires prior scan report)\n3. **Validate** - Verify removal didn't break anything (post-removal checks)\n\n**Wait for response before proceeding.**\n\u003C\u002Fintake>\n\n\u003Crouting>\n| Response | Workflow |\n|----------|----------|\n| 1, \"scan\", \"analyze\", \"find\", \"detect\", \"report\" | `workflows\u002Fscan-dead-code.md` |\n| 2, \"remove\", \"delete\", \"clean\", \"prune\" | `workflows\u002Fremove-dead-code.md` |\n| 3, \"validate\", \"verify\", \"check\", \"test\" | `workflows\u002Fvalidate-removal.md` |\n| Unclear | Ask: \"Would you like to scan first (recommended) or do you already have a scan report?\" |\n\n**Default flow:** Scan → Review report → Remove → Validate\n\n**After reading the workflow, follow it exactly.**\n\u003C\u002Frouting>\n\n\u003Csafety_rules>\n- NEVER remove code without creating a backup branch first\n- NEVER remove code that appears in test files as a test subject (test helpers ARE candidates)\n- NEVER remove re-exported types that could be part of a public API\n- NEVER remove files matching patterns: `*.config.*`, `*.setup.*`, `*.d.ts`, entry points\n- ALWAYS preserve code referenced by dynamic imports (`import()` expressions)\n- ALWAYS preserve code that might be used via string-based lookups or reflection\n- ALWAYS check `package.json` `exports`, `main`, `types`, and `bin` fields before removing\n- ALWAYS check framework conventions (Next.js pages\u002Froutes, Convex functions, etc.)\n\u003C\u002Fsafety_rules>\n\n\u003Creference_index>\nAll domain knowledge in `references\u002F`:\n\n**Detection:** detection-patterns.md - What to scan for and how to identify dead code\n**Agents:** agent-coordination.md - How multi-agent parallel analysis works\n\u003C\u002Freference_index>\n\n\u003Cworkflows_index>\n| Workflow | Purpose |\n|----------|---------|\n| scan-dead-code.md | Multi-agent analysis producing a dead code report |\n| remove-dead-code.md | Safe removal with backup branch and atomic commits |\n| validate-removal.md | Post-removal build, test, and type-check verification |\n\u003C\u002Fworkflows_index>\n\n\u003Csuccess_criteria>\nDead code removal is successful when:\n- Backup branch exists with pre-removal state\n- All flagged items were cross-validated by multiple agents\n- Build passes after removal (`tsc --noEmit`, `npm run build`)\n- All tests pass after removal\n- No new TypeScript errors introduced\n- Removal summary report generated with what was removed and why\n\u003C\u002Fsuccess_criteria>\n","\u003Cessential_principles>\n\n**Safety-first dead code removal.** Every removal is protected by an automatic backup branch. Multi-agent analysis reduces false positives. No code is deleted without cross-validation.\n\n**1. Backup Before Everything**\n\nBefore any modification, create a timestamped backup branch from the current HEAD. This is non-negotiable. The branch name format is `backup\u002Fdead-code-removal\u002F{timestamp}`.\n\n**2. Parallel Scout + Validator Pattern**\n\nMultiple scout agents analyze different aspects of dead code in parallel. A validator agent then cross-checks all findings against the full codebase before anything is flagged for removal. Only code confirmed dead by both scouts AND validator gets removed.\n\n**3. Conservative by Default**\n\nWhen in doubt, keep the code. False negatives (missing some dead code) are acceptable. False positives (removing live code) are not. Dynamic imports, reflection, test utilities, and public API surface are always treated as potentially live.\n\n**4. Never Remove Without Reporting First**\n\nThe scan workflow produces a report. The user reviews the report. Only then does the remove workflow execute against confirmed items.\n\n\u003C\u002Fessential_principles>\n\n\u003Cintake>\nWhat would you like to do?\n\n1. **Scan** - Analyze codebase for dead code (read-only, produces report)\n2. **Remove** - Remove confirmed dead code (requires prior scan report)\n3. **Validate** - Verify removal didn't break anything (post-removal checks)\n\n**Wait for response before proceeding.**\n\u003C\u002Fintake>\n\n\u003Crouting>\n| Response | Workflow |\n|----------|----------|\n| 1, \"scan\", \"analyze\", \"find\", \"detect\", \"report\" | `workflows\u002Fscan-dead-code.md` |\n| 2, \"remove\", \"delete\", \"clean\", \"prune\" | `workflows\u002Fremove-dead-code.md` |\n| 3, \"validate\", \"verify\", \"check\", \"test\" | `workflows\u002Fvalidate-removal.md` |\n| Unclear | Ask: \"Would you like to scan first (recommended) or do you already have a scan report?\" |\n\n**Default flow:** Scan → Review report → Remove → Validate\n\n**After reading the workflow, follow it exactly.**\n\u003C\u002Frouting>\n\n\u003Csafety_rules>\n- NEVER remove code without creating a backup branch first\n- NEVER remove code that appears in test files as a test subject (test helpers ARE candidates)\n- NEVER remove re-exported types that could be part of a public API\n- NEVER remove files matching patterns: `*.config.*`, `*.setup.*`, `*.d.ts`, entry points\n- ALWAYS preserve code referenced by dynamic imports (`import()` expressions)\n- ALWAYS preserve code that might be used via string-based lookups or reflection\n- ALWAYS check `package.json` `exports`, `main`, `types`, and `bin` fields before removing\n- ALWAYS check framework conventions (Next.js pages\u002Froutes, Convex functions, etc.)\n\u003C\u002Fsafety_rules>\n\n\u003Creference_index>\nAll domain knowledge in `references\u002F`:\n\n**Detection:** detection-patterns.md - What to scan for and how to identify dead code\n**Agents:** agent-coordination.md - How multi-agent parallel analysis works\n\u003C\u002Freference_index>\n\n\u003Cworkflows_index>\n| Workflow | Purpose |\n|----------|---------|\n| scan-dead-code.md | Multi-agent analysis producing a dead code report |\n| remove-dead-code.md | Safe removal with backup branch and atomic commits |\n| validate-removal.md | Post-removal build, test, and type-check verification |\n\u003C\u002Fworkflows_index>\n\n\u003Csuccess_criteria>\nDead code removal is successful when:\n- Backup branch exists with pre-removal state\n- All flagged items were cross-validated by multiple agents\n- Build passes after removal (`tsc --noEmit`, `npm run build`)\n- All tests pass after removal\n- No new TypeScript errors introduced\n- Removal summary report generated with what was removed and why\n\u003C\u002Fsuccess_criteria>\n",{"name":5,"description":7},"main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fremove-dead-code",1,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-11 23:56:26",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill remove-dead-code",{"tool":40,"command":41},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill remove-dead-code",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill remove-dead-code","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fremove-dead-code\u002FSKILL.md",true,[],[49,57,64,72,80,88],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\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":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"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":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]