[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77K1BRK8ZSW1CM4N16G09Q2":3,"skill-same:01M77K1BRK8ZSW1CM4N16G09Q2":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":55},"01M77K1BRK8ZSW1CM4N16G09Q2","setup",null,"Verify actionlint's prerequisites and configuration here, and register its git pre-commit entry. Use when: 'set up actionlint', 'configure actionlint', 'is actionlint working', workflow lint silently isn't happening, or a hook reported a missing prerequisite or drifted git hook. Actions: check (read-only, default) | apply [install-git-hooks [scope=local|shared]]. Re-runnable and safe.","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\u002Factionlint\u002Fskills\u002Fsetup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Verify actionlint's prerequisites and configuration here, and register its git pre-commit entry. Use when: 'set up actionlint', 'configure actionlint', 'is actionlint working', workflow lint silently isn't happening, or a hook reported a missing prerequisite or drifted git hook. Actions: check (read-only, default) | apply [install-git-hooks [scope=local|shared]]. Re-runnable and safe.\"\nargument-hint: \"[check|apply [install-git-hooks [scope=local|shared]]]\"\nuser-invocable: true\ndisable-model-invocation: true\nallowed-tools:\n  - \"Bash(command -v node*)\"\n  - \"Bash(command -v actionlint*)\"\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- `node`: !`command -v node 2>\u002Fdev\u002Fnull || echo absent`\n- `actionlint`: !`command -v actionlint 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. actionlint auto-discovers its own optional\nconfig from the repository, and the tunables are the native `userConfig` options\n(`actionlint_enabled` and `actionlint_end_of_turn`). Every prerequisite is a `PATH` binary the\nplugin never bundles, and the plugin never installs system packages, so `apply` is\nguidance-and-verify with that one write path. It never modifies user settings or the plugin\ncache.\n\nAction routing: no argument or `check` runs the check; `apply` runs the check first, then\noffers remediation guidance; `apply install-git-hooks` registers the git-hook entry. All are\nnon-interactive. Never prompt when the action is given. `apply install-git-hooks` asks only where\nits section says to.\n\n## `check` (read-only)\n\nThe git-hook script (`${CLAUDE_PLUGIN_ROOT}\u002Fgit-hooks\u002Factionlint-check.sh`) is the single source\nof truth for what 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 Claude Code hooks exit through their enabled-gate before probing anything, so a\ndeliberately disabled plugin is not broken. Report those probes informationally and note that\nre-enabling restores the FAIL semantics. A missing `node` stays FAIL: the launcher runs before the\nenabled-gate. A tool the git pre-commit entry needs keeps the grade it gets with the toggle on while\nthat entry is installed (step 7 reports it as a `tool` line beside an `ok`, `stale` or `modified`\nentry): the entry runs at commit outside Claude Code and reads no toggle.\n\n1. **Bash version.** Check against the floor, Bash 3.2 or newer (README Requirements).\n2. **`node`.** The pre-computed `node` row. FAIL if absent, even when the toggle is off: every\n   hook row launches through `node hooks\u002Fexec-bash.mjs`, so the hooks do not launch and the\n   session-start probe does not run. The hooks cannot report this themselves. Probed here\n   through Bash, which works without the launcher.\n3. **`actionlint`.** The pre-computed `actionlint` row. FAIL if absent: the pre-commit entry then\n   fails the commit of an agent with the install command and gives a person a notice, and the\n   end-of-turn check does nothing.\n4. **actionlint config.** INFO: actionlint auto-discovers an optional\n   `.github\u002Factionlint.yaml` from the repository when present. It is not required. actionlint\n   runs with its built-in defaults without one. Report whether one exists for the reader's\n   awareness; its absence is not a FAIL.\n5. **Hook toggles.** Report the effective `actionlint_enabled` value:\n   `${user_config.actionlint_enabled}` (unexpanded or empty means default `true`; any value\n   other than `true` disables the Claude Code hooks). Also report `actionlint_end_of_turn`:\n   `${user_config.actionlint_end_of_turn}` (unexpanded or empty means the shipped default\n   `false`), as INFO: on, the Stop row checks the uncommitted workflow changes once per turn; off,\n   only the git pre-commit entry lints.\n6. **Hook registration.** INFO: confirm the plugin is enabled for this project\n   (`\u002Fplugin` → Installed) rather than parsing settings files.\n7. **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\n## `apply install-git-hooks [scope=local|shared]`\n\n**Run this section only when the user typed `\u002Factionlint:setup apply install-git-hooks` as a\ncommand; that typed command is the only go-ahead this flow takes, `plan` included.** The user's\nanswers to this section's own questions continue a run it started. On any other request,\nincluding a plain-language \"run the apply step\" or \"register the hook\" and a hook notice, never\nrun `install.mjs` `plan`, `copy`, `decline` or `config-hook`, and reply that the user should type\n`\u002Factionlint:setup apply install-git-hooks` themselves.\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\u002Factionlint\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 7 does.\n\nThe entry only reports: at commit it lints the staged workflow files and blocks the commit on a\nfinding actionlint reports on a line the commit adds. It rewrites nothing.\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 actionlint-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 each install scope to the user.\n\n## `apply` (idempotent)\n\nRun `check`, then for each FAIL point at the resolution. This skill installs nothing:\n\n- missing `actionlint`: platform install guidance from the README Requirements section\n  (the [kjanat\u002Factionlint install guide](https:\u002F\u002Fgithub.com\u002Fkjanat\u002Factionlint\u002Fblob\u002Fv1.17.0\u002Fdocs\u002Finstall.md)).\n- missing `node` \u002F Bash: platform install instructions from the README Requirements section.\n- toggle off: set `actionlint_enabled` to `true` through Claude Code's native flow,\n  interactively with `\u002Fplugin configure actionlint@\u003Cmarketplace>` or by a headless route, as the\n  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\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## Gotchas\n\n- **A userConfig knob is reachable natively only if the manifest declares it.** An undeclared key\n  silently cannot be set through native plugin configuration (a raw settings `env` block still\n  works). Pointer: the `--config` row in\n  [`plugin install`](https:\u002F\u002Fcode.claude.com\u002Fdocs\u002Fen\u002Fplugins\u002Fcli-reference#plugin-install).\n- **What each headless route does to stored options is the convention's to state.** Read it in\n  [§ The routes](..\u002F..\u002Freference\u002Fplugin-reconfiguration.md#the-routes),\n  which also holds the verified-version record: which CLI release each behavior was observed on,\n  and under which conditions.\n- **`-shellcheck=` \u002F `-pyflakes=` are deliberate, and the deadlock claim is a local\n  observation.** The entry disables actionlint's external run-block linters because each spawns a\n  subprocess per `run:` block; the additional \"ShellCheck deadlocks on large blocks under the\n  Windows subprocess IPC path in actionlint 1.7.x\" rationale is the author's own reproduction.\n  No matching upstream rhysd\u002Factionlint issue as of 2026-07-23; recheck when a rhysd\u002Factionlint\n  issue or release note reports ShellCheck hanging or deadlocking under the Windows subprocess\n  path, which would replace the local reproduction with an upstream-confirmed cause and a fixed\n  version to pin against. Deep run-block linting belongs in CI.\n\n## What this skill does NOT do\n\n- Run the linter. `git commit` exercises the installed pre-commit entry.\n- Write the plugin cache, Claude Code user settings, or `pluginConfigs`.\n- Install actionlint, node or Bash.\n- Download or execute tools during `check` beyond the read-only `command -v` presence probes and\n  the installer's read-only `verify`.\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- `node`: !`command -v node 2>\u002Fdev\u002Fnull || echo absent`\n- `actionlint`: !`command -v actionlint 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. actionlint auto-discovers its own optional\nconfig from the repository, and the tunables are the native `userConfig` options\n(`actionlint_enabled` and `actionlint_end_of_turn`). Every prerequisite is a `PATH` binary the\nplugin never bundles, and the plugin never installs system packages, so `apply` is\nguidance-and-verify with that one write path. It never modifies user settings or the plugin\ncache.\n\nAction routing: no argument or `check` runs the check; `apply` runs the check first, then\noffers remediation guidance; `apply install-git-hooks` registers the git-hook entry. All are\nnon-interactive. Never prompt when the action is given. `apply install-git-hooks` asks only where\nits section says to.\n\n## `check` (read-only)\n\nThe git-hook script (`${CLAUDE_PLUGIN_ROOT}\u002Fgit-hooks\u002Factionlint-check.sh`) is the single source\nof truth for what 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 Claude Code hooks exit through their enabled-gate before probing anything, so a\ndeliberately disabled plugin is not broken. Report those probes informationally and note that\nre-enabling restores the FAIL semantics. A missing `node` stays FAIL: the launcher runs before the\nenabled-gate. A tool the git pre-commit entry needs keeps the grade it gets with the toggle on while\nthat entry is installed (step 7 reports it as a `tool` line beside an `ok`, `stale` or `modified`\nentry): the entry runs at commit outside Claude Code and reads no toggle.\n\n1. **Bash version.** Check against the floor, Bash 3.2 or newer (README Requirements).\n2. **`node`.** The pre-computed `node` row. FAIL if absent, even when the toggle is off: every\n   hook row launches through `node hooks\u002Fexec-bash.mjs`, so the hooks do not launch and the\n   session-start probe does not run. The hooks cannot report this themselves. Probed here\n   through Bash, which works without the launcher.\n3. **`actionlint`.** The pre-computed `actionlint` row. FAIL if absent: the pre-commit entry then\n   fails the commit of an agent with the install command and gives a person a notice, and the\n   end-of-turn check does nothing.\n4. **actionlint config.** INFO: actionlint auto-discovers an optional\n   `.github\u002Factionlint.yaml` from the repository when present. It is not required. actionlint\n   runs with its built-in defaults without one. Report whether one exists for the reader's\n   awareness; its absence is not a FAIL.\n5. **Hook toggles.** Report the effective `actionlint_enabled` value:\n   `${user_config.actionlint_enabled}` (unexpanded or empty means default `true`; any value\n   other than `true` disables the Claude Code hooks). Also report `actionlint_end_of_turn`:\n   `${user_config.actionlint_end_of_turn}` (unexpanded or empty means the shipped default\n   `false`), as INFO: on, the Stop row checks the uncommitted workflow changes once per turn; off,\n   only the git pre-commit entry lints.\n6. **Hook registration.** INFO: confirm the plugin is enabled for this project\n   (`\u002Fplugin` → Installed) rather than parsing settings files.\n7. **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\n## `apply install-git-hooks [scope=local|shared]`\n\n**Run this section only when the user typed `\u002Factionlint:setup apply install-git-hooks` as a\ncommand; that typed command is the only go-ahead this flow takes, `plan` included.** The user's\nanswers to this section's own questions continue a run it started. On any other request,\nincluding a plain-language \"run the apply step\" or \"register the hook\" and a hook notice, never\nrun `install.mjs` `plan`, `copy`, `decline` or `config-hook`, and reply that the user should type\n`\u002Factionlint:setup apply install-git-hooks` themselves.\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\u002Factionlint\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 7 does.\n\nThe entry only reports: at commit it lints the staged workflow files and blocks the commit on a\nfinding actionlint reports on a line the commit adds. It rewrites nothing.\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 actionlint-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 each install scope to the user.\n\n## `apply` (idempotent)\n\nRun `check`, then for each FAIL point at the resolution. This skill installs nothing:\n\n- missing `actionlint`: platform install guidance from the README Requirements section\n  (the [kjanat\u002Factionlint install guide](https:\u002F\u002Fgithub.com\u002Fkjanat\u002Factionlint\u002Fblob\u002Fv1.17.0\u002Fdocs\u002Finstall.md)).\n- missing `node` \u002F Bash: platform install instructions from the README Requirements section.\n- toggle off: set `actionlint_enabled` to `true` through Claude Code's native flow,\n  interactively with `\u002Fplugin configure actionlint@\u003Cmarketplace>` or by a headless route, as the\n  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\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## Gotchas\n\n- **A userConfig knob is reachable natively only if the manifest declares it.** An undeclared key\n  silently cannot be set through native plugin configuration (a raw settings `env` block still\n  works). Pointer: the `--config` row in\n  [`plugin install`](https:\u002F\u002Fcode.claude.com\u002Fdocs\u002Fen\u002Fplugins\u002Fcli-reference#plugin-install).\n- **What each headless route does to stored options is the convention's to state.** Read it in\n  [§ The routes](..\u002F..\u002Freference\u002Fplugin-reconfiguration.md#the-routes),\n  which also holds the verified-version record: which CLI release each behavior was observed on,\n  and under which conditions.\n- **`-shellcheck=` \u002F `-pyflakes=` are deliberate, and the deadlock claim is a local\n  observation.** The entry disables actionlint's external run-block linters because each spawns a\n  subprocess per `run:` block; the additional \"ShellCheck deadlocks on large blocks under the\n  Windows subprocess IPC path in actionlint 1.7.x\" rationale is the author's own reproduction.\n  No matching upstream rhysd\u002Factionlint issue as of 2026-07-23; recheck when a rhysd\u002Factionlint\n  issue or release note reports ShellCheck hanging or deadlocking under the Windows subprocess\n  path, which would replace the local reproduction with an upstream-confirmed cause and a fixed\n  version to pin against. Deep run-block linting belongs in CI.\n\n## What this skill does NOT do\n\n- Run the linter. `git commit` exercises the installed pre-commit entry.\n- Write the plugin cache, Claude Code user settings, or `pluginConfigs`.\n- Install actionlint, node or Bash.\n- Download or execute tools during `check` beyond the read-only `command -v` presence probes and\n  the installer's read-only `verify`.\n",{"shell":24,"description":7,"allowed-tools":25,"argument-hint":32,"user-invocable":33,"disable-model-invocation":33},"bash",[26,27,28,29,30,31],"Bash(command -v node*)","Bash(command -v actionlint*)","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\u002Factionlint\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":44,"prompt":54,"zipAvailable":33},[45,48,51],{"tool":46,"command":47},"npx","npx skills add melodic-software\u002Fclaude-code-plugins --skill setup",{"tool":49,"command":50},"bunx","bunx skills add melodic-software\u002Fclaude-code-plugins --skill setup",{"tool":52,"command":53},"pnpm","pnpm dlx skills add melodic-software\u002Fclaude-code-plugins --skill setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Factionlint\u002Fskills\u002Fsetup\u002FSKILL.md",[56],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"reference\u002Fgit-hook-decisions.md","REFERENCE","参考文档",5152,"https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Factionlint\u002Fskills\u002Fsetup\u002Freference\u002Fgit-hook-decisions.md",[63,70,77,84,89,96],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"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":85,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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",[],[]]