@produck/agent-toolkit 0.6.0 → 0.8.0

package/publish-assets/instructions/produck/10-produck-node.instructions.md

@@ -19,15 +19,19 @@ applyTo: '**'
 
 Required script keys:
 
-- `deps:install`
+- `produck:install`
 - `test`
 - `produck:coverage`
-- `lint`
+- `produck:lint`
 - `publish`
 
 Notes:
 
 - Script key names are fixed and must match exactly.
+- Keep the script key name `produck:install` (organization-reserved key).
+- The required value for `produck:install` is governed by
+  `agent-toolkit sync-install`; see the Monorepo mode section below for the
+  canonical value.
 - `publish` may be a no-op when repository-specific release workflow does not
   use npm publishing.
 - Coverage governance policy:
@@ -37,19 +41,18 @@ Notes:
     baseline.
   - Source of truth for tooling versions/template:
     `.github/distribution/produck/tooling-version-baseline.json`.
+  - Use central remediation command to deploy root install script baseline:
+    `npm exec -- agent-toolkit sync-install --cwd .`.
   - Use central remediation command to deploy coverage scripts:
-    `npm exec -- agent-toolkit sync-coverage-script --cwd .`.
+    `npm exec -- agent-toolkit sync-coverage --cwd .`.
   - Use central remediation command to deploy local anti-drift hook baseline:
-    `npm exec -- agent-toolkit sync-husky-hooks --cwd .`.
+    `npm exec -- agent-toolkit sync-git --cwd .`.
   - Use central remediation command to deploy root format script/config
     baseline:
-    `npm exec -- agent-toolkit sync-prettier-config --cwd .`.
+    `npm exec -- agent-toolkit sync-format --cwd .`.
   - Use central remediation command to deploy root lint script/config and
     eslint integration baseline:
-    `npm exec -- agent-toolkit sync-eslint-config --cwd .`.
-  - Use central remediation command to deploy root shared scripts/dependencies
-    baseline:
-    `npm exec -- agent-toolkit sync-workspace-config --cwd .`.
+    `npm exec -- agent-toolkit sync-lint --cwd .`.
   - `c8` execution baseline for deployed coverage scripts is fixed to the
     version specified in `tooling-version-baseline.json`.
   - Downstream repositories must not use unversioned `npx c8` or `c8@latest`
@@ -57,15 +60,15 @@ Notes:
   - Root local governance must pin `devDependencies.c8`,
     `devDependencies.husky`, `devDependencies.lerna`, and
     `devDependencies.@produck/agent-toolkit` via
-    `agent-toolkit sync-workspace-config`.
+    `agent-toolkit sync-git`.
   - Root local governance must pin `devDependencies.@produck/eslint-rules`
-    via `agent-toolkit sync-eslint-config`.
+    via `agent-toolkit sync-lint`.
 
 - Testing strategy and framework are repository-defined.
 - `verify` scripts are optional repository-local health checks and are not
   organization-required script keys.
 - `verify` is not part of organization commit gates; style gates remain
-  repository `format:check` and `lint` policy.
+  repository `produck:format` and `produck:lint` policy.
 - `test` script implementation is repository-defined and is not overwritten by
   organization coverage remediation.
 - Repositories should keep `npm run test` and `npm run produck:coverage`
@@ -73,7 +76,7 @@ Notes:
 - For intermediate commits, temporary non-executable state or failing tests are
   allowed.
 - Commit prechecks still require passing repository style gates (for example
-  `format:check` and `lint`).
+  `produck:format` and `produck:lint`).
 
 Central toolkit command role model:
 
@@ -83,19 +86,20 @@ Central toolkit command role model:
   but do not assume it can fully prevent AI hallucination or iterative drift.
 - `agent-toolkit preflight` is the hard guard for organization engineering
   baseline and is mandatory for required baseline checks.
-- `agent-toolkit sync-coverage-script` is the hard guard for monorepo coverage
+- `agent-toolkit sync-install` is the hard guard for root install script
+  governance and is mandatory in monorepo mode.
+- `agent-toolkit sync-coverage` is the hard guard for monorepo coverage
   governance and is mandatory in monorepo mode.
-- `agent-toolkit sync-husky-hooks` is the hard guard for local anti-drift hook
+- `agent-toolkit sync-git` is the hard guard for local anti-drift hook
   governance and is mandatory in monorepo mode.
