@phuc1403/musketeer 0.9.0 → 0.11.0

package/template/.claude/hooks/init-adr-dir.cjs

@@ -1,173 +1,173 @@
-#!/usr/bin/env node
-// PreToolUse guard: set up `.adr-dir` before the first `adr new` in a project,
-// so the agent never has to pick between `adr init` and a hand-written file.
-//
-// Two setup paths, and picking the wrong one is destructive:
-//   - fresh (no `.adr-dir`, no numbered ADRs yet): `adr init docs/adr` is safe —
-//     it creates docs/adr/, writes `.adr-dir`, and adds a baseline ADR.
-//   - migration (numbered ADRs already exist, but no `.adr-dir`): `adr init`
-//     would ALSO add that baseline ADR, burning the next real number. The fix
-//     is a plain `.adr-dir` file with no tool call.
-// Already initialized: nothing to do, both paths are a no-op.
-//
-// Also makes sure this skill's ADR template is the one `adr new` picks up, by
-// placing it at `<adr-dir>/templates/template.md` — the third step of the tool's
-// own template resolution, and the reason no env var has to be injected.
-//
-// Runs the setup itself (as a side effect) before allowing `adr new` through,
-// and denies a *direct* `adr init` call whenever running it would be wrong —
-// already initialized, or migration state — since either would burn a number.
-// Anything it does is echoed to stdout so it stays visible in the transcript.
-
-const fs = require('fs');
-const path = require('path');
-const { spawnSync } = require('child_process');
-const { invokesAdr } = require('./lib/adr/command-scan.cjs');
-
-const root = process.env.CLAUDE_PROJECT_DIR || process.cwd();
-const ADR_DIR = 'docs/adr';
-const ADR_DIR_FILE = path.join(root, '.adr-dir');
-const ADR_FILE = /^\d+-.*\.md$/;
-const SKILL_TEMPLATE = path.join(
-  root,
-  '.claude',
-  'skills',
-  'adr-writer',
-  'references',
-  'adr-template.md'
-);
-
-function allow(message) {
-  if (message) process.stdout.write(message + '\n');
-  process.exit(0);
-}
-
-function deny(reason) {
-  process.stdout.write(
-    JSON.stringify({
-      hookSpecificOutput: {
-        hookEventName: 'PreToolUse',
-        permissionDecision: 'deny',
-        permissionDecisionReason: reason,
-      },
-    })
-  );
-  process.exit(0);
-}
-
-function readAdrDir() {
-  try {
-    return fs.readFileSync(ADR_DIR_FILE, 'utf8').trim() || null;
-  } catch {
-    return null;
-  }
-}
-
-function isInitialized() {
-  return readAdrDir() !== null;
-}
-
-function hasNumberedAdrs() {
-  try {
-    return fs.readdirSync(path.join(root, ADR_DIR)).some((f) => ADR_FILE.test(f));
-  } catch {
-    return false; // directory doesn't exist yet -> nothing to migrate
-  }
-}
-
-function runAdrInit() {
-  // `adr` is an npm bin — a real executable on every platform, so it is called
-  // directly rather than through a shell script interpreter. `shell: true` is
-  // here only because npm installs it as `adr.cmd` on Windows, which
-  // CreateProcess cannot launch on its own; every argument is a constant, so
-  // there is nothing for a shell to interpolate.
-  return spawnSync('adr', ['init', ADR_DIR], { cwd: root, shell: true, encoding: 'utf8' });
-}
-
-// `adr init` writes `.adr-dir` with `path.relative`, so on Windows it lands as
-// `docs\adr` with no trailing newline. That file is committed and read on every
-// other machine, where a backslash is an ordinary filename character and not a
-// separator. Rewrite it in the portable form the rest of this toolchain emits.
-function normalizeAdrDirFile() {
-  const declared = readAdrDir();
-  if (!declared) return;
-  fs.writeFileSync(ADR_DIR_FILE, `${declared.split(path.sep).join('/')}\n`);
-}
-
-// The tool resolves its template as: explicit argument, then $ADR_TEMPLATE, then
-// `<adr-dir>/templates/template.md`, then its own bundled default. Copying this
-// skill's template into the third slot means a bare `adr new` produces a
-// musketeer ADR with no environment set up for it.
-//
-// Only ever writes when the file is absent, so a project that has customised its
-// own template keeps it.
-function ensureTemplate() {
-  try {
-    const dir = readAdrDir() || ADR_DIR;
-    const target = path.join(root, dir, 'templates', 'template.md');
-    if (fs.existsSync(target) || !fs.existsSync(SKILL_TEMPLATE)) return null;
-    fs.mkdirSync(path.dirname(target), { recursive: true });
-    fs.copyFileSync(SKILL_TEMPLATE, target);
-    return `Installed the adr-writer template at ${dir}/templates/template.md.`;
-  } catch {
-    return null; // never block an ADR over the template copy
-  }
-}
-
-function main() {
-  const payload = JSON.parse(fs.readFileSync(0, 'utf8'));
-  const command = payload?.tool_input?.command || '';
-  const isInit = invokesAdr(command, 'init');
-  const isNew = invokesAdr(command, 'new');
-  if (!isInit && !isNew) return allow();
-
-  if (isInitialized()) {
-    if (isInit) {
-      return deny(
-        '.adr-dir already exists — do not run `adr init` again, it would add a duplicate ' +
-          'baseline ADR and burn the next number. Run `adr new` directly.'
-      );
-    }
-    return allow(ensureTemplate()); // adr new, already set up: nothing else to do
-  }
-
-  if (hasNumberedAdrs()) {
-    // Migration: numbered ADRs exist but `.adr-dir` does not. `adr init` would
-    // still add a baseline ADR here, so it is never the right command.
-    if (isInit) {
-      return deny(
-        'Numbered ADRs already exist without `.adr-dir` — this is a migration, not a fresh ' +
-          'project. `adr init` would add a duplicate baseline ADR and burn the next number. ' +
-          'Run `adr new` directly; `.adr-dir` is set up automatically.'
-      );
-    }
-    fs.writeFileSync(ADR_DIR_FILE, `${ADR_DIR}\n`);
-    const note = ensureTemplate();
-    return allow(
-      `Migration detected: wrote .adr-dir (${ADR_DIR}) by hand, no baseline ADR added.` +
-        (note ? `\n${note}` : '')
-    );
-  }
-
-  // Fresh project.
-  if (isInit) return allow(); // the agent's own `adr init` call is correct here — let it run
-  const res = runAdrInit();
-  if (res.error || res.status !== 0) {
-    return allow(
-      `Could not run \`adr init ${ADR_DIR}\` (${res.error?.message || res.stderr}); ` +
-        'letting the original command run and fail with its own error.'
-    );
-  }
-  normalizeAdrDirFile();
-  const note = ensureTemplate();
-  return allow(
-    `Fresh project: ran \`adr init ${ADR_DIR}\` (creates the baseline ADR).` +
-      (note ? `\n${note}` : '')
-  );
-}
-
-try {
-  main();
-} catch {
-  allow(); // fail open
-}
+#!/usr/bin/env node
+// PreToolUse guard: set up `.adr-dir` before the first `adr new` in a project,
+// so the agent never has to pick between `adr init` and a hand-written file.
+//
+// Two setup paths, and picking the wrong one is destructive:
+//   - fresh (no `.adr-dir`, no numbered ADRs yet): `adr init docs/adr` is safe —
+//     it creates docs/adr/, writes `.adr-dir`, and adds a baseline ADR.
+//   - migration (numbered ADRs already exist, but no `.adr-dir`): `adr init`
+//     would ALSO add that baseline ADR, burning the next real number. The fix
+//     is a plain `.adr-dir` file with no tool call.
+// Already initialized: nothing to do, both paths are a no-op.
+//
+// Also makes sure this skill's ADR template is the one `adr new` picks up, by
+// placing it at `<adr-dir>/templates/template.md` — the third step of the tool's
+// own template resolution, and the reason no env var has to be injected.
+//
+// Runs the setup itself (as a side effect) before allowing `adr new` through,
+// and denies a *direct* `adr init` call whenever running it would be wrong —
+// already initialized, or migration state — since either would burn a number.
+// Anything it does is echoed to stdout so it stays visible in the transcript.
+
+const fs = require('fs');
+const path = require('path');
+const { spawnSync } = require('child_process');
+const { invokesAdr } = require('./lib/adr/command-scan.cjs');
+
+const root = process.env.CLAUDE_PROJECT_DIR || process.cwd();
+const ADR_DIR = 'docs/adr';
+const ADR_DIR_FILE = path.join(root, '.adr-dir');
+const ADR_FILE = /^\d+-.*\.md$/;
+const SKILL_TEMPLATE = path.join(
+  root,
+  '.claude',
+  'skills',
+  'adr-writer',
+  'references',
+  'adr-template.md'
+);
+
+function allow(message) {
+  if (message) process.stdout.write(message + '\n');
+  process.exit(0);
+}
+
+function deny(reason) {
+  process.stdout.write(
+    JSON.stringify({
+      hookSpecificOutput: {
+        hookEventName: 'PreToolUse',
+        permissionDecision: 'deny',
+        permissionDecisionReason: reason,
+      },
+    })
+  );
+  process.exit(0);
+}
+
+function readAdrDir() {
+  try {
+    return fs.readFileSync(ADR_DIR_FILE, 'utf8').trim() || null;
+  } catch {
+    return null;
+  }
+}
+
+function isInitialized() {
+  return readAdrDir() !== null;
+}
+
+function hasNumberedAdrs() {
+  try {
+    return fs.readdirSync(path.join(root, ADR_DIR)).some((f) => ADR_FILE.test(f));
+  } catch {
+    return false; // directory doesn't exist yet -> nothing to migrate
+  }
+}
+
+function runAdrInit() {
+  // `adr` is an npm bin — a real executable on every platform, so it is called
+  // directly rather than through a shell script interpreter. `shell: true` is
+  // here only because npm installs it as `adr.cmd` on Windows, which
+  // CreateProcess cannot launch on its own; every argument is a constant, so
+  // there is nothing for a shell to interpolate.
+  return spawnSync('adr', ['init', ADR_DIR], { cwd: root, shell: true, encoding: 'utf8' });
+}
+
+// `adr init` writes `.adr-dir` with `path.relative`, so on Windows it lands as
+// `docs\adr` with no trailing newline. That file is committed and read on every
+// other machine, where a backslash is an ordinary filename character and not a
+// separator. Rewrite it in the portable form the rest of this toolchain emits.
+function normalizeAdrDirFile() {
+  const declared = readAdrDir();
+  if (!declared) return;
+  fs.writeFileSync(ADR_DIR_FILE, `${declared.split(path.sep).join('/')}\n`);
+}
+
+// The tool resolves its template as: explicit argument, then $ADR_TEMPLATE, then
+// `<adr-dir>/templates/template.md`, then its own bundled default. Copying this
+// skill's template into the third slot means a bare `adr new` produces a
+// musketeer ADR with no environment set up for it.
+//
+// Only ever writes when the file is absent, so a project that has customised its
+// own template keeps it.
+function ensureTemplate() {
+  try {
+    const dir = readAdrDir() || ADR_DIR;
+    const target = path.join(root, dir, 'templates', 'template.md');
+    if (fs.existsSync(target) || !fs.existsSync(SKILL_TEMPLATE)) return null;
+    fs.mkdirSync(path.dirname(target), { recursive: true });
+    fs.copyFileSync(SKILL_TEMPLATE, target);
+    return `Installed the adr-writer template at ${dir}/templates/template.md.`;
+  } catch {
+    return null; // never block an ADR over the template copy
+  }
+}
+
+function main() {
+  const payload = JSON.parse(fs.readFileSync(0, 'utf8'));
+  const command = payload?.tool_input?.command || '';
+  const isInit = invokesAdr(command, 'init');
+  const isNew = invokesAdr(command, 'new');
+  if (!isInit && !isNew) return allow();
+
+  if (isInitialized()) {
+    if (isInit) {
+      return deny(
+        '.adr-dir already exists — do not run `adr init` again, it would add a duplicate ' +
+          'baseline ADR and burn the next number. Run `adr new` directly.'
+      );
+    }
+    return allow(ensureTemplate()); // adr new, already set up: nothing else to do
+  }
+
+  if (hasNumberedAdrs()) {
+    // Migration: numbered ADRs exist but `.adr-dir` does not. `adr init` would
+    // still add a baseline ADR here, so it is never the right command.
+    if (isInit) {
+      return deny(
+        'Numbered ADRs already exist without `.adr-dir` — this is a migration, not a fresh ' +
+          'project. `adr init` would add a duplicate baseline ADR and burn the next number. ' +
+          'Run `adr new` directly; `.adr-dir` is set up automatically.'
+      );
+    }
+    fs.writeFileSync(ADR_DIR_FILE, `${ADR_DIR}\n`);
+    const note = ensureTemplate();
+    return allow(
+      `Migration detected: wrote .adr-dir (${ADR_DIR}) by hand, no baseline ADR added.` +
+        (note ? `\n${note}` : '')
+    );
+  }
+
+  // Fresh project.
+  if (isInit) return allow(); // the agent's own `adr init` call is correct here — let it run
+  const res = runAdrInit();
+  if (res.error || res.status !== 0) {
+    return allow(
+      `Could not run \`adr init ${ADR_DIR}\` (${res.error?.message || res.stderr}); ` +
+        'letting the original command run and fail with its own error.'
+    );
+  }
+  normalizeAdrDirFile();
+  const note = ensureTemplate();
+  return allow(
+    `Fresh project: ran \`adr init ${ADR_DIR}\` (creates the baseline ADR).` +
+      (note ? `\n${note}` : '')
+  );
+}
+
+try {
+  main();
+} catch {
+  allow(); // fail open
+}

