[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77KRTJB2DAB3HMSJ00TV6DT":3,"skill-same:01M77KRTJB2DAB3HMSJ00TV6DT":63},{"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":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":56},"01M77KRTJB2DAB3HMSJ00TV6DT","setup",null,"Verify go-format's prerequisites and configuration here, and register its git pre-commit entry. Use when: 'set up go-format', 'configure go-format', 'is go-format working', Go import\u002Fformatting fixes silently aren't happening, or a hook reported a missing prerequisite or drifted git hook. Actions: check (read-only, default) | apply | apply install-git-hooks [scope=local|shared]. Re-runnable.","melodic-software\u002Fclaude-code-plugins","melodic-software","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F58273638?v=4","01M77JVQTXNGKCE4MDFY2BC936","Melodic Software","01M77JVQVN9QDWKAH6W03ANP76",30,"MIT","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fgo-format\u002Fskills\u002Fsetup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Verify go-format's prerequisites and configuration here, and register its git pre-commit entry. Use when: 'set up go-format', 'configure go-format', 'is go-format working', Go import\u002Fformatting fixes silently aren't happening, or a hook reported a missing prerequisite or drifted git hook. Actions: check (read-only, default) | apply | apply install-git-hooks [scope=local|shared]. Re-runnable.\"\nargument-hint: \"[check|apply [install-git-hooks [scope=local|shared]]]\"\nuser-invocable: true\ndisable-model-invocation: true\nallowed-tools:\n  - \"Bash(command -v jq*)\"\n  - \"Bash(command -v node*)\"\n  - \"Bash(command -v goimports*)\"\n  - \"Bash(node \\\"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs\\\" verify:*)\"\n  - \"Bash(node ${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs verify:*)\"\n  - \"Bash(node \\\"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs\\\" plan:*)\"\n  - \"Bash(node ${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs plan:*)\"\nshell: bash\n---\n\n## Pre-computed context\n\n`check`'s tool probes ran at load time. Read these rows instead of re-issuing them; each shows the\ntool's path when present, or `absent` when missing:\n\n- `jq`: !`command -v jq 2>\u002Fdev\u002Fnull || echo absent`\n- `node`: !`command -v node 2>\u002Fdev\u002Fnull || echo absent`\n- `goimports`: !`command -v goimports 2>\u002Fdev\u002Fnull || echo absent`\n\nA row reading `[shell command execution disabled by policy]` carries no result: run that tool's\n`command -v` probe via Bash instead.\n\n- **Pointer**: for the placeholder a skipped load-time command leaves, fetch\n  [skills § Inject dynamic context](https:\u002F\u002Fcode.claude.com\u002Fdocs\u002Fen\u002Fskills#inject-dynamic-context)\n  live.\n- **As of**: 2026-11-11\n- **Recheck trigger**: the placeholder text changes.\n\n## Purpose\n\nThin check-centric setup per the uniform setup contract (`docs\u002Fplugin-philosophy.md`\n\"Setup is explicit and repeatable\" in the marketplace repository): `check` inspects and\nreports, `apply` resolves. The only consumer-project files this plugin owns are its git-hook\nentry copies, which `apply install-git-hooks` writes. It has no consumer-config opt-in gate\n(unlike sibling formatter plugins Ruff\u002Ftypos), so the tunables are the native `userConfig`\noptions: `go_format_enabled`, `go_format_lint_gitignored` and `go_format_end_of_turn`. Like\n`spelling`, `goimports` has no per-repo dependency-manager install path in the way Ruff's\n`.venv` does. It is conventionally `go install`ed to the machine-global `$GOPATH\u002Fbin`, never as\na project dependency. `apply` is therefore guidance-only for tools: it never installs anything,\nmatching the hook's own PATH-only resolution and the plugin philosophy's never-download-silently\nrule.\n\nAction routing: no argument or `check` runs the check; `apply` runs the check first, then\nprints remediation guidance for each FAIL. Both are non-interactive. Never prompt when the\naction is given. `apply install-git-hooks` asks only where its section says to.\n\n## `check` (read-only)\n\nThe hook script (`${CLAUDE_PLUGIN_ROOT}\u002Fhooks\u002Fgo-format.sh`) is the single source of truth for\nwhat it requires and how it resolves things.\n\n**Read it first.** Probe what it actually does, don't recite this file. Then read the\npre-computed tool rows, run the remaining probes via Bash, and report a PASS\u002FFAIL\u002FINFO\ntable with one remediation line per FAIL. Do not modify anything.\nRead each option value from this text; never put a `${user_config.*}` string in a shell command.\nOpen plugin files by the `${CLAUDE_PLUGIN_ROOT}` paths this skill names; never Glob or Grep the plugin directory.\n\nWhen the plugin's toggle is disabled, every prerequisite absence except `node` downgrades from\nFAIL to INFO. The hook exits through its enabled-gate before probing anything, so a deliberately\ndisabled plugin is not broken. Report those probes informationally and note that re-enabling\nrestores the FAIL semantics. A missing `node` stays FAIL in either state: Claude Code launches\n`node` before the launcher can read the toggle, so both hook rows fail to start. A tool the git\npre-commit entry needs keeps the grade it gets with the toggle on while that entry is installed\n(step 9 reports it as a `tool` line beside an `ok`, `stale` or `modified` entry): the entry runs at\ncommit outside Claude Code and reads no toggle.\n\n1. **Bash version.** Check against the hooks' floor, Bash 3.2 or newer (`${CLAUDE_PLUGIN_ROOT}\u002Fhooks\u002Fhook-utils.sh`).\n2. **`jq`.** The pre-computed `jq` row. FAIL if absent: the batch hook then does nothing,\n   since it reads the file paths with `jq`.\n3. **`node`.** The pre-computed `node` row. FAIL if absent: every hook row launches through\n   `node hooks\u002Fexec-bash.mjs`, so without node the hooks do not start and nothing is enforced.\n   The row reflects Bash's PATH, while Claude Code resolves the hook's `node` from its own\n   environment (`docs\u002Fformatter-path-probes.md`), so a PASS here does not establish that hooks\n   launch. If hooks fail to start despite a PASS, report hook availability as unestablished.\n4. **`goimports` binary.** The pre-computed `goimports` row (the hook resolves PATH only, no\n   `.venv`-style per-repo convention). Report the resolved path and `goimports -h`'s first line\n   when found (goimports has no `--version` flag; the help header is the closest signal). FAIL\n   when absent. The hook then skips the files, and the `SessionStart` probe reports the absence\n   in every repository where the plugin is enabled, with or without `.go` files.\n5. **Hook toggle.** Report the effective `go_format_enabled` value:\n   `${user_config.go_format_enabled}` (unexpanded or empty means default `true`).\n6. **Gitignored files.** Report the effective `go_format_lint_gitignored` value:\n   `${user_config.go_format_lint_gitignored}` (unexpanded or empty means default `false`). At\n   `false` the hook skips files the repository gitignores; a tracked file matching an ignore\n   pattern stays in scope.\n7. **End-of-turn check.** Report the effective `go_format_end_of_turn` value:\n   `${user_config.go_format_end_of_turn}` (unexpanded or empty means the shipped default `false`),\n   as INFO: on, the Stop row parses the uncommitted Go files once per turn; off, only the batch\n   rewrite and the git pre-commit entry run.\n8. **Hook registration.** INFO: confirm the plugin is enabled for this project\n   (`\u002Fplugin` → Installed) rather than parsing settings files.\n9. **Git pre-commit entry.** Run `node \"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs\" verify`\n   from the repository. Each line is `\u003Cstate>\\t\u003Centry>[\\t\u003Cdetail>]`: `ok` is PASS, `declined` is\n   INFO (this clone said no; silent at session start), and `missing`, `stale`, `modified` or `superseded` is a\n   FAIL whose remediation is `apply install-git-hooks`; a `superseded` detail lists what an install under an earlier plugin name left, which that action removes on the user's yes. A `tool\\t\u003Ctool>\\tmissing` line means the\n   installed entry cannot run here: list every such tool with its install method from the\n   `${CLAUDE_PLUGIN_ROOT}\u002Fprerequisites.json` (Read that path), so a lane or cloud setup script can provision it before an\n   auto-mode session commits. Outside a git repository, report INFO and skip the step.\n\nThere is no consumer-config probe (unlike `spelling`'s config-walk check). This hook has\nno consumer-config gate by design; report that plainly as INFO, not as a gap.\n\n## `apply install-git-hooks [scope=local|shared]`\n\nRegisters the plugin's git-hook entries (`git-hooks\u002Fentries.json`) with the repository's hook\nmanager. The installer script only detects, renders and writes files the plugin owns; every step\nthat needs judgment comes back to you as a `decisions[]` item, which you reason about and apply\nwith your own edit tools.\n\n1. **Scope.** Use the argument when given. Otherwise, when the user is present, ask: `local`\n   (this clone only, nothing committed) or `shared` (committed under `.githooks\u002Fgo-format\u002F`,\n   so every teammate and agent gets it). When nobody can answer, use `local`.\n2. **Plan.** Run `node \"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs\" plan --scope \u003Cscope>`\n   and read the JSON: `manager`, `actions[]`, `decisions[]`.\n3. **Manager conflict.** A `manager-conflict` decision lists the evidence (two managers, or one\n   this installer does not drive, such as the pre-commit framework). Show it and ask which manager\n   should carry the entry; rerun `plan` with `--manager lefthook|husky|plain`. Without an answer,\n   stop here and report.\n4. **Actions.** When `actions[]` holds `copy` items, run\n   `node \"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs\" copy --scope \u003Cscope>` (plus the same\n   `--manager` when you passed one). It prints `installed`, `refreshed`, `unchanged`, `refused`,\n   `blocked`, `unsafe-path` or `stage-failed` per entry; `refused` means a locally edited copy or\n   dispatcher, which the `modified` decision covers, `blocked` that another tool owns the local\n   hooks directory, which the `hooks-path-owned` decision covers, `unsafe-path` the decision of\n   that name, and `stage-failed` that `git add` failed on a shared install: report it, since the\n   team would not receive the files.\n5. **Decisions.** Read [reference\u002Fgit-hook-decisions.md](reference\u002Fgit-hook-decisions.md) for\n   what each kind asks of you, apply each one, then rerun `plan` until only the decisions you\n   chose to leave remain.\n6. **Verify.** Run `verify` and report its lines as `check` step 9 does.\n\nThe entry rewrites: at commit it runs goimports over the staged Go files and stages the result,\nso tell the user that a commit can change the files it contains, and that a partly staged Go file\nis refused untouched. It fails a commit only for a file goimports cannot parse.\n\nWhen the user does not want an entry in this clone, run\n`node \"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs\" decline --entry goimports-format`; the\nsession-start drift line then stays silent until `verify` runs by hand, and `--undo` reverses it.\nAdd `--global` (with or without `--undo`) to decline the entry in every clone;\n`git config --global checks.git-hooks.declined true` declines every entry of every plugin, and an\nentry's own key set to `false` in a clone opts that entry back in. The [adoption\npath](https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fdocs\u002Fcontracts\u002Fcheck-placement\u002Fadopting-git-hooks.md) explains to the user each scope and why a formatter's cleanup PR comes first.\n\n## `apply` (idempotent)\n\nRun `check`, then for each FAIL print remediation guidance. Never install anything. There is\nno `apply install-goimports` write path. This skill follows the refusal template in\n[docs\u002Fplugin-philosophy.md](..\u002F..\u002F..\u002F..\u002Fdocs\u002Fplugin-philosophy.md) `### Install subactions and refusal`\nand prints the consumer-run command instead. Reason 1 applies: the hook resolves `goimports` on `PATH` only, so the install it can use,\n`go install golang.org\u002Fx\u002Ftools\u002Fcmd\u002Fgoimports@latest`, writes to the machine-global `$GOPATH\u002Fbin`;\na `go.mod` tool line is not one the hook finds.\n\nAfter the consumer installs `goimports` themselves, re-run `check` with live Bash probes (the\npre-computed rows predate the install) and report its actual result. Never claim resolved without\nre-verifying. For everything else `apply` only points:\n\n- missing `goimports`: `go install golang.org\u002Fx\u002Ftools\u002Fcmd\u002Fgoimports@latest` (requires a Go\n  toolchain: https:\u002F\u002Fgo.dev\u002Fdl\u002F).\n- missing `node` \u002F `jq` \u002F Bash: platform install instructions from the README Requirements section;\n  this skill never installs system packages.\n- toggle off: set `go_format_enabled` to `false` (and `go_format_lint_gitignored` the same way)\n  through Claude Code's native flow, interactively with `\u002Fplugin configure go-format@\u003Cmarketplace>`\n  or by a headless route, as the marketplace's plugin-reconfiguration convention gives them in\n  [§ The routes](..\u002F..\u002Freference\u002Fplugin-reconfiguration.md#the-routes)\n  (it owns the verified-version record). Apply the scope and failure-signal caveats in its\n  [§ Caveats every setup skill's short form carries](..\u002F..\u002Freference\u002Fplugin-reconfiguration.md#caveats-every-setup-skills-short-form-carries).\n  Read both sections and print what they give, the fallback route, its behavior on an\n  already-installed plugin and the scope to pass included, rather than only naming them, and\n  leave out the verified-version record.\n  Never uninstall to reconfigure; that section links what an uninstall deletes. This skill never\n  writes user settings or `pluginConfigs`. Afterwards rerun `check` in a **fresh session**, since a\n  same-session `check` can still show the old value, and report the observed effective value,\n  never an unobserved change.\n\n  - **Pointer**: for the headless command's flags, how it reports a saved or refused value, and\n    when a saved value applies, fetch\n    [plugin CLI reference § plugin configure](https:\u002F\u002Fcode.claude.com\u002Fdocs\u002Fen\u002Fplugins\u002Fcli-reference#plugin-configure)\n    live.\n\nRe-running `apply` after everything passes changes nothing and reports \"already configured\".\n\n## What this skill does NOT do\n\n- Run the formatter. Editing any `.go` file exercises the hook end-to-end; `git commit`\n  exercises the installed pre-commit entry.\n- Write the plugin cache, Claude Code user settings, or `pluginConfigs`.\n- Install `goimports`. Installation is always the consumer's own choice and command, at the\n  machine level, never a project dependency this skill records.\n- Download tools, or run any during `check` or `apply` beyond the read-only `goimports -h` probe\n  and the `install.mjs` commands named above.\n","## Pre-computed context\n\n`check`'s tool probes ran at load time. Read these rows instead of re-issuing them; each shows the\ntool's path when present, or `absent` when missing:\n\n- `jq`: !`command -v jq 2>\u002Fdev\u002Fnull || echo absent`\n- `node`: !`command -v node 2>\u002Fdev\u002Fnull || echo absent`\n- `goimports`: !`command -v goimports 2>\u002Fdev\u002Fnull || echo absent`\n\nA row reading `[shell command execution disabled by policy]` carries no result: run that tool's\n`command -v` probe via Bash instead.\n\n- **Pointer**: for the placeholder a skipped load-time command leaves, fetch\n  [skills § Inject dynamic context](https:\u002F\u002Fcode.claude.com\u002Fdocs\u002Fen\u002Fskills#inject-dynamic-context)\n  live.\n- **As of**: 2026-11-11\n- **Recheck trigger**: the placeholder text changes.\n\n## Purpose\n\nThin check-centric setup per the uniform setup contract (`docs\u002Fplugin-philosophy.md`\n\"Setup is explicit and repeatable\" in the marketplace repository): `check` inspects and\nreports, `apply` resolves. The only consumer-project files this plugin owns are its git-hook\nentry copies, which `apply install-git-hooks` writes. It has no consumer-config opt-in gate\n(unlike sibling formatter plugins Ruff\u002Ftypos), so the tunables are the native `userConfig`\noptions: `go_format_enabled`, `go_format_lint_gitignored` and `go_format_end_of_turn`. Like\n`spelling`, `goimports` has no per-repo dependency-manager install path in the way Ruff's\n`.venv` does. It is conventionally `go install`ed to the machine-global `$GOPATH\u002Fbin`, never as\na project dependency. `apply` is therefore guidance-only for tools: it never installs anything,\nmatching the hook's own PATH-only resolution and the plugin philosophy's never-download-silently\nrule.\n\nAction routing: no argument or `check` runs the check; `apply` runs the check first, then\nprints remediation guidance for each FAIL. Both are non-interactive. Never prompt when the\naction is given. `apply install-git-hooks` asks only where its section says to.\n\n## `check` (read-only)\n\nThe hook script (`${CLAUDE_PLUGIN_ROOT}\u002Fhooks\u002Fgo-format.sh`) is the single source of truth for\nwhat it requires and how it resolves things.\n\n**Read it first.** Probe what it actually does, don't recite this file. Then read the\npre-computed tool rows, run the remaining probes via Bash, and report a PASS\u002FFAIL\u002FINFO\ntable with one remediation line per FAIL. Do not modify anything.\nRead each option value from this text; never put a `${user_config.*}` string in a shell command.\nOpen plugin files by the `${CLAUDE_PLUGIN_ROOT}` paths this skill names; never Glob or Grep the plugin directory.\n\nWhen the plugin's toggle is disabled, every prerequisite absence except `node` downgrades from\nFAIL to INFO. The hook exits through its enabled-gate before probing anything, so a deliberately\ndisabled plugin is not broken. Report those probes informationally and note that re-enabling\nrestores the FAIL semantics. A missing `node` stays FAIL in either state: Claude Code launches\n`node` before the launcher can read the toggle, so both hook rows fail to start. A tool the git\npre-commit entry needs keeps the grade it gets with the toggle on while that entry is installed\n(step 9 reports it as a `tool` line beside an `ok`, `stale` or `modified` entry): the entry runs at\ncommit outside Claude Code and reads no toggle.\n\n1. **Bash version.** Check against the hooks' floor, Bash 3.2 or newer (`${CLAUDE_PLUGIN_ROOT}\u002Fhooks\u002Fhook-utils.sh`).\n2. **`jq`.** The pre-computed `jq` row. FAIL if absent: the batch hook then does nothing,\n   since it reads the file paths with `jq`.\n3. **`node`.** The pre-computed `node` row. FAIL if absent: every hook row launches through\n   `node hooks\u002Fexec-bash.mjs`, so without node the hooks do not start and nothing is enforced.\n   The row reflects Bash's PATH, while Claude Code resolves the hook's `node` from its own\n   environment (`docs\u002Fformatter-path-probes.md`), so a PASS here does not establish that hooks\n   launch. If hooks fail to start despite a PASS, report hook availability as unestablished.\n4. **`goimports` binary.** The pre-computed `goimports` row (the hook resolves PATH only, no\n   `.venv`-style per-repo convention). Report the resolved path and `goimports -h`'s first line\n   when found (goimports has no `--version` flag; the help header is the closest signal). FAIL\n   when absent. The hook then skips the files, and the `SessionStart` probe reports the absence\n   in every repository where the plugin is enabled, with or without `.go` files.\n5. **Hook toggle.** Report the effective `go_format_enabled` value:\n   `${user_config.go_format_enabled}` (unexpanded or empty means default `true`).\n6. **Gitignored files.** Report the effective `go_format_lint_gitignored` value:\n   `${user_config.go_format_lint_gitignored}` (unexpanded or empty means default `false`). At\n   `false` the hook skips files the repository gitignores; a tracked file matching an ignore\n   pattern stays in scope.\n7. **End-of-turn check.** Report the effective `go_format_end_of_turn` value:\n   `${user_config.go_format_end_of_turn}` (unexpanded or empty means the shipped default `false`),\n   as INFO: on, the Stop row parses the uncommitted Go files once per turn; off, only the batch\n   rewrite and the git pre-commit entry run.\n8. **Hook registration.** INFO: confirm the plugin is enabled for this project\n   (`\u002Fplugin` → Installed) rather than parsing settings files.\n9. **Git pre-commit entry.** Run `node \"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs\" verify`\n   from the repository. Each line is `\u003Cstate>\\t\u003Centry>[\\t\u003Cdetail>]`: `ok` is PASS, `declined` is\n   INFO (this clone said no; silent at session start), and `missing`, `stale`, `modified` or `superseded` is a\n   FAIL whose remediation is `apply install-git-hooks`; a `superseded` detail lists what an install under an earlier plugin name left, which that action removes on the user's yes. A `tool\\t\u003Ctool>\\tmissing` line means the\n   installed entry cannot run here: list every such tool with its install method from the\n   `${CLAUDE_PLUGIN_ROOT}\u002Fprerequisites.json` (Read that path), so a lane or cloud setup script can provision it before an\n   auto-mode session commits. Outside a git repository, report INFO and skip the step.\n\nThere is no consumer-config probe (unlike `spelling`'s config-walk check). This hook has\nno consumer-config gate by design; report that plainly as INFO, not as a gap.\n\n## `apply install-git-hooks [scope=local|shared]`\n\nRegisters the plugin's git-hook entries (`git-hooks\u002Fentries.json`) with the repository's hook\nmanager. The installer script only detects, renders and writes files the plugin owns; every step\nthat needs judgment comes back to you as a `decisions[]` item, which you reason about and apply\nwith your own edit tools.\n\n1. **Scope.** Use the argument when given. Otherwise, when the user is present, ask: `local`\n   (this clone only, nothing committed) or `shared` (committed under `.githooks\u002Fgo-format\u002F`,\n   so every teammate and agent gets it). When nobody can answer, use `local`.\n2. **Plan.** Run `node \"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs\" plan --scope \u003Cscope>`\n   and read the JSON: `manager`, `actions[]`, `decisions[]`.\n3. **Manager conflict.** A `manager-conflict` decision lists the evidence (two managers, or one\n   this installer does not drive, such as the pre-commit framework). Show it and ask which manager\n   should carry the entry; rerun `plan` with `--manager lefthook|husky|plain`. Without an answer,\n   stop here and report.\n4. **Actions.** When `actions[]` holds `copy` items, run\n   `node \"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs\" copy --scope \u003Cscope>` (plus the same\n   `--manager` when you passed one). It prints `installed`, `refreshed`, `unchanged`, `refused`,\n   `blocked`, `unsafe-path` or `stage-failed` per entry; `refused` means a locally edited copy or\n   dispatcher, which the `modified` decision covers, `blocked` that another tool owns the local\n   hooks directory, which the `hooks-path-owned` decision covers, `unsafe-path` the decision of\n   that name, and `stage-failed` that `git add` failed on a shared install: report it, since the\n   team would not receive the files.\n5. **Decisions.** Read [reference\u002Fgit-hook-decisions.md](reference\u002Fgit-hook-decisions.md) for\n   what each kind asks of you, apply each one, then rerun `plan` until only the decisions you\n   chose to leave remain.\n6. **Verify.** Run `verify` and report its lines as `check` step 9 does.\n\nThe entry rewrites: at commit it runs goimports over the staged Go files and stages the result,\nso tell the user that a commit can change the files it contains, and that a partly staged Go file\nis refused untouched. It fails a commit only for a file goimports cannot parse.\n\nWhen the user does not want an entry in this clone, run\n`node \"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs\" decline --entry goimports-format`; the\nsession-start drift line then stays silent until `verify` runs by hand, and `--undo` reverses it.\nAdd `--global` (with or without `--undo`) to decline the entry in every clone;\n`git config --global checks.git-hooks.declined true` declines every entry of every plugin, and an\nentry's own key set to `false` in a clone opts that entry back in. The [adoption\npath](https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fdocs\u002Fcontracts\u002Fcheck-placement\u002Fadopting-git-hooks.md) explains to the user each scope and why a formatter's cleanup PR comes first.\n\n## `apply` (idempotent)\n\nRun `check`, then for each FAIL print remediation guidance. Never install anything. There is\nno `apply install-goimports` write path. This skill follows the refusal template in\n[docs\u002Fplugin-philosophy.md](..\u002F..\u002F..\u002F..\u002Fdocs\u002Fplugin-philosophy.md) `### Install subactions and refusal`\nand prints the consumer-run command instead. Reason 1 applies: the hook resolves `goimports` on `PATH` only, so the install it can use,\n`go install golang.org\u002Fx\u002Ftools\u002Fcmd\u002Fgoimports@latest`, writes to the machine-global `$GOPATH\u002Fbin`;\na `go.mod` tool line is not one the hook finds.\n\nAfter the consumer installs `goimports` themselves, re-run `check` with live Bash probes (the\npre-computed rows predate the install) and report its actual result. Never claim resolved without\nre-verifying. For everything else `apply` only points:\n\n- missing `goimports`: `go install golang.org\u002Fx\u002Ftools\u002Fcmd\u002Fgoimports@latest` (requires a Go\n  toolchain: https:\u002F\u002Fgo.dev\u002Fdl\u002F).\n- missing `node` \u002F `jq` \u002F Bash: platform install instructions from the README Requirements section;\n  this skill never installs system packages.\n- toggle off: set `go_format_enabled` to `false` (and `go_format_lint_gitignored` the same way)\n  through Claude Code's native flow, interactively with `\u002Fplugin configure go-format@\u003Cmarketplace>`\n  or by a headless route, as the marketplace's plugin-reconfiguration convention gives them in\n  [§ The routes](..\u002F..\u002Freference\u002Fplugin-reconfiguration.md#the-routes)\n  (it owns the verified-version record). Apply the scope and failure-signal caveats in its\n  [§ Caveats every setup skill's short form carries](..\u002F..\u002Freference\u002Fplugin-reconfiguration.md#caveats-every-setup-skills-short-form-carries).\n  Read both sections and print what they give, the fallback route, its behavior on an\n  already-installed plugin and the scope to pass included, rather than only naming them, and\n  leave out the verified-version record.\n  Never uninstall to reconfigure; that section links what an uninstall deletes. This skill never\n  writes user settings or `pluginConfigs`. Afterwards rerun `check` in a **fresh session**, since a\n  same-session `check` can still show the old value, and report the observed effective value,\n  never an unobserved change.\n\n  - **Pointer**: for the headless command's flags, how it reports a saved or refused value, and\n    when a saved value applies, fetch\n    [plugin CLI reference § plugin configure](https:\u002F\u002Fcode.claude.com\u002Fdocs\u002Fen\u002Fplugins\u002Fcli-reference#plugin-configure)\n    live.\n\nRe-running `apply` after everything passes changes nothing and reports \"already configured\".\n\n## What this skill does NOT do\n\n- Run the formatter. Editing any `.go` file exercises the hook end-to-end; `git commit`\n  exercises the installed pre-commit entry.\n- Write the plugin cache, Claude Code user settings, or `pluginConfigs`.\n- Install `goimports`. Installation is always the consumer's own choice and command, at the\n  machine level, never a project dependency this skill records.\n- Download tools, or run any during `check` or `apply` beyond the read-only `goimports -h` probe\n  and the `install.mjs` commands named above.\n",{"shell":24,"description":7,"allowed-tools":25,"argument-hint":33,"user-invocable":34,"disable-model-invocation":34},"bash",[26,27,28,29,30,31,32],"Bash(command -v jq*)","Bash(command -v node*)","Bash(command -v goimports*)","Bash(node \"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs\" verify:*)","Bash(node ${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs verify:*)","Bash(node \"${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs\" plan:*)","Bash(node ${CLAUDE_PLUGIN_ROOT}\u002Flib\u002Fgit-hooks\u002Finstall.mjs plan:*)","[check|apply [install-git-hooks [scope=local|shared]]]",true,"main","5aff8ba54896bc54fd0eb46e4a954099449cf67d","plugins\u002Fgo-format\u002Fskills\u002Fsetup",7,"https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins","https:\u002F\u002Fgithub.com\u002Fmelodic-software","https:\u002F\u002Fmelodicsoftware.com","Independent software studio building developer tools, automation, and application services, with roots in music.","2026-11-15 05:15:06",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":34},[46,49,52],{"tool":47,"command":48},"npx","npx skills add melodic-software\u002Fclaude-code-plugins --skill setup",{"tool":50,"command":51},"bunx","bunx skills add melodic-software\u002Fclaude-code-plugins --skill setup",{"tool":53,"command":54},"pnpm","pnpm dlx skills add melodic-software\u002Fclaude-code-plugins --skill setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fgo-format\u002Fskills\u002Fsetup\u002FSKILL.md",[57],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"reference\u002Fgit-hook-decisions.md","REFERENCE","参考文档",5152,"https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fgo-format\u002Fskills\u002Fsetup\u002Freference\u002Fgit-hook-decisions.md",[64,71,78,85,90,97],{"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":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7DYYDG31B9YX7N9MB9QW2GW","track","Backlog reads through the bound tracker: search open and closed items, view one item with its comments and state history. Use when another skill searches or reads tracker items.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsession-flow\u002Fevals\u002Frecall-still-reports-reopened-bug\u002Fwork-items-stub\u002Fskills\u002Ftrack\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7DYXVBAVG3NV30PA7GKW9Q6","reviewer-media","Reviewer media for one pull request: decides whether it needs a narrated walkthrough, builds the storyboard from \u002Freview:explain-change's digest, has \u002Fexplainer-video:produce render it and hands the manifest to \u002Fsource-control:pull-request media. Use when asked for 'reviewer media', 'a walkthrough video for this PR', 'a produced video of this change', or when pull-request ready or monitor hands a PR over.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freview\u002Fskills\u002Freviewer-media\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7DYRZ5YD44AMYH26YR25GZ8","route","Model and effort per agent role (orchestrator, worker, verifier, retrieval) for a multi-agent run, resolved through the bundled defaults and the user, team and personal override config layers into fenced JSON with single-agent and fan-out variants and the layer behind each value. Use when asked 'which model for the subagents', 'route the roles' or 'model routing', or before a skill passes a role's model on a spawn.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fdiscovery\u002Fevals\u002Fex-model-pin-without-override\u002Fmulti-agent-stub\u002Fskills\u002Froute\u002FSKILL.md",[],[],{"skillNo":86,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DYRTVT4FWTGDJY0HCCFJMZ","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fdiscovery\u002Fevals\u002Fex-model-override-from-route\u002Fmulti-agent-stub\u002Fskills\u002Froute\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7DYNZC8PNW3T27V2ADKECKJ","principles","Module-design vocabulary for architecture findings, and the checks built on it. Use when: 'what is a deep module', 'what is a seam', 'deep vs shallow module', 'what is the deletion test', 'leverage and locality', 'module design vocabulary', 'which word do we use for X in architecture findings'. Scanning a codebase for friction is \u002Farchitecture:improve.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Farchitecture\u002Fskills\u002Fprinciples\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7DYNMCZNEWBFHV9KTSS6H60","write","Structured five-field bug report (title, steps to reproduce, expected vs actual, justified severity, suggested fix location) from an informal description, read-only. Use when the user names a defect they observed, or asks for one written up ('report a bug', 'file a bug', 'write this up as a bug').","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Farchitecture\u002Fevals\u002Fdeepening-defect-goes-to-bugs-write\u002Fbugs-stub\u002Fskills\u002Fwrite\u002FSKILL.md",[],[]]