Task summary
The suggest command validates --max-diff-size and exits with "Invalid --max-diff-size value. Expected a positive integer." when given invalid input, but there is no test covering non-numeric, zero, or negative values.
Why this is a good first issue
The error message and validation logic already exist. The task is writing one CLI test that asserts exit code and stderr output — a good intro to the project's node:test patterns.
Suggested files or areas
src/commands/suggest.ts — validation logic (line ~146)
tests/empty-repo-suggest.test.mjs — pattern to follow
tests/e2e/suggest-smoke.test.mjs — has a valid --max-diff-size case for reference
Acceptance criteria
Extra context
tests/config-store.test.mjs already tests invalid maxDiffSize values at the config layer; this issue covers the CLI flag path specifically.
Task summary
The
suggestcommand validates--max-diff-sizeand exits with "Invalid --max-diff-size value. Expected a positive integer." when given invalid input, but there is no test covering non-numeric, zero, or negative values.Why this is a good first issue
The error message and validation logic already exist. The task is writing one CLI test that asserts exit code and stderr output — a good intro to the project's
node:testpatterns.Suggested files or areas
src/commands/suggest.ts— validation logic (line ~146)tests/empty-repo-suggest.test.mjs— pattern to followtests/e2e/suggest-smoke.test.mjs— has a valid--max-diff-sizecase for referenceAcceptance criteria
0,-1, orabc)npm testpassesExtra context
tests/config-store.test.mjsalready tests invalidmaxDiffSizevalues at the config layer; this issue covers the CLI flag path specifically.