• Validate --cwd directory exists before execution
• Throw CliError with exit code 1 for non-existent directories
• Add three test cases covering both flag variants and valid paths

Add --cwd directory existence validation

• Import fs module from node:fs
• Add validation check after flag normalization in main function
• Throw CliError with descriptive message if --cwd directory doesn't exist
• Error is logged to console before throwing to ensure user sees the message

@commitlint/cli/src/cli.ts

Add tests for --cwd directory validation

• Add test for --cwd with non-existent directory (expects exit code 1 and error message)
• Add test for -d alias with non-existent directory (same behavior as --cwd)
• Add test for --cwd with valid existing directory (expects successful execution)

@commitlint/cli/src/cli.test.ts

Description

The new validation in main() only checks fs.existsSync(flags.cwd), so an existing file path passes
even though --cwd is documented as a directory. Subsequent git operations use nodeOptions.cwd and
can fail with a non-CliError, causing the CLI to throw (stack trace/uncontrolled exit) instead of
exiting cleanly with ExitCode.CommitlintErrorDefault.

Code

@commitlint/cli/src/cli.ts[R214-221]

+	if (!fs.existsSync(flags.cwd)) {
+		const err = new CliError(
+			`The specified --cwd directory "${flags.cwd}" does not exist.`,
+			pkg.name,
+		);
+		console.error(err.message);
+		throw err;
+	}

Evidence

--cwd is explicitly documented as a directory, but the new check only validates existence, not that
the path is a directory. The cwd value is passed into git execution via tinyexec (nodeOptions.cwd),
and non-CliError failures are rethrown by the CLI top-level handler rather than converted to a
controlled exit code, so a file-path cwd can still crash the process.

@commitlint/cli/src/cli.ts[60-66]
@commitlint/cli/src/cli.ts[214-221]
@commitlint/read/src/read.ts[30-35]
@commitlint/cli/src/cli.ts[170-176]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`--cwd` is documented as a directory, but current validation only checks `existsSync`, so existing *files* pass and later git operations can fail with a non-`CliError` (uncontrolled throw/stack trace).

### Issue Context
`main(cli.argv).catch(...)` only converts `CliError` (matching `pkg.name`) into a controlled exit; other errors are rethrown.

### Fix Focus Areas
- @commitlint/cli/src/cli.ts[214-221]
- @commitlint/cli/src/cli.ts[170-176]
- @commitlint/cli/src/cli.test.ts[41-66]

### Implementation notes
- Replace `existsSync` check with a `try { statSync(flags.cwd) }` guard and verify `.isDirectory()`.
- If stat fails or `.isDirectory()` is false, throw `new CliError(...)` with a message like: `The specified --cwd path "..." must be an existing directory.`
- Add a unit test that creates/uses an existing file in a fixture (e.g., `path.join(cwd, 'commitlint.config.js' or 'package.json')`) and asserts stderr contains the message and exit code is `ExitCode.CommitlintErrorDefault`.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools