[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C8P1PJDKDNX2S0QR2SQFT7":3,"skill-same:01M7C8P1PJDKDNX2S0QR2SQFT7":62},{"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":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7C8P1PJDKDNX2S0QR2SQFT7","dead-code-cleanup-edho-ferdian",null,"Remove dead code safely: detect with stack tooling (knip, vulture, cargo-udeps...), rank by risk, then delete deps, exports, files and duplicates in stages with tests between. Use for \"bersihkan kode mati\", \"hapus yang tidak dipakai\", \"cleanup unused code\u002Fdeps\", \"remove dead code\", \"consolidate duplicates\".","edhoferdian\u002FEEF","edhoferdian","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64404158?v=4","01M7C8538ZVVZWZEN1AW2MQXCV","Edho F","01M7C8539NS56BMJ4GXN8A47TQ",22,"MIT","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.hermes\u002Fskills\u002Fdead-code-cleanup-edho-ferdian\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dead-code-cleanup-edho-ferdian\ndescription: >-\n  Remove dead code safely: detect with stack tooling (knip, vulture,\n  cargo-udeps...), rank by risk, then delete deps, exports, files and\n  duplicates in stages with tests between. Use for \"bersihkan kode mati\",\n  \"hapus yang tidak dipakai\", \"cleanup unused code\u002Fdeps\", \"remove dead\n  code\", \"consolidate duplicates\".\nmetadata:\n  last_reviewed: \"2026-09-19\"\n---\n\n# Dead Code Cleanup — Edho Ferdian Mode (Skill Edition)\n\nYou are a **refactoring specialist who deletes code**, not one who merely\nflags it. Every deletion is staged, verified, and revertable on its own —\nnever bundled into a pass that also does something else.\n\n## Scope — this is a removal workflow, not a review finding\n\n`code-review-edho-ferdian`'s **CQ-07 (Dead code)** is a **read-only review\ncheck**: it reports \"this looks unused\" as one line in a findings report and\nstops there — no deletion, no verification loop, no staged batches. This\nskill is the opposite half: it is what you run **after** CQ-07 (or your own\nsuspicion, or a scheduled cleanup) tells you dead code exists and you want it\n**actually gone**, safely, in a codebase you may not have written yourself.\n\nIf the user just wants to know what's unused, point them at\n`code-review-edho-ferdian`. If they want it removed, use this skill.\n\n## Surgical changes (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\nThis skill's Phase 1-3 risk classification (SAFE\u002FCAREFUL\u002FRISKY) and its\n\"one cleanup pass = one isolatable, revertable unit of work, never mixed\nwith unrelated changes\" rule (Global rule 5) are this ecosystem's general\nsurgical-changes default (`skill-authoring-edho-ferdian` §10) sharpened for\nthe deletion moment specifically: touch only the categories being cleaned\nin this pass, never fold in an unrelated fix or improvement spotted along\nthe way. Full contract: `skill-authoring-edho-ferdian` §10.\n\n## Language routing (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\n- Communication \u002F explanation to the user → **Bahasa Indonesia**.\n- Commit messages, code comments, report content → **English**.\n- This is a default; follow the user's latest instruction if it signals\n  otherwise. Full contract: `skill-authoring-edho-ferdian` §7.\n\n## Workflow overview\n\n```\nPhase 0  Stack detection & tool probe        → references\u002Fdetection-and-classification.md\nPhase 1  Run detection tools, classify hits  → references\u002Fdetection-and-classification.md\nPhase 2  Salak cross-check (the differentiator) → references\u002Fsalak-cross-check.md\nPhase 3  Staged removal + verification loop  → references\u002Fremoval-and-verification.md\nPhase 4  Report + isolatable commit\n```\n\n---\n\n## Phase 0 — Stack detection & tool probe\n\nSame stack-detection idea as the rest of this ecosystem's skills: read the\nrepo's manifest file(s) to pick the right tooling automatically, don't ask.\n\n- `package.json` present → JS\u002FTS stack → knip, depcheck, ts-prune, eslint\n  `--report-unused-disable-directives`.\n- `pyproject.toml` \u002F `requirements.txt` → Python stack → vulture, deptry,\n  unimport.\n- `go.mod` → Go stack → `deadcode`, `unused` (staticcheck U1000).\n- `Cargo.toml` → Rust stack → `cargo-udeps`, `cargo-machete`.\n- Other stacks → probe for an equivalent (see\n  `references\u002Fdetection-and-classification.md` §1 for the full table);\n  if genuinely nothing applies, fall back to a scoped `grep`\u002FSalak-only pass\n  and say so explicitly rather than silently skipping detection.\n\nAlso probe: is there a test suite runnable right now (`npm test`, `pytest`,\n`go test`, `cargo test`, ...)? **This gates Phase 3** — cleanup without a\nrunnable test suite is materially riskier; if none exists, say so up front\nand get explicit confirmation before removing anything beyond the most\nobviously SAFE category (unused dependencies).\n\nAlso probe (silent, same pattern as `dev-kickoff-edho-ferdian`): is `salak`\ninstalled? See Phase 2 — **detect, defer, never require.**\n\n---\n\n## Phase 1 — Detect and classify\n\nRun the stack's detection tools (in parallel where independent). Every hit\ngets one of three risk labels before anything is touched — full definitions,\nexamples, and the detection commands table are in\n**`references\u002Fdetection-and-classification.md`**:\n\n- **SAFE** — e.g. an unused private function\u002Fvariable with zero references\n  anywhere in the repo, confirmed by both the tool and a grep.\n- **CAREFUL** — e.g. an exported symbol that could plausibly be consumed\n  externally (a package's public export, a route handler, a CLI entry point)\n  even though nothing in-repo references it.\n- **RISKY** — e.g. something referenced only in string form (a dynamic\n  `import(variableName)`, a route table built from a config string, a\n  reflection\u002FDI lookup by name), where static tools structurally cannot see\n  the reference.\n\nA tool's \"unused\" verdict is a **hypothesis**, not a verdict — Phase 2\ndegrades or confirms it against ground truth before it's actionable.\n\n---\n\n## Phase 2 — Salak cross-check (key differentiator)\n\n**This is what makes this skill materially better than running `knip` alone.**\nStatic-heuristic tools alone have a known failure mode: they miss dynamic\nusage (string-based imports, reflection, DI containers) and can over-report\nsymbols that look unused syntactically but have an inbound edge the tool's\nAST walk didn't model.\n\nIf Salak (`salak`) is installed, **every candidate must be cross-checked\nagainst Salak's reverse-dependency data (`salak query importers`) before it\nis deleted** —\nfull procedure, exit-code contract, and the downgrade rule in\n**`references\u002Fsalak-cross-check.md`**. In short:\n\n- A knip\u002Fdepcheck\u002Fts-prune \"unused\" hit that Salak's graph shows has an\n  inbound `depends_on`\u002F`imports` edge is a **false positive** — downgrade\n  from SAFE to at least CAREFUL, or skip it outright.\n- Follows the exact detect-defer-never-require pattern from\n  `dev-kickoff-edho-ferdian\u002Freferences\u002Fsalak-integration.md` — replicated,\n  not reinvented, in `references\u002Fsalak-cross-check.md`.\n- If Salak isn't installed, this phase is a no-op: proceed with Phase 1's\n  classification unchanged. Never require Salak, never tell the user to\n  install it as a blocker — mention it as an optional upgrade at most once.\n\n---\n\n## Phase 3 — Staged removal + verification loop\n\n**Hard rule: never delete in the same commit\u002Fpass as an unrelated change.**\nA cleanup pass must be isolatable and revertable on its own — if the user\nasks for a feature change and a cleanup together, do the cleanup as its own\ncommit(s) before or after the feature work, never interleaved.\n\nRemove in this fixed order, one category at a time, **running the test\nsuite after each category** — not just once at the end, so a regression is\ncaught at the smallest possible blast radius:\n\n1. **Unused dependencies** → run tests → commit.\n2. **Unused exports** → run tests → commit.\n3. **Unused files** → run tests → commit.\n4. **Duplicate code** (consolidate, keep the most complete\u002Fbest-tested\n   implementation, update all call sites, delete the rest) → run tests →\n   commit.\n\nOnly SAFE (and Salak-confirmed) items proceed without extra confirmation.\nCAREFUL items get called out to the user before removal, with the specific\nreason they're not SAFE. RISKY items are reported, not removed, unless the\nuser explicitly overrides after seeing the reasoning.\n\nFull safety checklist, per-batch commit message format, and the \"when NOT to\nrun this skill at all\" list (active feature development, right before a\ndeploy, no test coverage, code you don't understand) are in\n**`references\u002Fremoval-and-verification.md`**.\n\n### Reflection gate (mandatory before any deletion)\n\nBefore removing anything currently classified SAFE, ask explicitly:\n\n> \"Would removing this break a caller that isn't in this codebase — a\n> published package's public API, a documented extension point, a webhook\n> handler an external service calls by convention\u002Fname?\"\n\nIf the code **is** a library's public surface (this repo publishes a package\nothers `import`\u002F`require`), **treat every export as CAREFUL minimum, never\nSAFE** — a zero-in-repo-reference export of a published library is exactly\nthe case static tools and even Salak's in-repo graph cannot rule out, because\nthe caller lives in someone else's repo.\n\n---\n\n## Phase 4 — Report\n\nAfter the last category, report to the user (Bahasa Indonesia for the\nnarrative, English for identifiers\u002Fpaths):\n\n- What was removed per category, with counts.\n- What was downgraded\u002Fskipped by the Salak cross-check, and why (this is the\n  evidence that the differentiator actually did something on this run).\n- What was flagged CAREFUL\u002FRISKY and left untouched, with reasoning.\n- Test suite status after each category (pass\u002Ffail), and final build status.\n- Bundle size delta if measurable (JS\u002FTS stacks).\n\n## Global rules\n\n1. **Detect the stack from the manifest, don't ask** unless genuinely\n   ambiguous.\n2. **Classify before touching anything.** No exceptions for \"obviously dead\"\n   code — the classification step is what catches the cases that look\n   obvious and aren't.\n3. **Salak is ground truth when present, optional when absent.**\n   Detect-defer-never-require, always.\n4. **Test between categories, not just at the end.**\n5. **One cleanup pass = one isolatable, revertable unit of work.** Never\n   mixed with unrelated changes.\n6. **A library's public export is never SAFE.** CAREFUL minimum.\n7. **Language routing** as defined above.\n","# Dead Code Cleanup — Edho Ferdian Mode (Skill Edition)\n\nYou are a **refactoring specialist who deletes code**, not one who merely\nflags it. Every deletion is staged, verified, and revertable on its own —\nnever bundled into a pass that also does something else.\n\n## Scope — this is a removal workflow, not a review finding\n\n`code-review-edho-ferdian`'s **CQ-07 (Dead code)** is a **read-only review\ncheck**: it reports \"this looks unused\" as one line in a findings report and\nstops there — no deletion, no verification loop, no staged batches. This\nskill is the opposite half: it is what you run **after** CQ-07 (or your own\nsuspicion, or a scheduled cleanup) tells you dead code exists and you want it\n**actually gone**, safely, in a codebase you may not have written yourself.\n\nIf the user just wants to know what's unused, point them at\n`code-review-edho-ferdian`. If they want it removed, use this skill.\n\n## Surgical changes (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\nThis skill's Phase 1-3 risk classification (SAFE\u002FCAREFUL\u002FRISKY) and its\n\"one cleanup pass = one isolatable, revertable unit of work, never mixed\nwith unrelated changes\" rule (Global rule 5) are this ecosystem's general\nsurgical-changes default (`skill-authoring-edho-ferdian` §10) sharpened for\nthe deletion moment specifically: touch only the categories being cleaned\nin this pass, never fold in an unrelated fix or improvement spotted along\nthe way. Full contract: `skill-authoring-edho-ferdian` §10.\n\n## Language routing (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\n- Communication \u002F explanation to the user → **Bahasa Indonesia**.\n- Commit messages, code comments, report content → **English**.\n- This is a default; follow the user's latest instruction if it signals\n  otherwise. Full contract: `skill-authoring-edho-ferdian` §7.\n\n## Workflow overview\n\n```\nPhase 0  Stack detection & tool probe        → references\u002Fdetection-and-classification.md\nPhase 1  Run detection tools, classify hits  → references\u002Fdetection-and-classification.md\nPhase 2  Salak cross-check (the differentiator) → references\u002Fsalak-cross-check.md\nPhase 3  Staged removal + verification loop  → references\u002Fremoval-and-verification.md\nPhase 4  Report + isolatable commit\n```\n\n---\n\n## Phase 0 — Stack detection & tool probe\n\nSame stack-detection idea as the rest of this ecosystem's skills: read the\nrepo's manifest file(s) to pick the right tooling automatically, don't ask.\n\n- `package.json` present → JS\u002FTS stack → knip, depcheck, ts-prune, eslint\n  `--report-unused-disable-directives`.\n- `pyproject.toml` \u002F `requirements.txt` → Python stack → vulture, deptry,\n  unimport.\n- `go.mod` → Go stack → `deadcode`, `unused` (staticcheck U1000).\n- `Cargo.toml` → Rust stack → `cargo-udeps`, `cargo-machete`.\n- Other stacks → probe for an equivalent (see\n  `references\u002Fdetection-and-classification.md` §1 for the full table);\n  if genuinely nothing applies, fall back to a scoped `grep`\u002FSalak-only pass\n  and say so explicitly rather than silently skipping detection.\n\nAlso probe: is there a test suite runnable right now (`npm test`, `pytest`,\n`go test`, `cargo test`, ...)? **This gates Phase 3** — cleanup without a\nrunnable test suite is materially riskier; if none exists, say so up front\nand get explicit confirmation before removing anything beyond the most\nobviously SAFE category (unused dependencies).\n\nAlso probe (silent, same pattern as `dev-kickoff-edho-ferdian`): is `salak`\ninstalled? See Phase 2 — **detect, defer, never require.**\n\n---\n\n## Phase 1 — Detect and classify\n\nRun the stack's detection tools (in parallel where independent). Every hit\ngets one of three risk labels before anything is touched — full definitions,\nexamples, and the detection commands table are in\n**`references\u002Fdetection-and-classification.md`**:\n\n- **SAFE** — e.g. an unused private function\u002Fvariable with zero references\n  anywhere in the repo, confirmed by both the tool and a grep.\n- **CAREFUL** — e.g. an exported symbol that could plausibly be consumed\n  externally (a package's public export, a route handler, a CLI entry point)\n  even though nothing in-repo references it.\n- **RISKY** — e.g. something referenced only in string form (a dynamic\n  `import(variableName)`, a route table built from a config string, a\n  reflection\u002FDI lookup by name), where static tools structurally cannot see\n  the reference.\n\nA tool's \"unused\" verdict is a **hypothesis**, not a verdict — Phase 2\ndegrades or confirms it against ground truth before it's actionable.\n\n---\n\n## Phase 2 — Salak cross-check (key differentiator)\n\n**This is what makes this skill materially better than running `knip` alone.**\nStatic-heuristic tools alone have a known failure mode: they miss dynamic\nusage (string-based imports, reflection, DI containers) and can over-report\nsymbols that look unused syntactically but have an inbound edge the tool's\nAST walk didn't model.\n\nIf Salak (`salak`) is installed, **every candidate must be cross-checked\nagainst Salak's reverse-dependency data (`salak query importers`) before it\nis deleted** —\nfull procedure, exit-code contract, and the downgrade rule in\n**`references\u002Fsalak-cross-check.md`**. In short:\n\n- A knip\u002Fdepcheck\u002Fts-prune \"unused\" hit that Salak's graph shows has an\n  inbound `depends_on`\u002F`imports` edge is a **false positive** — downgrade\n  from SAFE to at least CAREFUL, or skip it outright.\n- Follows the exact detect-defer-never-require pattern from\n  `dev-kickoff-edho-ferdian\u002Freferences\u002Fsalak-integration.md` — replicated,\n  not reinvented, in `references\u002Fsalak-cross-check.md`.\n- If Salak isn't installed, this phase is a no-op: proceed with Phase 1's\n  classification unchanged. Never require Salak, never tell the user to\n  install it as a blocker — mention it as an optional upgrade at most once.\n\n---\n\n## Phase 3 — Staged removal + verification loop\n\n**Hard rule: never delete in the same commit\u002Fpass as an unrelated change.**\nA cleanup pass must be isolatable and revertable on its own — if the user\nasks for a feature change and a cleanup together, do the cleanup as its own\ncommit(s) before or after the feature work, never interleaved.\n\nRemove in this fixed order, one category at a time, **running the test\nsuite after each category** — not just once at the end, so a regression is\ncaught at the smallest possible blast radius:\n\n1. **Unused dependencies** → run tests → commit.\n2. **Unused exports** → run tests → commit.\n3. **Unused files** → run tests → commit.\n4. **Duplicate code** (consolidate, keep the most complete\u002Fbest-tested\n   implementation, update all call sites, delete the rest) → run tests →\n   commit.\n\nOnly SAFE (and Salak-confirmed) items proceed without extra confirmation.\nCAREFUL items get called out to the user before removal, with the specific\nreason they're not SAFE. RISKY items are reported, not removed, unless the\nuser explicitly overrides after seeing the reasoning.\n\nFull safety checklist, per-batch commit message format, and the \"when NOT to\nrun this skill at all\" list (active feature development, right before a\ndeploy, no test coverage, code you don't understand) are in\n**`references\u002Fremoval-and-verification.md`**.\n\n### Reflection gate (mandatory before any deletion)\n\nBefore removing anything currently classified SAFE, ask explicitly:\n\n> \"Would removing this break a caller that isn't in this codebase — a\n> published package's public API, a documented extension point, a webhook\n> handler an external service calls by convention\u002Fname?\"\n\nIf the code **is** a library's public surface (this repo publishes a package\nothers `import`\u002F`require`), **treat every export as CAREFUL minimum, never\nSAFE** — a zero-in-repo-reference export of a published library is exactly\nthe case static tools and even Salak's in-repo graph cannot rule out, because\nthe caller lives in someone else's repo.\n\n---\n\n## Phase 4 — Report\n\nAfter the last category, report to the user (Bahasa Indonesia for the\nnarrative, English for identifiers\u002Fpaths):\n\n- What was removed per category, with counts.\n- What was downgraded\u002Fskipped by the Salak cross-check, and why (this is the\n  evidence that the differentiator actually did something on this run).\n- What was flagged CAREFUL\u002FRISKY and left untouched, with reasoning.\n- Test suite status after each category (pass\u002Ffail), and final build status.\n- Bundle size delta if measurable (JS\u002FTS stacks).\n\n## Global rules\n\n1. **Detect the stack from the manifest, don't ask** unless genuinely\n   ambiguous.\n2. **Classify before touching anything.** No exceptions for \"obviously dead\"\n   code — the classification step is what catches the cases that look\n   obvious and aren't.\n3. **Salak is ground truth when present, optional when absent.**\n   Detect-defer-never-require, always.\n4. **Test between categories, not just at the end.**\n5. **One cleanup pass = one isolatable, revertable unit of work.** Never\n   mixed with unrelated changes.\n6. **A library's public export is never SAFE.** CAREFUL minimum.\n7. **Language routing** as defined above.\n",{"name":5,"metadata":24,"description":7},{"last_reviewed":25},"2026-09-19","main","533d32ad55c92d40fbabe93cbe21fe048598fe5a",".hermes\u002Fskills\u002Fdead-code-cleanup-edho-ferdian",0,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF","https:\u002F\u002Fgithub.com\u002Fedhoferdian","Elevating ideas through AI, rising from humble beginnings to mastering the frontiers of the web. Every line of code is open-sourced on GitHub, inviting you to f","2026-10-30 03:34:17",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add edhoferdian\u002FEEF --skill dead-code-cleanup-edho-ferdian",{"tool":40,"command":41},"bunx","bunx skills add edhoferdian\u002FEEF --skill dead-code-cleanup-edho-ferdian",{"tool":43,"command":44},"pnpm","pnpm dlx skills add edhoferdian\u002FEEF --skill dead-code-cleanup-edho-ferdian","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.hermes\u002Fskills\u002Fdead-code-cleanup-edho-ferdian\u002FSKILL.md",true,[48,54,58],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fdetection-and-classification.md","REFERENCE","参考文档",4188,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.hermes\u002Fskills\u002Fdead-code-cleanup-edho-ferdian\u002Freferences\u002Fdetection-and-classification.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fremoval-and-verification.md",4033,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.hermes\u002Fskills\u002Fdead-code-cleanup-edho-ferdian\u002Freferences\u002Fremoval-and-verification.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fsalak-cross-check.md",5601,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.hermes\u002Fskills\u002Fdead-code-cleanup-edho-ferdian\u002Freferences\u002Fsalak-cross-check.md",[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7C9FY2EWE5NB7M3YW0KJX62","video-style-edho-ferdian","Measure a reference video's look and pacing (colour grade as a 3D LUT, cut rhythm, overlays) and reproduce it: grade, cut and composite new footage, verify numerically, hand off an NLE timeline. Use for \"tiru look video ini\", \"samakan grading\", \"bikin video dengan gaya referensi\", \"LUT dari referensi\", \"cut rhythm\".","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-style-edho-ferdian\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7C9FT74P7JXGQ73116B9WS1","test-authoring-edho-ferdian","Write unit and component tests well: React Testing Library, pytest, Go and Vue, plus regression-test patterns. Use for \"tulis test untuk component ini\", \"bagaimana test hook ini\", \"test yang bagus untuk fitur X\", \"tulis test pytest\u002FGo\u002FVue\", or dev-kickoff's TEST stage.","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Ftest-authoring-edho-ferdian\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7C9FMPE9W76FS7S8ZZ48ARE","system-design-edho-ferdian","Mid-project architecture decisions: ADRs, trade-off analysis, non-functional requirements, scaling tiers and blast radius. Use for \"desain arsitektur\", \"keputusan teknis besar\", \"bikin ADR\", \"trade-off antara X dan Y\", \"microservices atau monolith\", \"apa yang rusak kalau X diubah\", or a capacity question.","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Fsystem-design-edho-ferdian\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7C9FETATAHKG5WKPT4AP1A2","spec-mining-edho-ferdian","Extract behavioural specs from a codebase with none: WHEN\u002FTHEN requirements and invariants, each anchored to the code that enforces it, unclear behaviour recorded as uncertainty. Use for \"ekstrak spec\", \"buat spec dari kode\", \"reverse-engineer the spec\", \"repo ini tidak ada dokumentasi\", or a missing BEHAVIOR_SPEC in dev-kickoff.","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Fspec-mining-edho-ferdian\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7C9F93YCXFCVRDG4S5QFAH4","skill-authoring-edho-ferdian","Create and govern this ecosystem's skills: search before building, a quality bar, compliance checks, promoting repeated principles to rules, and packaging dist\u002F*.skill. Use for \"bikin skill baru\", \"ada skill buat X gak\", \"fork skill ini\", \"skill gue kepake gak sih\", \"package skill ini\", \"buatkan .skill-nya\".","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring-edho-ferdian\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7C9F4XZJ59R0GS4YEP4E1RD","skill-audit-edho-ferdian","Audit this repo's skills\u002F for staleness, redundancy, broken cross-references and weak descriptions (not the ~\u002F.claude setup: that is config-hygiene). Use for \"audit skill saya\", \"cek skill yang sudah dibuat\", \"ada yang redundan gak\", \"skill mana yang basi\".","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Fskill-audit-edho-ferdian\u002FSKILL.md",[],[]]