-- `agent-toolkit sync-prettier-config` is the hard guard for root format
+- `agent-toolkit sync-format` is the hard guard for root format
   script/config governance and is mandatory in monorepo mode.
-- `agent-toolkit sync-eslint-config` is the hard guard for root lint
+- `agent-toolkit sync-lint` is the hard guard for root lint
   script/config and eslint integration governance and is mandatory in monorepo
   mode.
-- `agent-toolkit sync-workspace-config` is the hard guard for root shared
-  scripts/dependencies governance and is mandatory in monorepo mode.
-- For simplified downstream execution of mandatory flow (1 -> 2 -> 3 -> 4 ->
-  5 -> 6 -> 7),
+- `agent-toolkit sync-publish` is the hard guard for root publish script
+  governance when `lerna.json` is present.
+- For simplified downstream execution of mandatory flow (1 -> 2 -> ... -> 9),
   use:
   `npm exec -- agent-toolkit`.
 - Equivalent explicit form:
@@ -112,62 +116,30 @@ Central toolkit command role model:
   interpreter workflows for parsing/filtering over brittle OS-shell pipelines.
 - For human engineers, `run-capture` and `summarize-log` are optional helpers.
 
-Test authoring baseline (required):
-
-- Prefer Node.js standard library test runner (`node:test`) with `describe` and
-  `it`.
-- Each test case must be independently executable.
-- Test cases must not depend on execution order or state from other cases.
-- New test debugging should use local `only` mode for scoped regression.
-- After debugging, remove all `only` markers before final validation.
+Test authoring baseline:
 
-Recommended local debug flow:
-
-1. Add `{ only: true }` to the target `describe/it` and all ancestor
-   `describe` blocks.
-2. Run `node --test --test-only test/index.mjs`.
-3. Remove all `only` markers.
-4. Run full regression via repository standard test command.
+- See [Test Authoring Baseline](12-produck-test.instructions.md) for the full
+  test writing, structure, debug, and coverage workflow rules.
 
 Script and output directory policy:
 
-- Reusable project scripts should be committed under root `scripts/`.
-- Organization-level shared tooling may use a central npm package bridge instead
-  of repository-local `scripts/` duplication.
-- Runtime command outputs should be written under root `logs/` (or a documented
-  equivalent) and ignored by git.
-- Temporary debug scripts should not be committed.
-- `.github/` should not be used as a temporary script workspace.
+- Follow script/output placement and lifecycle policy from
+  `00-produck-base.instructions.md`.
+- For monorepo shared configuration and root workspace practices, follow
+  `15-produck-workspace.instructions.md`.
 
 Required ignore baseline:
 
 - Each Node.js repository must include a root `.gitignore`.
-- The root `.gitignore` must start from the GitHub default template for Node.js
-  projects (`Node.gitignore` from github/gitignore).
-- Team-specific ignore conventions should be appended on top of that baseline
-  template, not used as a replacement.
-- The root `.gitignore` should at minimum ignore:
-  - `node_modules/`
-  - `coverage/`
-  - `.env`
-  - `.env.*`
-  - npm logs (for example `npm-debug.log*`)
-  - OS/editor noise (for example `.DS_Store`, `Thumbs.db`, `.vscode/` when
-    workspace settings are not intended to be shared)
+- Baseline template and required minimum entries follow
+  `00-produck-base.instructions.md`.
+- Monorepo centralization policy and workspace-specific ignore guidance follow
+  `15-produck-workspace.instructions.md`.
 
 Team conventions for `.gitignore`:
 
-- Keep organization-wide additions grouped under a dedicated comment block for
-  easy updates.
-- Do not remove baseline entries from the GitHub template unless repository
-  owners document a justified exception.
-- Organization-approved team extension entries are:
-  - `*.ign*` (manually created local directories/files that should not be
-    committed)
-  - `*.gen*` (generated artifacts created by program execution, for example
-    during tests)
-- Append these team entries under a dedicated team block at the end of the root
-  `.gitignore`.
+- Team extension entries and placement rules follow
+  `00-produck-base.instructions.md`.
 
 ## Monorepo mode
 
@@ -178,42 +150,46 @@ Repository layout:
 
 Script placement:
 
-- Root `package.json` must provide `deps:install`, `test`, `produck:coverage`,
-  and `lint` orchestration scripts.
-- Root `package.json` must reserve `produck:precommit-check` for organization
+- Root `package.json` must provide `produck:install`, `test`, `produck:coverage`,
+  and `produck:lint` orchestration scripts.
+- Root `package.json` must reserve `produck:commit:check` for organization
   anti-drift gate with required value:
   `npm run produck:format && npm run produck:lint`.
 - Root `package.json` must reserve `prepare` for husky setup with required
   value: `husky`.
 - Root `package.json` must reserve `produck:format` and `produck:lint` for
   organization-controlled format/lint gates.
