[kalwalt]

Refs #1. This is the plugin side. The three repositories drop their copies in follow-up PRs.

The two Claude Code hooks copied into arjs-plugin-artoolkit, AR.js-next and arjs-plugin-threejs now ship once, in the arjs plugin. They are wired by plugins/arjs/hooks/hooks.json through ${CLAUDE_PLUGIN_ROOT}.

Hooks

• guard-protected-branches.mjs (PreToolUse, Bash|PowerShell) refuses git commit on main and pushes to main. It is imported from arjs-plugin-artoolkit@f8a6604 and changed as follows:
  • It acts only in AR-js-org repositories (scope.mjs): any remote.<name>.url under github.com[:/]AR-js-org/, so forks with an upstream remote count too. A plugin hook runs in every repository, so outside this scope the guard does nothing.
  • It checks the PowerShell tool. Before, it checked only Bash. It handles backtick continuations and backtick escapes, and Set-Location/sl/Push-Location with -Path/-LiteralPath.
  • It follows if ($?) { … } (the PowerShell 5.1 chaining idiom) and Bash then/do/else bodies.
  • It tracks git switch / git checkout [-c|-b] within one command, but only across &&. A switch to main holds across any separator. Without this, the release skill's dev re-sync was falsely blocked.
  • git push --tags is no longer blocked. It spawns git only when a verdict needs it, and it exits 0 silently on malformed stdin.
• format-on-edit.mjs (PostToolUse, Edit|Write|MultiEdit) runs the repository's own prettier and eslint --fix on the edited file. Changes:
  • The repository is taken from the edited file, not the session cwd, so edits to a sibling repository are formatted too. Paths are compared via realpath, which handles Windows drive letters and 8.3 names.
  • It runs only in AR-js-org repositories.
  • It reports "not installed" only when package.json declares the tool. Repositories that don't use prettier get no noise.

Repository

• package.json (Vitest, Node ≥ 22.12 for the tests; the hooks use only Node built-ins) and CI on ubuntu and windows.
• Tests run with stub CLIs and git fixtures isolated from the runner's config: 48 tests.
• AGENTS.md. The guard's message points to it, and this repository is protected by the guard too.
• README: hooks table, "Use in a repository" (the extraKnownMarketplaces / enabledPlugins snippet), migration note, tests.
• release skill: the step 3 re-sync pushes origin dev explicitly.
• Plugin version 0.3.0.

Known limits

The guard is a guard-rail against mistakes. GitHub branch protection stays the enforcement. It lets through, by design: subshells, bash -c, git aliases, Pop-Location, -Path:"x", and a recorded main overwritten by a later failed switch. It blocks, fail-closed, a non-main switch followed by ; (use &&).

Migration

Project hooks and plugin hooks are not deduplicated. Each repository must drop .claude/hooks/ in the same PR that enables the plugin. Those PRs (artoolkit, AR.js-next, and threejs#6) follow this one.

Verification

• npm test: 48/48 on Windows. CI runs ubuntu and windows.
• claude plugin validate: passes.
• Scripted smoke test of the hooks.json commands against an AR-js-org repository and a foreign repository.
• Manual check with claude --plugin-dir ./plugins/arjs, in a throwaway clone of arjs-plugin-artoolkit on main with its own .claude/hooks removed:
  • /hooks lists [Plugin] Bash|PowerShell and [Plugin] Edit|Write|MultiEdit from arjs@inline, and no project hooks.
  • Bash git commit --allow-empty -m test on main is blocked with the plugin's message. git log shows no new commit.
  • PowerShell git add -A; if ($?) { git commit -m test } is blocked. git status shows nothing staged, because the whole call was refused.
  • git switch -c test/x && git commit --allow-empty -m test from main goes through, because the guard follows the switch.
  • Adding # Prova formatter to README.md ends up as # Prova formatter, with a blank line before it, from the repository's own prettier.
• Still to check after merge: the enabledPlugins route (trusted folder, no --plugin-dir).

🤖 Generated with Claude Code