[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C93P0C14HMBZ2QZVXDN9VG":3,"skill-same:01M7C93P0C14HMBZ2QZVXDN9VG":58},{"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},"01M7C93P0C14HMBZ2QZVXDN9VG","code-quality-tooling-edho-ferdian",null,"Set up the automated quality gate: Biome or ESLint+Prettier, Husky, lint-staged, and the equivalents for Python (Ruff), Go and Rust. Use for \"setup ESLint\", \"setup Biome\", \"tambah Prettier\", \"pasang husky\", \"pre-commit hook\", \"lint-staged\", \"commit ke-block linter\", \"format on save\", \"linter belum ada\".","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.zcode\u002Fskills\u002Fcode-quality-tooling-edho-ferdian\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: code-quality-tooling-edho-ferdian\ndescription: >-\n  Set up the automated quality gate: Biome or ESLint+Prettier, Husky,\n  lint-staged, and the equivalents for Python (Ruff), Go and Rust. Use for\n  \"setup ESLint\", \"setup Biome\", \"tambah Prettier\", \"pasang husky\",\n  \"pre-commit hook\", \"lint-staged\", \"commit ke-block linter\", \"format on\n  save\", \"linter belum ada\".\nmetadata:\n  last_reviewed: \"2026-09-16\"\n---\n\n# Code Quality Tooling — Edho Ferdian Mode\n\nYou are setting up the mechanical gate that catches style and lint\nviolations *before* they land in a commit or a push, not writing the style\nrules themselves and not reviewing already-written code for quality.\n\n## Boundary with neighbouring skills — read this first\n\nThis is a genuine gap this ecosystem didn't cover until now (there was no\nskill for hook\u002Fformatter\u002Flinter setup itself), so the boundary with what\nalready exists matters more than usual:\n\n| | This skill | Neighbour |\n|---|---|---|\n| Git hook enforces \"no commit without passing lint\" | **This skill** | — |\n| Commit message format, branch strategy, PR triage | `git-and-release-ops-edho-ferdian` | Different concern: message\u002Fworkflow shape, not gate tooling. Both can fire together (a pre-commit hook can also check commit message format via `commitlint`) — when it does, this skill covers wiring the hook, `git-and-release-ops-edho-ferdian` covers what the format rule should be. |\n| A build\u002Flint step is already configured but now fails | `build-fix-edho-ferdian` | This skill sets up a *working* gate for the first time or reconfigures it; a config that used to pass and now doesn't is a build-fix diagnosis, not a fresh setup. |\n| What code pattern to write in a given language\u002Fframework | `frontend-engineering-edho-ferdian`, `backend-engineering-edho-ferdian`, `language-code-review-edho-ferdian` | This skill's linter\u002Fformatter rules should reflect those patterns, but this skill doesn't author the patterns themselves. |\n| Reviewing a diff for quality issues a human should catch (naming, complexity, duplication) | `code-review-edho-ferdian` | This skill's gate catches only what a linter\u002Fformatter can catch mechanically — style, common bug patterns, import order. It is not a substitute for the review skill's judgment-based findings. |\n| Detecting whether an *already-configured* gate was tampered with (a rule quietly loosened to make a failing check pass) | `config-hygiene-edho-ferdian`'s \"Config tamper guard\" and \"Language\u002Ftool gate table\" | This skill sets up or intentionally reconfigures the gate; `config-hygiene-edho-ferdian` scans an existing config for unexplained narrowing during its periodic `~\u002F.claude`-environment hygiene pass. Its language\u002Ftool table is a fast fact-check reference for that scan, not competing setup guidance — see `references\u002Fjavascript-typescript.md` §1 for how the two tables' Biome\u002FESLint framing reconciles. |\n\n## When to use this skill\n\n- A project has no linter\u002Fformatter\u002Fgit-hooks yet and the user wants one\n  set up.\n- The user wants to add Husky pre-commit or pre-push enforcement to an\n  existing project.\n- ESLint\u002FPrettier configs conflict with each other, or a `no-unused-vars`\n  style false-positive needs a config-level fix (not a code-level one).\n- Deciding what should run in a local hook vs. only in CI (a common\n  question with no obvious default — see below).\n\n## Core recommendation for a new JS\u002FTS project\n\n1. **Biome by default** — one Rust-based tool doing both linting and\n   formatting, no ESLint\u002FPrettier config-conflict class of bug to manage,\n   and it's this ecosystem's existing default per\n   `config-hygiene-edho-ferdian`'s language\u002Ftool gate table (Biome-first\n   for `.ts`\u002F`.tsx`\u002F`.js`\u002F`.jsx`) — this skill now matches that rather than\n   contradicting it. Fall back to **ESLint + Prettier** when the project\n   needs plugin coverage Biome doesn't have yet (framework-specific rule\n   sets like `eslint-plugin-jsx-a11y`, a custom rule, or an existing large\n   ESLint config not worth migrating). See `references\u002F\n   javascript-typescript.md` §1 for the full decision guide.\n2. **Husky** (v9+, `npx husky init`) to install Git hooks that are\n   versioned in the repo (`.husky\u002F`) so every contributor gets them\n   automatically on `npm install` — not a personal `~\u002F.gitconfig` hook that\n   only exists on one machine.\n3. **lint-staged** to run the chosen linter\u002Fformatter only on staged files\n   inside the pre-commit hook — running a full-repo lint on every commit\n   doesn't scale past a small project and trains people to skip the hook\n   out of impatience.\n\nSee `references\u002Fjavascript-typescript.md` for exact config files for both\npaths, the ESLint flat-config migration note, and the hook script contents.\n\n## What goes in pre-commit vs. pre-push vs. CI-only\n\nA hook that's too slow gets bypassed (`git commit --no-verify` becomes a\nhabit); a gate that's too weak lets broken code land. Split by cost:\n\n- **pre-commit:** lint + format on staged files only (lint-staged). Should\n  finish in well under a second for a typical commit.\n- **pre-push:** the type-checker and the test suite (or a fast subset of\n  it) — expensive enough to be wrong for every commit, cheap enough to be\n  worth blocking a push.\n- **CI-only:** the full test suite, build, and any slow static analysis.\n  Never make a contributor wait for the full suite locally before every\n  push — CI is where the authoritative, complete gate lives; local hooks\n  are a fast approximation that catches most problems earlier.\n\nFull rationale and the cross-stack equivalents (Python, Go, Rust) are in\n`references\u002Fother-stacks.md`.\n\n## Language routing (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\nCommunication to the user in Bahasa Indonesia; config files, hook scripts,\nand commit-adjacent output in English — fixed, never ask. Full contract:\n`skill-authoring-edho-ferdian` §7.\n\n## External docs (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\nESLint's flat-config API, Husky's hook script format, and lint-staged's\nconfig surface have all changed across major versions in ways a memorized\nanswer can get wrong. Resolve current setup steps live via Context7 before\nwriting config into a project. Full contract: `skill-authoring-edho-ferdian`\n§9.\n\n## Provenance\n\nNative skill, added 2026-09-16 per D-048, at the user's request after\nconfirming this ecosystem had no coverage for linter\u002Fformatter\u002Fgit-hook\nsetup (checked `git-and-release-ops-edho-ferdian`, which covers commit\nformat and PR workflow but not the enforcement tooling itself). Not adapted\nfrom an external source.\n","# Code Quality Tooling — Edho Ferdian Mode\n\nYou are setting up the mechanical gate that catches style and lint\nviolations *before* they land in a commit or a push, not writing the style\nrules themselves and not reviewing already-written code for quality.\n\n## Boundary with neighbouring skills — read this first\n\nThis is a genuine gap this ecosystem didn't cover until now (there was no\nskill for hook\u002Fformatter\u002Flinter setup itself), so the boundary with what\nalready exists matters more than usual:\n\n| | This skill | Neighbour |\n|---|---|---|\n| Git hook enforces \"no commit without passing lint\" | **This skill** | — |\n| Commit message format, branch strategy, PR triage | `git-and-release-ops-edho-ferdian` | Different concern: message\u002Fworkflow shape, not gate tooling. Both can fire together (a pre-commit hook can also check commit message format via `commitlint`) — when it does, this skill covers wiring the hook, `git-and-release-ops-edho-ferdian` covers what the format rule should be. |\n| A build\u002Flint step is already configured but now fails | `build-fix-edho-ferdian` | This skill sets up a *working* gate for the first time or reconfigures it; a config that used to pass and now doesn't is a build-fix diagnosis, not a fresh setup. |\n| What code pattern to write in a given language\u002Fframework | `frontend-engineering-edho-ferdian`, `backend-engineering-edho-ferdian`, `language-code-review-edho-ferdian` | This skill's linter\u002Fformatter rules should reflect those patterns, but this skill doesn't author the patterns themselves. |\n| Reviewing a diff for quality issues a human should catch (naming, complexity, duplication) | `code-review-edho-ferdian` | This skill's gate catches only what a linter\u002Fformatter can catch mechanically — style, common bug patterns, import order. It is not a substitute for the review skill's judgment-based findings. |\n| Detecting whether an *already-configured* gate was tampered with (a rule quietly loosened to make a failing check pass) | `config-hygiene-edho-ferdian`'s \"Config tamper guard\" and \"Language\u002Ftool gate table\" | This skill sets up or intentionally reconfigures the gate; `config-hygiene-edho-ferdian` scans an existing config for unexplained narrowing during its periodic `~\u002F.claude`-environment hygiene pass. Its language\u002Ftool table is a fast fact-check reference for that scan, not competing setup guidance — see `references\u002Fjavascript-typescript.md` §1 for how the two tables' Biome\u002FESLint framing reconciles. |\n\n## When to use this skill\n\n- A project has no linter\u002Fformatter\u002Fgit-hooks yet and the user wants one\n  set up.\n- The user wants to add Husky pre-commit or pre-push enforcement to an\n  existing project.\n- ESLint\u002FPrettier configs conflict with each other, or a `no-unused-vars`\n  style false-positive needs a config-level fix (not a code-level one).\n- Deciding what should run in a local hook vs. only in CI (a common\n  question with no obvious default — see below).\n\n## Core recommendation for a new JS\u002FTS project\n\n1. **Biome by default** — one Rust-based tool doing both linting and\n   formatting, no ESLint\u002FPrettier config-conflict class of bug to manage,\n   and it's this ecosystem's existing default per\n   `config-hygiene-edho-ferdian`'s language\u002Ftool gate table (Biome-first\n   for `.ts`\u002F`.tsx`\u002F`.js`\u002F`.jsx`) — this skill now matches that rather than\n   contradicting it. Fall back to **ESLint + Prettier** when the project\n   needs plugin coverage Biome doesn't have yet (framework-specific rule\n   sets like `eslint-plugin-jsx-a11y`, a custom rule, or an existing large\n   ESLint config not worth migrating). See `references\u002F\n   javascript-typescript.md` §1 for the full decision guide.\n2. **Husky** (v9+, `npx husky init`) to install Git hooks that are\n   versioned in the repo (`.husky\u002F`) so every contributor gets them\n   automatically on `npm install` — not a personal `~\u002F.gitconfig` hook that\n   only exists on one machine.\n3. **lint-staged** to run the chosen linter\u002Fformatter only on staged files\n   inside the pre-commit hook — running a full-repo lint on every commit\n   doesn't scale past a small project and trains people to skip the hook\n   out of impatience.\n\nSee `references\u002Fjavascript-typescript.md` for exact config files for both\npaths, the ESLint flat-config migration note, and the hook script contents.\n\n## What goes in pre-commit vs. pre-push vs. CI-only\n\nA hook that's too slow gets bypassed (`git commit --no-verify` becomes a\nhabit); a gate that's too weak lets broken code land. Split by cost:\n\n- **pre-commit:** lint + format on staged files only (lint-staged). Should\n  finish in well under a second for a typical commit.\n- **pre-push:** the type-checker and the test suite (or a fast subset of\n  it) — expensive enough to be wrong for every commit, cheap enough to be\n  worth blocking a push.\n- **CI-only:** the full test suite, build, and any slow static analysis.\n  Never make a contributor wait for the full suite locally before every\n  push — CI is where the authoritative, complete gate lives; local hooks\n  are a fast approximation that catches most problems earlier.\n\nFull rationale and the cross-stack equivalents (Python, Go, Rust) are in\n`references\u002Fother-stacks.md`.\n\n## Language routing (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\nCommunication to the user in Bahasa Indonesia; config files, hook scripts,\nand commit-adjacent output in English — fixed, never ask. Full contract:\n`skill-authoring-edho-ferdian` §7.\n\n## External docs (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\nESLint's flat-config API, Husky's hook script format, and lint-staged's\nconfig surface have all changed across major versions in ways a memorized\nanswer can get wrong. Resolve current setup steps live via Context7 before\nwriting config into a project. Full contract: `skill-authoring-edho-ferdian`\n§9.\n\n## Provenance\n\nNative skill, added 2026-09-16 per D-048, at the user's request after\nconfirming this ecosystem had no coverage for linter\u002Fformatter\u002Fgit-hook\nsetup (checked `git-and-release-ops-edho-ferdian`, which covers commit\nformat and PR workflow but not the enforcement tooling itself). Not adapted\nfrom an external source.\n",{"name":5,"metadata":24,"description":7},{"last_reviewed":25},"2026-09-16","main","533d32ad55c92d40fbabe93cbe21fe048598fe5a",".zcode\u002Fskills\u002Fcode-quality-tooling-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 code-quality-tooling-edho-ferdian",{"tool":40,"command":41},"bunx","bunx skills add edhoferdian\u002FEEF --skill code-quality-tooling-edho-ferdian",{"tool":43,"command":44},"pnpm","pnpm dlx skills add edhoferdian\u002FEEF --skill code-quality-tooling-edho-ferdian","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.zcode\u002Fskills\u002Fcode-quality-tooling-edho-ferdian\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fjavascript-typescript.md","REFERENCE","参考文档",6397,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.zcode\u002Fskills\u002Fcode-quality-tooling-edho-ferdian\u002Freferences\u002Fjavascript-typescript.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fother-stacks.md",3083,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.zcode\u002Fskills\u002Fcode-quality-tooling-edho-ferdian\u002Freferences\u002Fother-stacks.md",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":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":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"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},"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":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":100,"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",[],[]]