+- Root `package.json` must reserve `produck:publish` for organization-controlled
+  publish gate when `lerna.json` is present (governed by
+  `agent-toolkit sync-publish`).
 - `publish` may be defined at root or package level based on release workflow.
 - Workspace subpackage `produck:coverage` scripts must be synchronized by
-  `agent-toolkit sync-coverage-script`.
+  `agent-toolkit sync-coverage`.
 - Root local hook governance must be synchronized by
-  `agent-toolkit sync-husky-hooks`.
+  `agent-toolkit sync-git`.
+- Root local shared script governance must initialize
+  `scripts.produck:install` with required value `npm -v && npm install`
+  via `agent-toolkit sync-install`.
 - Root local format governance must be synchronized by
-  `agent-toolkit sync-prettier-config`.
+  `agent-toolkit sync-format`.
 - Root local lint governance must be synchronized by
-  `agent-toolkit sync-eslint-config`.
-- Root local shared script/dependency governance must be synchronized by
-  `agent-toolkit sync-workspace-config`.
+  `agent-toolkit sync-lint`.
 - Root local shared script/dependency governance must pin root
   `devDependencies.c8`,
   `devDependencies.husky`, `devDependencies.lerna`,
   `devDependencies.@produck/agent-toolkit` via
-  `agent-toolkit sync-workspace-config`.
+  `agent-toolkit sync-git`.
 - Root local shared script/dependency governance must initialize
   `scripts.produck:coverage` with workspace-level execution behavior:
   attempt `test` on all workspace packages using `--workspaces --if-present`.
 - Root local shared script/dependency governance must initialize `.c8rc.json`
-  via `agent-toolkit sync-workspace-config`.
+  via `agent-toolkit sync-coverage`.
 - Root local format governance must initialize `.prettierrc` and
-  `scripts.produck:format` via `agent-toolkit sync-prettier-config`.
+  `scripts.produck:format` via `agent-toolkit sync-format`.
 - Root local lint governance must initialize `eslint.config.mjs`,
   `scripts.produck:lint`, and `devDependencies.@produck/eslint-rules`
   (including append-mode integration for existing eslint config) via
-  `agent-toolkit sync-eslint-config`.
+  `agent-toolkit sync-lint`.
 - Root `package.json` must define a `produck:baseline` script for organization
   baseline enforcement:
   ```json
@@ -240,7 +216,8 @@ Root workspace `package.json` minimal baseline (required):
 
 - `private`: `true`
 - `workspaces` (explicit package path list only)
-- `scripts` with at least: `deps:install`, `test`, `produck:coverage`, `lint`
+- `scripts` with at least: `produck:install`, `test`, `produck:coverage`,
+  `produck:lint`
 - `publish` script is optional at root when release is managed per package or
   by external workflow.
 
@@ -276,8 +253,8 @@ Repository layout:
 
 Script placement:
 
-- The repository root `package.json` must define `deps:install`, `test`,
-  `produck:coverage`, `lint`, and `publish`.
+- The repository root `package.json` must define `produck:install`, `test`,
+  `produck:coverage`, `produck:lint`, and `publish`.
 - Root `package.json` must define a `produck:baseline` script for organization
   baseline enforcement:
   ```json

package/publish-assets/instructions/produck/12-produck-test.instructions.md

