@eventmodelers/cli 1.0.47 → 1.0.49

package/cli.js

@@ -927,10 +927,14 @@ async function installStack(stackKey, stackCfg, options = {}) {
         }
         try {
           execSync('git rev-parse --git-dir', { cwd: targetDir, stdio: 'ignore' });
-          execSync('git config core.hooksPath .githooks', { cwd: targetDir });
+          // core.hooksPath is resolved against the repo's actual top level, not `cwd` —
+          // a relative `.githooks` breaks silently (no error, hooks just don't run) when
+          // targetDir is a subfolder of a larger repo rather than the repo root itself.
+          // Use an absolute path so it's correct regardless of where the git root is.
+          execSync(`git config core.hooksPath "${join(targetDir, '.githooks')}"`, { cwd: targetDir });
           console.log('  ✓ Installed .githooks/ and set core.hooksPath — commits touching src/slices/ are now scope-guarded');
         } catch {
-          console.log('  ✓ Installed .githooks/ — run `git config core.hooksPath .githooks` once this directory is a git repo to activate it');
+          console.log(`  ✓ Installed .githooks/ — run \`git config core.hooksPath ${join(targetDir, '.githooks')}\` once this directory is a git repo to activate it`);
         }
       } else {
         console.log('  ℹ️  --hooks was given but this stack ships no .githooks/ template — nothing to install');
@@ -1704,6 +1708,7 @@ credentialFlags(program
   .description('Refresh an already-installed kit from the current CLI version — re-copies skills and the kit dir (.build-kit or .agent-modeling-kit) so you pick up script/skill updates after upgrading. Unlike `init`, never touches the project root scaffold or the root CLAUDE.md router, and leaves existing credentials alone unless --force is passed.')
   .option('--modeling', 'Refresh the modeling kit (.agent-modeling-kit) instead of a build kit')
   .option('--stack <name>', `Override which stack to refresh from (${Object.keys(REINITIABLE_STACKS).join(', ')}) instead of the one recorded in install-manifest.json — use this when the manifest is missing/stale, or to switch a .build-kit install to a different stack`)
+  .option('--hooks', 'Install the slice commit-scope guard (.githooks/pre-commit) and wire it up via `git config core.hooksPath .githooks` — same as `init --hooks`, for turning it on after the fact without a full re-scaffold. Off by default.')
   .option('--global', 'Re-install skills into ~/.claude/skills/ instead of the project — defaults to however they were originally installed')
   .option('-f, --force', 'Re-prompt for credentials even if a config already has everything required — overwrites the existing config.json'))
   .action(async (opts, command) => {
@@ -1745,6 +1750,7 @@ credentialFlags(program
       force: opts.force,
       credentialOverrides: credentialOverridesFromOpts(opts),
       skipRootScaffold: true,
+      hooks: opts.hooks,
     });
   });
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eventmodelers/cli",
-  "version": "1.0.47",
+  "version": "1.0.49",
   "description": "Eventmodelers CLI — real-time Claude agent + skills for Claude Code, for any stack (Node, Supabase, Axon, Cratis, OpenCQRS, UmaDB, Kurrent, or modeling-only)",
   "type": "module",
   "bin": {

package/stacks/node/templates/root/setup-env.sh

@@ -54,6 +54,9 @@ echo ".env created successfully."
 
 if [ -f .githooks/pre-commit ] && git rev-parse --git-dir >/dev/null 2>&1; then
   chmod +x .githooks/pre-commit 2>/dev/null || true
-  git config core.hooksPath .githooks
+  # core.hooksPath resolves against the repo's actual top level, not this directory —
+  # a relative ".githooks" silently breaks (no error, hooks just don't run) when this
+  # project sits in a subfolder of a larger repo instead of being the repo root itself.
+  git config core.hooksPath "$(pwd)/.githooks"
   echo "Configured git to use .githooks/ (slice commit-scope guard)."
 fi

package/stacks/supabase/templates/root/setup-env.sh

@@ -54,6 +54,9 @@ echo ".env created successfully."
 
 if [ -f .githooks/pre-commit ] && git rev-parse --git-dir >/dev/null 2>&1; then
   chmod +x .githooks/pre-commit 2>/dev/null || true
-  git config core.hooksPath .githooks
+  # core.hooksPath resolves against the repo's actual top level, not this directory —
+  # a relative ".githooks" silently breaks (no error, hooks just don't run) when this
+  # project sits in a subfolder of a larger repo instead of being the repo root itself.
+  git config core.hooksPath "$(pwd)/.githooks"
   echo "Configured git to use .githooks/ (slice commit-scope guard)."
 fi