[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77K67RRR3R2VAKGATVX2JS7":3,"skill-same:01M77K67RRR3R2VAKGATVX2JS7":64},{"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":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":57},"01M77K67RRR3R2VAKGATVX2JS7","setup",null,"Verify bash-format's prerequisites and configuration here, and register its git pre-commit entry. Use when: 'set up bash-format', 'configure bash-format', 'is bash-format working', shell lint or formatting silently isn't happening, or a hook reported a missing prerequisite or drifted git hook. Actions: check (read-only verification, 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\u002Fbash-format\u002Fskills\u002Fsetup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Verify bash-format's prerequisites and configuration here, and register its git pre-commit entry. Use when: 'set up bash-format', 'configure bash-format', 'is bash-format working', shell lint or formatting silently isn't happening, or a hook reported a missing prerequisite or drifted git hook. Actions: check (read-only verification, 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 shellcheck*)\"\n  - \"Bash(command -v shfmt*)\"\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- `shellcheck`: !`command -v shellcheck 2>\u002Fdev\u002Fnull || echo absent`\n- `shfmt`: !`command -v shfmt 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. Linting rules come from the repository's\nown `.shellcheckrc`, formatting from its `.editorconfig`, and the tunables are the native\n`userConfig` options (the on\u002Foff toggle, the gitignored-file switch and the end-of-turn check).\nEvery prerequisite is a `PATH` binary the plugin never bundles, and the plugin never installs\nsystem packages, so the rest of `apply` is guidance-only. It never modifies user settings or the\nplugin cache.\n\nAction routing: no argument or `check` runs the check; `apply` runs the check first, then\noffers remediation guidance. Both are non-interactive. Never prompt when the action is given.\n`apply install-git-hooks` asks only where its section says to.\n\n## `check` (read-only)\n\nThe batch hook (`${CLAUDE_PLUGIN_ROOT}\u002Fhooks\u002Fbash-format.sh`), the pre-commit check\n(`${CLAUDE_PLUGIN_ROOT}\u002Fgit-hooks\u002Fshell-check.sh`) and the shared rewrite helper\n(`${CLAUDE_PLUGIN_ROOT}\u002Fgit-hooks\u002Fshfmt-rewrite.sh`) are the single source of truth for what\nthey require and how they resolve 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\nThe format pass (the batch row and the pre-commit rewrite) and the lint pass (the pre-commit\nShellCheck findings) are independent; report each separately.\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 the probes informationally and note that re-enabling\nrestores the FAIL semantics. A missing `node` stays FAIL in either state: every hook row launches\n`node`, and the gate runs inside `hooks\u002Fexec-bash.mjs`. A tool the git pre-commit entry needs keeps\nthe grade it gets with the toggle on while that entry is installed (step 12 reports it as a `tool`\nline beside an `ok`, `stale` or `modified` entry): the entry runs at commit outside Claude Code\nand 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. **`node`.** The pre-computed `node` row. FAIL if absent: every hook row launches through\n   `node hooks\u002Fexec-bash.mjs`, so without `node` the hook does not launch and no shell edit is\n   formatted in the session (`${CLAUDE_PLUGIN_ROOT}\u002FREADME.md` Requirements).\n3. **`jq`.** The pre-computed `jq` row. FAIL if absent: the batch row does nothing, since it\n   reads the file paths with `jq`, and the pre-commit rewrite is skipped.\n4. **`shellcheck`** (lint pass). The pre-computed `shellcheck` row. FAIL if absent: the pre-commit\n   entry reports no findings.\n5. **`shfmt`** (format pass). The pre-computed `shfmt` row. Its FAIL\u002FINFO status depends on the\n   `.editorconfig` opt-in below, because the format pass runs **only when the repo has opted\n   in**:\n   - opted in AND `shfmt` absent → FAIL: neither the batch row nor the pre-commit entry formats.\n   - not opted in → INFO regardless of `shfmt`: the format pass stays quiet by design (the\n     repo chose not to format), so a missing `shfmt` is not a defect here.\n6. **`.editorconfig` shell opt-in.** Mirror the hook's opt-in logic\n   (`shfmt_governed` \u002F `section_applies_to_shell` in `${CLAUDE_PLUGIN_ROOT}\u002Fgit-hooks\u002Fshfmt-rewrite.sh`), not merely \"does an\n   `.editorconfig` exist\". The opt-in is an EditorConfig **section that names shell files**:\n   a shell glob such as `[*.sh]`, `[*.bash]`, or `[*.{sh,bash}]` (including path-prefixed\n   forms like `[**\u002F*.sh]`), discovered by walking up from the file's directory to the repo\n   root and stopping at a `root = true` config. A bare `[*]` catch-all does NOT count (most\n   repos only set line-ending \u002F charset properties there). Path-only sections like\n   `[scripts\u002F**]` do NOT count either. Report as INFO: whether a governing shell section\n   exists and therefore whether the format pass is active. If none exists, INFO-note the\n   consequence per the hook's logic: shell files are left unformatted rather than rewritten\n   to shfmt's built-in defaults.\n7. **`.shellcheckrc`.** INFO: ShellCheck auto-discovers `.shellcheckrc` by walking up from\n   the file's directory. Report whether one exists; its absence is not a FAIL (ShellCheck\n   applies its own defaults).\n8. **Hook options.** Report the effective values. `${user_config.bash_format_enabled}`\n   (unexpanded or empty means the manifest default `true`; any value other than `true`\n   disables the hook). `${user_config.bash_format_lint_gitignored}` (unexpanded or empty means\n   the manifest default `false`): unless it is `true`, the batch row silently skips an edit to a\n   file the repository gitignores, so a user asking why `.work\u002Fscratch.sh` was not formatted\n   gets this answer. `${user_config.bash_format_end_of_turn}` (unexpanded or empty means the\n   shipped default `false`), as INFO: on, the Stop row checks the uncommitted changes once per\n   turn; off, only the batch format and the git pre-commit entry run.\n9. **Hook registration.** INFO: confirm the plugin is enabled for this project\n   (`\u002Fplugin` → Installed) rather than parsing settings files.\n10. **Project scope.** INFO: when `CLAUDE_PROJECT_DIR` is set, the batch row acts only\n   on shell files inside it (symlink-resolved membership guard in the shared hook\n   library, aware of Windows 8.3 short-name spellings of in-project paths, a\n   per-volume property; only volumes with 8.3 generation enabled produce them);\n   a `.sh`\u002F`.bash` file written *outside* the project (temp\u002Fscratchpad\n   dirs) is silently skipped. No lint, no format, no notice. The OS temp tree\n   counts as outside even when it sits under `CLAUDE_PROJECT_DIR`, unless the\n   project root itself lives under temp. When\n   `CLAUDE_PROJECT_DIR` is **unset** (e.g. some headless `-p` sessions) the guard\n   is skipped and any existing edited file is processed. Report this so a green\n   `check` is not read as \"every shell edit anywhere is covered\".\n11. **Gitignored files.** INFO: unless `bash_format_lint_gitignored` is `true`, a file the\n    repository gitignores (`git check-ignore`) is silently skipped: no lint, no format, no\n    notice. A tracked file that matches an ignore pattern stays in scope, and when git cannot\n    decide (git absent, no repository, an error) the hook acts as before\n    (`hook::gitignored_out_of_scope` in `${CLAUDE_PLUGIN_ROOT}\u002Fhooks\u002Fhook-utils.sh`). Report the item 8 value\n    beside this.\n12. **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\nWhen every probe passes, report the result **with the scope caveats** (items 10 and 11).\nNever an unqualified \"fully operational\", which would imply out-of-project shell\nedits are covered when they are deliberately skipped.\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\u002Fbash-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 12 does.\n\nThe entry rewrites: at commit it formats the staged shell scripts an `.editorconfig` section\ngoverns and stages the result, so tell the user that a commit can change the files it contains,\nand that a partly staged governed script is refused untouched.\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 shell-check`; 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 point at the resolution. Apart from the git-hook entry above, this\nskill installs nothing:\n\n- missing `shellcheck`: install guidance from the README Requirements section\n  (the [ShellCheck install guide](https:\u002F\u002Fgithub.com\u002Fkoalaman\u002Fshellcheck#installing)); this\n  skill never installs system packages.\n- missing `shfmt` while the repo opts in: install guidance\n  ([shfmt](https:\u002F\u002Fgithub.com\u002Fmvdan\u002Fsh#shfmt)); this skill never installs system packages.\n- missing `node` \u002F `jq` \u002F Bash: platform install instructions from the README Requirements section.\n- no shell `.editorconfig` opt-in (and formatting is wanted): explain that adding a governing\n  shell section (`[*.sh]`, `[*.bash]`, or `[*.{sh,bash}]`) to an `.editorconfig` opts the\n  repo in. A bare `[*]` is not enough, but this skill does not write it. `.editorconfig` is\n  cross-cutting (it governs every editor and tool in the repo), so the choice and the edit\n  belong to the consumer.\n- toggle off, gitignored files wanted, or the end-of-turn check wanted: set\n  `bash_format_enabled`, `bash_format_lint_gitignored` or `bash_format_end_of_turn` to `true`\n  through Claude Code's native flow, interactively with\n  `\u002Fplugin configure bash-format@\u003Cmarketplace>` or by a headless route, as the marketplace's\n  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\nAfter pointing at a remediation, re-run the relevant `check` probe live via Bash (a pre-computed row\npredates the remediation, so never re-read it) and report its actual result. Never claim resolved on\nthe reader's report that they installed something.\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 linter or formatter. Editing any `.sh` or `.bash` file exercises the batch row end to\n  end; `git commit` exercises the installed pre-commit entry.\n- Write the plugin cache, Claude Code user settings, or `pluginConfigs`. Nor the repository,\n  beyond the git-hook entry copies, including `.editorconfig` \u002F `.shellcheckrc`. Every\n  prerequisite is a `PATH` binary or the native toggle, so remediation is guidance only.\n- Download or execute tools during `check` beyond the read-only `command -v` presence probes.\n\n## Gotchas\n\n- **`ENAMETOOLONG` when grepping the plugin cache.** Installed plugins run from a\n  deeply nested, cache-isolated path. Piping a `grep`\u002F`rg` over the long absolute\n  path to `hooks\u002Fhook-utils.sh` (or another bundled file) can spawn-fail with\n  `ENAMETOOLONG` on some hosts. Read the file directly rather than passing the full\n  cache path on the command line.\n- **`check` PASS ≠ every shell edit is covered.** When `CLAUDE_PROJECT_DIR` is set\n  the hook is project-scoped (probe 10): shell files written outside it are silently\n  skipped, so a fully green `check` still does not cover out-of-project edits. (When\n  `CLAUDE_PROJECT_DIR` is unset the scoping does not apply. See probe 10.)\n- **`shfmt` FAIL is opt-in-conditional.** A missing `shfmt` is only a FAIL when an\n  `.editorconfig` section governs shell files; without that opt-in it is INFO, not\n  a defect. Resolve the `.editorconfig` opt-in state before calling `shfmt` a failure.\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- `shellcheck`: !`command -v shellcheck 2>\u002Fdev\u002Fnull || echo absent`\n- `shfmt`: !`command -v shfmt 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. Linting rules come from the repository's\nown `.shellcheckrc`, formatting from its `.editorconfig`, and the tunables are the native\n`userConfig` options (the on\u002Foff toggle, the gitignored-file switch and the end-of-turn check).\nEvery prerequisite is a `PATH` binary the plugin never bundles, and the plugin never installs\nsystem packages, so the rest of `apply` is guidance-only. It never modifies user settings or the\nplugin cache.\n\nAction routing: no argument or `check` runs the check; `apply` runs the check first, then\noffers remediation guidance. Both are non-interactive. Never prompt when the action is given.\n`apply install-git-hooks` asks only where its section says to.\n\n## `check` (read-only)\n\nThe batch hook (`${CLAUDE_PLUGIN_ROOT}\u002Fhooks\u002Fbash-format.sh`), the pre-commit check\n(`${CLAUDE_PLUGIN_ROOT}\u002Fgit-hooks\u002Fshell-check.sh`) and the shared rewrite helper\n(`${CLAUDE_PLUGIN_ROOT}\u002Fgit-hooks\u002Fshfmt-rewrite.sh`) are the single source of truth for what\nthey require and how they resolve 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\nThe format pass (the batch row and the pre-commit rewrite) and the lint pass (the pre-commit\nShellCheck findings) are independent; report each separately.\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 the probes informationally and note that re-enabling\nrestores the FAIL semantics. A missing `node` stays FAIL in either state: every hook row launches\n`node`, and the gate runs inside `hooks\u002Fexec-bash.mjs`. A tool the git pre-commit entry needs keeps\nthe grade it gets with the toggle on while that entry is installed (step 12 reports it as a `tool`\nline beside an `ok`, `stale` or `modified` entry): the entry runs at commit outside Claude Code\nand 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. **`node`.** The pre-computed `node` row. FAIL if absent: every hook row launches through\n   `node hooks\u002Fexec-bash.mjs`, so without `node` the hook does not launch and no shell edit is\n   formatted in the session (`${CLAUDE_PLUGIN_ROOT}\u002FREADME.md` Requirements).\n3. **`jq`.** The pre-computed `jq` row. FAIL if absent: the batch row does nothing, since it\n   reads the file paths with `jq`, and the pre-commit rewrite is skipped.\n4. **`shellcheck`** (lint pass). The pre-computed `shellcheck` row. FAIL if absent: the pre-commit\n   entry reports no findings.\n5. **`shfmt`** (format pass). The pre-computed `shfmt` row. Its FAIL\u002FINFO status depends on the\n   `.editorconfig` opt-in below, because the format pass runs **only when the repo has opted\n   in**:\n   - opted in AND `shfmt` absent → FAIL: neither the batch row nor the pre-commit entry formats.\n   - not opted in → INFO regardless of `shfmt`: the format pass stays quiet by design (the\n     repo chose not to format), so a missing `shfmt` is not a defect here.\n6. **`.editorconfig` shell opt-in.** Mirror the hook's opt-in logic\n   (`shfmt_governed` \u002F `section_applies_to_shell` in `${CLAUDE_PLUGIN_ROOT}\u002Fgit-hooks\u002Fshfmt-rewrite.sh`), not merely \"does an\n   `.editorconfig` exist\". The opt-in is an EditorConfig **section that names shell files**:\n   a shell glob such as `[*.sh]`, `[*.bash]`, or `[*.{sh,bash}]` (including path-prefixed\n   forms like `[**\u002F*.sh]`), discovered by walking up from the file's directory to the repo\n   root and stopping at a `root = true` config. A bare `[*]` catch-all does NOT count (most\n   repos only set line-ending \u002F charset properties there). Path-only sections like\n   `[scripts\u002F**]` do NOT count either. Report as INFO: whether a governing shell section\n   exists and therefore whether the format pass is active. If none exists, INFO-note the\n   consequence per the hook's logic: shell files are left unformatted rather than rewritten\n   to shfmt's built-in defaults.\n7. **`.shellcheckrc`.** INFO: ShellCheck auto-discovers `.shellcheckrc` by walking up from\n   the file's directory. Report whether one exists; its absence is not a FAIL (ShellCheck\n   applies its own defaults).\n8. **Hook options.** Report the effective values. `${user_config.bash_format_enabled}`\n   (unexpanded or empty means the manifest default `true`; any value other than `true`\n   disables the hook). `${user_config.bash_format_lint_gitignored}` (unexpanded or empty means\n   the manifest default `false`): unless it is `true`, the batch row silently skips an edit to a\n   file the repository gitignores, so a user asking why `.work\u002Fscratch.sh` was not formatted\n   gets this answer. `${user_config.bash_format_end_of_turn}` (unexpanded or empty means the\n   shipped default `false`), as INFO: on, the Stop row checks the uncommitted changes once per\n   turn; off, only the batch format and the git pre-commit entry run.\n9. **Hook registration.** INFO: confirm the plugin is enabled for this project\n   (`\u002Fplugin` → Installed) rather than parsing settings files.\n10. **Project scope.** INFO: when `CLAUDE_PROJECT_DIR` is set, the batch row acts only\n   on shell files inside it (symlink-resolved membership guard in the shared hook\n   library, aware of Windows 8.3 short-name spellings of in-project paths, a\n   per-volume property; only volumes with 8.3 generation enabled produce them);\n   a `.sh`\u002F`.bash` file written *outside* the project (temp\u002Fscratchpad\n   dirs) is silently skipped. No lint, no format, no notice. The OS temp tree\n   counts as outside even when it sits under `CLAUDE_PROJECT_DIR`, unless the\n   project root itself lives under temp. When\n   `CLAUDE_PROJECT_DIR` is **unset** (e.g. some headless `-p` sessions) the guard\n   is skipped and any existing edited file is processed. Report this so a green\n   `check` is not read as \"every shell edit anywhere is covered\".\n11. **Gitignored files.** INFO: unless `bash_format_lint_gitignored` is `true`, a file the\n    repository gitignores (`git check-ignore`) is silently skipped: no lint, no format, no\n    notice. A tracked file that matches an ignore pattern stays in scope, and when git cannot\n    decide (git absent, no repository, an error) the hook acts as before\n    (`hook::gitignored_out_of_scope` in `${CLAUDE_PLUGIN_ROOT}\u002Fhooks\u002Fhook-utils.sh`). Report the item 8 value\n    beside this.\n12. **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\nWhen every probe passes, report the result **with the scope caveats** (items 10 and 11).\nNever an unqualified \"fully operational\", which would imply out-of-project shell\nedits are covered when they are deliberately skipped.\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\u002Fbash-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 12 does.\n\nThe entry rewrites: at commit it formats the staged shell scripts an `.editorconfig` section\ngoverns and stages the result, so tell the user that a commit can change the files it contains,\nand that a partly staged governed script is refused untouched.\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 shell-check`; 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 point at the resolution. Apart from the git-hook entry above, this\nskill installs nothing:\n\n- missing `shellcheck`: install guidance from the README Requirements section\n  (the [ShellCheck install guide](https:\u002F\u002Fgithub.com\u002Fkoalaman\u002Fshellcheck#installing)); this\n  skill never installs system packages.\n- missing `shfmt` while the repo opts in: install guidance\n  ([shfmt](https:\u002F\u002Fgithub.com\u002Fmvdan\u002Fsh#shfmt)); this skill never installs system packages.\n- missing `node` \u002F `jq` \u002F Bash: platform install instructions from the README Requirements section.\n- no shell `.editorconfig` opt-in (and formatting is wanted): explain that adding a governing\n  shell section (`[*.sh]`, `[*.bash]`, or `[*.{sh,bash}]`) to an `.editorconfig` opts the\n  repo in. A bare `[*]` is not enough, but this skill does not write it. `.editorconfig` is\n  cross-cutting (it governs every editor and tool in the repo), so the choice and the edit\n  belong to the consumer.\n- toggle off, gitignored files wanted, or the end-of-turn check wanted: set\n  `bash_format_enabled`, `bash_format_lint_gitignored` or `bash_format_end_of_turn` to `true`\n  through Claude Code's native flow, interactively with\n  `\u002Fplugin configure bash-format@\u003Cmarketplace>` or by a headless route, as the marketplace's\n  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\nAfter pointing at a remediation, re-run the relevant `check` probe live via Bash (a pre-computed row\npredates the remediation, so never re-read it) and report its actual result. Never claim resolved on\nthe reader's report that they installed something.\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 linter or formatter. Editing any `.sh` or `.bash` file exercises the batch row end to\n  end; `git commit` exercises the installed pre-commit entry.\n- Write the plugin cache, Claude Code user settings, or `pluginConfigs`. Nor the repository,\n  beyond the git-hook entry copies, including `.editorconfig` \u002F `.shellcheckrc`. Every\n  prerequisite is a `PATH` binary or the native toggle, so remediation is guidance only.\n- Download or execute tools during `check` beyond the read-only `command -v` presence probes.\n\n## Gotchas\n\n- **`ENAMETOOLONG` when grepping the plugin cache.** Installed plugins run from a\n  deeply nested, cache-isolated path. Piping a `grep`\u002F`rg` over the long absolute\n  path to `hooks\u002Fhook-utils.sh` (or another bundled file) can spawn-fail with\n  `ENAMETOOLONG` on some hosts. Read the file directly rather than passing the full\n  cache path on the command line.\n- **`check` PASS ≠ every shell edit is covered.** When `CLAUDE_PROJECT_DIR` is set\n  the hook is project-scoped (probe 10): shell files written outside it are silently\n  skipped, so a fully green `check` still does not cover out-of-project edits. (When\n  `CLAUDE_PROJECT_DIR` is unset the scoping does not apply. See probe 10.)\n- **`shfmt` FAIL is opt-in-conditional.** A missing `shfmt` is only a FAIL when an\n  `.editorconfig` section governs shell files; without that opt-in it is INFO, not\n  a defect. Resolve the `.editorconfig` opt-in state before calling `shfmt` a failure.\n",{"shell":24,"description":7,"allowed-tools":25,"argument-hint":34,"user-invocable":35,"disable-model-invocation":35},"bash",[26,27,28,29,30,31,32,33],"Bash(command -v jq*)","Bash(command -v node*)","Bash(command -v shellcheck*)","Bash(command -v shfmt*)","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","c68fcc0bf2eb1373a1c9ed172abdae781872e8d0","plugins\u002Fbash-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":46,"prompt":56,"zipAvailable":35},[47,50,53],{"tool":48,"command":49},"npx","npx skills add melodic-software\u002Fclaude-code-plugins --skill setup",{"tool":51,"command":52},"bunx","bunx skills add melodic-software\u002Fclaude-code-plugins --skill setup",{"tool":54,"command":55},"pnpm","pnpm dlx skills add melodic-software\u002Fclaude-code-plugins --skill setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbash-format\u002Fskills\u002Fsetup\u002FSKILL.md",[58],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"reference\u002Fgit-hook-decisions.md","REFERENCE","参考文档",5152,"https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbash-format\u002Fskills\u002Fsetup\u002Freference\u002Fgit-hook-decisions.md",[65,72,79,86,91,98],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"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":87,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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":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},"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":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},"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",[],[]]