CodeVetter · Repo Unpack · Contributor handoff
oxc-project/oxc
Use the pinned implementation and nearest package guidance to choose a narrow edit boundary. Tests and CI were inspected, not executed, and the inventory remains bounded rather than exhaustive. Future verification should target the changed runtime surface before broad workspace checks. Generated outputs, formatter policy, and Rust-versus-Node feature differences are recurring traps.
- Start with the root and nearest package AGENTS.md; Oxfmt's guide identifies separate CLI, stdin, LSP, direct API, and textToDoc paths and warns against assuming shared behavior.
- Use manifests for version decisions: development Rust is 1.99.0, MSRV is 1.97.0, and the root package manager is pnpm 12.7.0.
- Edit generator inputs rather than generated artifacts: AST builder output names its generator, and linter registry output requires cargo lintgen; root guidance also requires lint-timings for linter codegen changes.
- For formatter changes, read the shared FORMATTER_POLICY through the crate guide, preserve text-in API boundaries, and keep comments, parentheses, and embedding responsibilities in their owning layer.
- Account for Oxfmt execution differences: the pure Rust CLI has no stdin/LSP support, the Node API uses caller-supplied options without config discovery, and native formatters do not fall back to Prettier.
- For later authorized checks, use focused Rust tests, filtered cargo coverage tasks, or package-specific pnpm build-test/test commands; this investigation inspected their definitions and CI wiring without executing them.
- Do not treat just fmt or just ready as harmless read-only checks: fmt invokes cargo shear --fix, while ready installs dependencies, regenerates code, formats files, and runs broad checks.
- Submission guidance requires AI-use disclosure and human responsibility for reviewed, understood, tested contributions; preserve this requirement when preparing an issue or PR.