feat: accept multiple file paths as positional arguments

[skoshx]

Summary

Fixes #1744

Allows the CLI to accept multiple file paths as positional arguments, enabling CI systems to pass pre-computed changed-file lists directly instead of forcing react-doctor to re-derive them via --scope files --base.

Changes

• Changed CLI argument from [directory] to [paths...] to accept variadic arguments
• When multiple paths are provided, they're normalized to repo-relative paths and passed through the same code path as --changed-files-from
• Maintains full backward compatibility:
  • 0 arguments → scans current directory .
  • 1 argument → scans that directory (existing behavior)
  • N arguments (N > 1) → scans those specific files
• Added path normalization to handle both relative and absolute paths
• Updated help examples to show the new usage
• Added unit tests and e2e tests

Usage

# Scan specific files (new)
react-doctor src/a.tsx src/b.tsx

# Scan current directory (backward compatible)
react-doctor

# Scan specific directory (backward compatible)  
react-doctor ./apps/web

Testing

• All existing tests pass
• Added 3 new unit tests for the different argument cases
• Added e2e tests to verify the feature works correctly
• Manual testing confirms:
  • Multiple files are scanned correctly
  • Only specified files are scanned (others ignored)
  • Both relative and absolute paths work
  • Backward compatibility maintained

Scope

This is a CLI-only change that doesn't affect the diagnostic engine. The diagnostics produced are identical to using --changed-files-from - we're just adding a more ergonomic way to specify the file list directly on the command line.

  

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/eslint-plugin-react-doctor@1745

npm i https://pkg.pr.new/oxlint-plugin-react-doctor@1745

npm i https://pkg.pr.new/react-doctor@1745

commit: f23352e

[github-actions]

React Doctor found no new issues. 🎉

_{Reviewed by React Doctor for commit f23352e.}

[github-actions]

Interactive terminal E2E

Terminal Control verified the built CLI at f23352e in a real PTY:

• selected a project interactively and observed Scanning... before the three-second Git delay completed
• waited for the clean result and exercised the compact report
• opened copy context and the GitHub Actions confirmation, then cancelled safely

Download the edited MP4 and PNG evidence