package/template/.claude/hooks/inject-adr-flags.cjs

@@ -1,94 +1,94 @@
-#!/usr/bin/env node
-// PreToolUse guard: add the one flag every `adr new` call needs, so the agent
-// can write a bare `adr new -- "Title"` and still get a safe command.
-//
-//   -q / --quiet — without it, an `-s` pattern matching more than one file
-//     opens an interactive prompt on stdin and hangs the session. With it,
-//     the ambiguous case throws instead, so the wrong ADR is never superseded
-//     by a silent guess.
-//
-// Nothing else is injected. The template no longer needs an env var: `adr`
-// resolves `<adr-dir>/templates/template.md` on its own, and init-adr-dir.cjs
-// puts musketeer's template there. There is no editor to suppress either —
-// `adr` only opens one on an explicit `--open`.
-//
-// Uses PreToolUse's `updatedInput` (not just allow/deny) to rewrite the
-// command before it runs. A `-q` the agent already wrote is left alone, and
-// the call is a silent no-op.
-//
-// Safety: a title that happens to contain the literal text "adr new" could
-// make the matching regex fire inside a quoted string. Guarded by counting
-// quote characters before each match — an odd count means "inside an open
-// string", and that occurrence is left untouched rather than risk corrupting
-// the title.
-
-const fs = require('fs');
-const {
-  invocationRe,
-  isInsideQuotes,
-  isInsideHeredoc,
-  invokesAdr,
-} = require('./lib/adr/command-scan.cjs');
-
-const QUIET = /(?:^|\s)(?:-q|--quiet)(?=\s|$)/;
-
-// Everything between `adr new` and either the `--` option terminator or the end
-// of this command segment, whichever comes first.
-//
-// The title lives after `--` and may legitimately contain the text "-q"
-// ("Use -q for quiet builds"). Scanning it would make the hook believe the flag
-// was already supplied and skip an invocation that genuinely needs it, so the
-// title is never part of the region searched.
-function flagsRegion(command, from) {
-  const rest = command.slice(from);
-  let end = rest.length;
-
-  const terminator = rest.search(/\s--(\s|$)/);
-  if (terminator !== -1) end = terminator;
-
-  for (let i = 0; i < end; i++) {
-    if (';&|\n'.includes(rest[i]) && !isInsideQuotes(command, from + i)) {
-      end = i;
-      break;
-    }
-  }
-  return rest.slice(0, end);
-}
-
-function main() {
-  const payload = JSON.parse(fs.readFileSync(0, 'utf8'));
-  const command = payload?.tool_input?.command || '';
-  if (!invokesAdr(command, 'new')) return;
-
-  let changed = false;
-  const updated = command.replace(invocationRe('new'), (whole, boundary, ws, envPrefix, adrNew, offset) => {
-    // Both guards, for the same reason the deny hooks use them: a heredoc body
-    // is documentation being written, and injecting a flag into it would
-    // rewrite the file's contents rather than the command.
-    // `offset` is the boundary character; step past it to the word `adr`.
-    const at = offset + boundary.length + ws.length + envPrefix.length;
-    if (isInsideQuotes(command, at) || isInsideHeredoc(command, at)) return whole;
-    if (QUIET.test(flagsRegion(command, at + adrNew.length))) return whole;
-    changed = true;
-    return `${boundary}${ws}${envPrefix}${adrNew} -q`;
-  });
-  if (!changed) return;
-
-  process.stdout.write(
-    JSON.stringify({
-      systemMessage: 'Added -q to `adr new` — without it an ambiguous -s prompts on stdin and hangs.',
-      hookSpecificOutput: {
-        hookEventName: 'PreToolUse',
-        permissionDecision: 'allow',
-        updatedInput: { command: updated },
-      },
-    })
-  );
-}
-
-try {
-  main();
-} catch {
-  /* fail open: leave the command untouched */
-}
-process.exit(0);
+#!/usr/bin/env node
+// PreToolUse guard: add the one flag every `adr new` call needs, so the agent
+// can write a bare `adr new -- "Title"` and still get a safe command.
+//
+//   -q / --quiet — without it, an `-s` pattern matching more than one file
+//     opens an interactive prompt on stdin and hangs the session. With it,
+//     the ambiguous case throws instead, so the wrong ADR is never superseded
+//     by a silent guess.
+//
+// Nothing else is injected. The template no longer needs an env var: `adr`
+// resolves `<adr-dir>/templates/template.md` on its own, and init-adr-dir.cjs
+// puts musketeer's template there. There is no editor to suppress either —
+// `adr` only opens one on an explicit `--open`.
+//
+// Uses PreToolUse's `updatedInput` (not just allow/deny) to rewrite the
+// command before it runs. A `-q` the agent already wrote is left alone, and
+// the call is a silent no-op.
+//
+// Safety: a title that happens to contain the literal text "adr new" could
+// make the matching regex fire inside a quoted string. Guarded by counting
+// quote characters before each match — an odd count means "inside an open
+// string", and that occurrence is left untouched rather than risk corrupting
+// the title.
+
+const fs = require('fs');
+const {
+  invocationRe,
+  isInsideQuotes,
+  isInsideHeredoc,
+  invokesAdr,
+} = require('./lib/adr/command-scan.cjs');
+
+const QUIET = /(?:^|\s)(?:-q|--quiet)(?=\s|$)/;
+
+// Everything between `adr new` and either the `--` option terminator or the end
+// of this command segment, whichever comes first.
+//
+// The title lives after `--` and may legitimately contain the text "-q"
+// ("Use -q for quiet builds"). Scanning it would make the hook believe the flag
+// was already supplied and skip an invocation that genuinely needs it, so the
+// title is never part of the region searched.
+function flagsRegion(command, from) {
+  const rest = command.slice(from);
+  let end = rest.length;
+
+  const terminator = rest.search(/\s--(\s|$)/);
+  if (terminator !== -1) end = terminator;
+
+  for (let i = 0; i < end; i++) {
+    if (';&|\n'.includes(rest[i]) && !isInsideQuotes(command, from + i)) {
+      end = i;
+      break;
+    }
+  }
+  return rest.slice(0, end);
+}
+
+function main() {
+  const payload = JSON.parse(fs.readFileSync(0, 'utf8'));
+  const command = payload?.tool_input?.command || '';
+  if (!invokesAdr(command, 'new')) return;
+
+  let changed = false;
+  const updated = command.replace(invocationRe('new'), (whole, boundary, ws, envPrefix, adrNew, offset) => {
+    // Both guards, for the same reason the deny hooks use them: a heredoc body
+    // is documentation being written, and injecting a flag into it would
+    // rewrite the file's contents rather than the command.
+    // `offset` is the boundary character; step past it to the word `adr`.
+    const at = offset + boundary.length + ws.length + envPrefix.length;
+    if (isInsideQuotes(command, at) || isInsideHeredoc(command, at)) return whole;
+    if (QUIET.test(flagsRegion(command, at + adrNew.length))) return whole;
+    changed = true;
+    return `${boundary}${ws}${envPrefix}${adrNew} -q`;
+  });
+  if (!changed) return;
+
+  process.stdout.write(
+    JSON.stringify({
+      systemMessage: 'Added -q to `adr new` — without it an ambiguous -s prompts on stdin and hangs.',
+      hookSpecificOutput: {
+        hookEventName: 'PreToolUse',
+        permissionDecision: 'allow',
+        updatedInput: { command: updated },
+      },
+    })
+  );
+}
+
+try {
+  main();
+} catch {
+  /* fail open: leave the command untouched */
+}
+process.exit(0);