@@ -0,0 +1,94 @@
+---
+applyTo: '**'
+---
+
+<!-- managed-by: @produck/agent-toolkit -->
+<!-- source: .github/distribution/produck/12-produck-test.instructions.md -->
+
+# Test Authoring Baseline
+
+## Scope
+
+- Applies to Node.js repositories in the organization.
+- This document governs how tests are authored, structured, and executed.
+- Repository-specific rules may add stricter requirements; they override this
+  baseline when they conflict.
+
+## Framework
+
+- MUST use Node.js standard library test runner (`node:test`) with `describe`
+  and `it`.
+- Do not introduce a third-party test framework unless repository owners
+  explicitly document the justification.
+
+## File structure
+
+- Each package must have a dedicated test directory: `test/`.
+- Tests are organized in individual files per subject area under `test/`.
+- Each package MUST provide a single entrypoint file: `test/index.mjs`.
+- The entrypoint imports all test files to be executed.
+
+Example entrypoint:
+
+```js
+import './feature-a.test.mjs';
+import './feature-b.test.mjs';
+```
+
+## Single Entrypoint Rule (required)
+
+- Execution MUST always go through the entrypoint file.
+- Command-line execution MUST NOT use the `--test` flag. Use
+  `node <entrypoint>` directly.
+- Correct: `node test/index.mjs`
+- Wrong: `node --test` or `node --test test/feature-a.test.mjs`
+- All tooling (scripts, CI, coverage) must target the entrypoint only.
+
+## Test case rules
+
+- Each test case must be independently executable.
+- Test cases must not depend on execution order or shared mutable state from
+  other cases.
+- Avoid global side effects that persist across test cases.
+- Clean up resources (temp files, open handles) at the end of each test case.
+
+## Naming conventions
+
+- Test files use the `.test.mjs` suffix.
+- Top-level `describe` label should match the subject being tested (for example
+  the module name or command name).
+- `it` labels should describe the expected behavior in plain language.
+
+## Local debug workflow (recommended)
+
+When debugging a failing test case:
+
+1. Add `{ only: true }` to the target `it` and all ancestor `describe` blocks.
+2. Run `node --test-only test/index.mjs`.
+3. Verify the issue is isolated.
+4. Remove all `only` markers.
+5. Run full regression: `node test/index.mjs`.
+
+Rules for `only` mode:
+
+- `--test-name-pattern` does NOT match tests nested inside `describe()` blocks
+  — it may silently run zero tests. Do not use it for focused runs.
+- Always remove `only` markers before committing.
+- Never commit a test file with `{ only: true }` present.
+
+## Coverage
+
+- Coverage is governed by `produck:coverage` script and `c8`.
+- Scoped coverage (for partial branch verification during development):
+  `npm exec -- c8 --reporter=lcov --reporter=html --reporter=text-summary node --test-only test/index.mjs`
+- Before merge or release, run full coverage via `npm run produck:coverage`.
+- See [Node.js Baseline](10-produck-node.instructions.md) for coverage script
+  governance details.
+
+## Regression discipline
+
+- Before merge or release: restore executable test commands and fix all failing
+  tests.
+- Temporary non-executable state or failing tests are allowed for intermediate
+  commits.
+- Full regression MUST pass before a release commit is made.

package/publish-assets/instructions/produck/15-produck-workspace.instructions.md

@@ -11,13 +11,6 @@ applyTo: '**'
 
 The Produck monorepo provides unified configuration across all packages for consistency and ease of maintenance.
 
-## Distribution classification
-
-This document is maintained directly as a downstream-distributable source.
-
-- Authoritative path:
-  `.github/distribution/produck/15-produck-workspace.instructions.md`
-
 ## Shared Configurations
 
 ### 1. ESLint Configuration (`eslint.config.mjs`)
