CodeVetter · Repo Unpack · Contributor handoff
stylelint/stylelint
Start with the public API and the narrow rule or integration path being changed. Preserve configuration precedence, diagnostic locations, disable behavior, and the distinction between string output and file persistence. Tests and CI were inspected, not executed; future verification must report actual outcomes and respect the current read-only restriction.
- Read package.json and the npm lockfile before planning checks; npm test invokes pretest linting, then Jest and node:test, whereas test-only targets Jest with lifecycle scripts disabled.
- For runtime changes, begin with index, standalone, lintSource, and lintPostcssResult; preserve the callable PostCSS export and its explicit module.exports interoperability binding.
- Rule edits should remain standard-CSS focused and use validateOptions, syntax/type guards, and report; contributor guidance requires accepted/rejected cases and varied locations, including multiple warnings.
- Maintain .mjs/JSDoc conventions and strict no-emit checking; EditorConfig uses tabs generally and two-space indentation for package.json, Markdown, CSS, and YAML.
- Configuration edits require examining getConfigForFile and augmentConfig: cache keys include target paths, inheritance replaces whole rule settings, and overrides merge in matching order.
- Fix-related edits must cover string-input output, atomic file writes, disable ranges, and edit-information mutation; existing tests specify config-enabled fixes and disableFix behavior.
- When execution is authorized, the existing test-only script supports a narrow Jest test-file check before broader verification; npm test adds linting and node:test, while the Yarn PnP suite requires explicit enabling and performs packaging/install operations.
- This handoff records inspected test and CI specifications, not executed results; distinguish configured coverage thresholds and declared matrix jobs from observed passes, and do not treat snapshot system cases as exhaustive coverage.