setup

Pre-computed context

check's tool probes ran at load time. Read these rows instead of re-issuing them; each shows the tool's path when present, or absent when missing:

• node: !command -v node 2>/dev/null || echo absent
• actionlint: !command -v actionlint 2>/dev/null || echo absent

A row reading [shell command execution disabled by policy] carries no result: run that tool's command -v probe via Bash instead.

Purpose

Thin check-centric setup per the uniform setup contract (docs/plugin-philosophy.md "Setup is explicit and repeatable" in the marketplace repository): check inspects and reports, apply resolves. The only consumer-project files this plugin owns are its git-hook entry copies, which apply install-git-hooks writes. actionlint auto-discovers its own optional config from the repository, and the tunables are the native userConfig options (actionlint_enabled and actionlint_end_of_turn). Every prerequisite is a PATH binary the plugin never bundles, and the plugin never installs system packages, so apply is guidance-and-verify with that one write path. It never modifies user settings or the plugin cache.

Action routing: no argument or check runs the check; apply runs the check first, then offers remediation guidance; apply install-git-hooks registers the git-hook entry. All are non-interactive. Never prompt when the action is given. apply install-git-hooks asks only where its section says to.

check (read-only)

The git-hook script (${CLAUDE_PLUGIN_ROOT}/git-hooks/actionlint-check.sh) is the single source of truth for what it requires and how it resolves things.

Read it first. Probe what it actually does, don't recite this file. Then read the pre-computed tool rows, run the remaining probes via Bash, and report a PASS/FAIL/INFO table with one remediation line per FAIL. Do not modify anything.

When the plugin's toggle is disabled, every prerequisite absence except node downgrades from FAIL to INFO. The Claude Code hooks exit through their enabled-gate before probing anything, so a deliberately disabled plugin is not broken. Report those probes informationally and note that re-enabling restores the FAIL semantics. A missing node stays FAIL: the launcher runs before the enabled-gate.