@@ -137,56 +130,30 @@ export default [
 # Type check all packages (optional: only when root tsconfig.json is present)
 npm run type-check
 
-# Format check without writing
-npm run format:check
-
-# Format and write
-npm run format
+# Format and write using the organization format gate
+npm run produck:format
 
-# Lint (requires root eslint.config.mjs)
-npm run lint
+# Lint using the organization lint gate
+npm run produck:lint
 
 # Run all package tests
 npm run test
 
 # Check coverage across packages
-npm run coverage
+npm run produck:coverage
 ```
 
 ### Release & Coverage Tooling
 
-- Monorepo release workflow is `lerna`-based and required.
-- Source of truth for `lerna`/`c8` versions and coverage script template:
+- Release and coverage governance follows
+  `10-produck-node.instructions.md`.
+- Source of truth for version pinning and script templates remains
   `.github/distribution/produck/tooling-version-baseline.json`.
-- `lerna` execution version is governed at organization level, not per
-  repository.
-- Required execution baseline: version specified in `tooling-version-baseline.json`.
-- Required `lerna` invocation:
-  `npm exec -- lerna <subcommand>`.
-- Shared scripts/CI must not use unversioned `npx lerna` or `lerna@latest`.
-- Wrapper scripts are allowed, but should keep parity with organization version
-  policy.
-- Workspace subpackage coverage scripts are fully organization-governed.
-- Deploy/repair coverage scripts via central remediation command:
-  `npm exec -- agent-toolkit sync-coverage-script --cwd .`.
-- Root anti-drift local hook baseline is organization-governed.
-- Deploy/repair root local hooks via central remediation command:
-  `npm exec -- agent-toolkit sync-husky-hooks --cwd .`.
-- Deployed coverage scripts use the `c8` version specified in
-  `tooling-version-baseline.json` for each governed workspace package.
-- Deployed local hook baseline uses the `husky` version specified in
-  `tooling-version-baseline.json` for root `devDependencies.husky`.
-- Deployed local hook baseline also pins root
-  `devDependencies.@produck/agent-toolkit` to the fixed version managed by the organization baseline.
-- Shared scripts/CI must not use unversioned `npx c8` or `c8@latest`.
-- `test` script implementation remains repository-defined and is not overwritten
-  by coverage remediation.
-- Root `devDependencies.c8` is pinned at root by `agent-toolkit sync-husky-hooks`;
-  workspace package `devDependencies.c8` is pinned per package by
-  `agent-toolkit sync-coverage-script`.
-- Root local hooks may be bypassed intentionally by developers (for example via
-  `--no-verify`) and are treated as local strong guardrails rather than
-  immutable release gates.
+- For monorepo remediation, use:
+  - `npm exec -- agent-toolkit sync-coverage --cwd .`
+  - `npm exec -- agent-toolkit sync-git --cwd .`
+- Keep workspace wrappers and local scripts consistent with Node baseline
+  execution policy.
 
 ## Package Integration
 
@@ -264,14 +231,14 @@ Root scripts are designed for CI pipelines:
 
 ```bash
 # Pre-commit checks
-npm run format:check
+npm run produck:format
+npm run produck:lint
 # Optional when root tsconfig.json is used
 npm run type-check
-npm run lint
 
 # Testing
 npm run test
-npm run coverage
+npm run produck:coverage
 ```
 
 ## Best Practices
@@ -297,7 +264,7 @@ npm install
 Root `.prettierrc` and `eslint.config.mjs` are synchronized. If conflict occurs:
 
 1. Check both configs have matching rules
-2. Run `npm run format` first, then `npm run lint`
+2. Run `npm run produck:format` first, then `npm run produck:lint`
 
 ### TypeScript includes too many files (when root tsconfig.json is used)
 

package/publish-assets/instructions/produck/20-produck-commit.instructions.md

@@ -175,8 +175,8 @@ Use the local validator before commit:
 Commit precheck gate (AI-agent required, human recommended):
 
 - For AI-agent-authored operations, complete repository style gates before both
-  `git commit` and `git commit --amend` (for example `format:check` and
-  `lint`).
+  `git commit` and `git commit --amend` (for example `produck:format` and
+  `produck:lint`).
 - For AI-agent-authored operations, `git commit --no-verify` and
   `git commit --amend --no-verify` are forbidden.
 - For human engineer-authored operations, style gates are recommended baseline

package/publish-assets/instructions/produck/tooling-version-baseline.json

@@ -16,17 +16,29 @@
       "version": "9.0.7",
       "policy": "pinned",
       "allowLatest": false
+    },
+    "prettier": {
+      "version": "3.8.3",
+      "policy": "pinned",
+      "allowLatest": false
+    },
+    "@produck/eslint-rules": {
+      "version": "0.3.5",
+      "policy": "pinned",
+      "allowLatest": false
     }
   },
   "coverage": {
-    "scriptTemplate": "c8@{c8.version} --reporter=lcov --reporter=html --reporter=text-summary npm test"
+    "scriptTemplate": "c8 --reporter=lcov --reporter=html --reporter=text-summary npm test"
   },
   "enforce": {
     "sharedScriptsDisallow": [
       "npx c8",
       "c8@latest",
       "npx lerna",
-      "lerna@latest"
+      "lerna@latest",
+      "npx prettier",
+      "prettier@latest"
     ]
   }
 }

package/publish-assets/prettierignore

@@ -0,0 +1,2 @@
+CHANGELOG.md
+package-lock.json

package/bin/command/sync-husky-hooks/help.txt

@@ -1,14 +0,0 @@
-Usage:
-  agent-toolkit sync-husky-hooks [--cwd <dir>] [--check] [--dry-run]
-    [--json <file>]
-
-Behavior:
-  - Applies organization-required hook files only:
-    - .husky/pre-commit
-    - .husky/commit-msg
-  - commit-msg hook validates message via local node_modules toolkit path
-
-Rules:
-  - --check validates without writing and exits non-zero on mismatch
-  - --dry-run prints planned changes without writing
-  - --check takes precedence over --dry-run

package/bin/command/sync-husky-hooks/index.mjs

@@ -1,89 +0,0 @@
-import fs from 'node:fs';
-import path from 'node:path';
-import { fileURLToPath } from 'node:url';
-
-import { getSingle, hasFlag } from '../shared/args.mjs';
-import { printTextResource } from '../shared/text-resource.mjs';
-
-const COMMAND_DIR = path.dirname(fileURLToPath(import.meta.url));
-const HELP_FILE = path.resolve(COMMAND_DIR, 'help.txt');
-
-const REQUIRED_PRE_COMMIT_HOOK = '#!/usr/bin/env sh\nnpm run produck:precommit-check\n';
-const REQUIRED_COMMIT_MSG_HOOK =
-  '#!/usr/bin/env sh\nnode ./node_modules/@produck/agent-toolkit/bin/agent-toolkit.mjs validate-commit-msg --file "$1"\n';
-
-export function printSyncHuskyHooksHelp() {
-  printTextResource(HELP_FILE);
-}
-
-function readFileIfExists(filePath) {
-  if (!fs.existsSync(filePath)) {
-    return null;
-  }
-
-  return fs.readFileSync(filePath, 'utf8');
-}
-
-export function runSyncHuskyHooks(options) {
-  const cwd = path.resolve(getSingle(options, '--cwd', process.cwd()));
-  const check = hasFlag(options, '--check');
-  const dryRun = hasFlag(options, '--dry-run') && !check;
-  const jsonFile = getSingle(options, '--json', '');
-  const mode = check ? 'check' : dryRun ? 'dry-run' : 'sync';
-
-  if (!fs.existsSync(cwd)) {
-    console.error(`CWD does not exist: ${cwd}`);
-    process.exit(2);
-  }
-
-  const huskyDir = path.resolve(cwd, '.husky');
-  const preCommitHookPath = path.resolve(huskyDir, 'pre-commit');
-  const commitMsgHookPath = path.resolve(huskyDir, 'commit-msg');
-
-  const previousPreCommitHook = readFileIfExists(preCommitHookPath);
-  const previousCommitMsgHook = readFileIfExists(commitMsgHookPath);
-
-  const matchesRequiredPreCommitHook = previousPreCommitHook === REQUIRED_PRE_COMMIT_HOOK;
-  const matchesRequiredCommitMsgHook = previousCommitMsgHook === REQUIRED_COMMIT_MSG_HOOK;
-  const requiresUpdate = !matchesRequiredPreCommitHook || !matchesRequiredCommitMsgHook;
-
-  if (mode === 'sync' && requiresUpdate) {
-    fs.mkdirSync(huskyDir, { recursive: true });
-    fs.writeFileSync(preCommitHookPath, REQUIRED_PRE_COMMIT_HOOK, 'utf8');
-    fs.writeFileSync(commitMsgHookPath, REQUIRED_COMMIT_MSG_HOOK, 'utf8');
-  }
-
-  const report = {
-    cwd,
-    mode,
-    ok: true,
-    required: {
-      preCommitHookPath: path.relative(cwd, preCommitHookPath),
-      commitMsgHookPath: path.relative(cwd, commitMsgHookPath),
-    },
-    status: {
-      matchesRequiredPreCommitHookBefore: matchesRequiredPreCommitHook,
-      matchesRequiredCommitMsgHookBefore: matchesRequiredCommitMsgHook,
-      matchesRequiredPreCommitHookAfter:
-        requiresUpdate && mode === 'sync' ? true : matchesRequiredPreCommitHook,
-      matchesRequiredCommitMsgHookAfter:
-        requiresUpdate && mode === 'sync' ? true : matchesRequiredCommitMsgHook,
-      updated: requiresUpdate && mode === 'sync',
-    },
-  };
-
-  if (mode === 'check' && requiresUpdate) {
-    report.ok = false;
-  }
-
-  if (jsonFile) {
-    const outPath = path.resolve(cwd, jsonFile);
-    fs.mkdirSync(path.dirname(outPath), { recursive: true });
-    fs.writeFileSync(outPath, `${JSON.stringify(report, null, 2)}\n`, 'utf8');
-  }
-
-  process.stdout.write(`${JSON.stringify(report, null, 2)}\n`);
-  if (!report.ok) {
-    process.exit(2);
-  }
-}