docs: mention changesets in rule validation

[rayhanadev]

Why

Make the rule validation skill remind agents to create a changeset when a rule change affects published packages.

This keeps validation, PR prep, and release notes aligned so user-facing rule work does not skip the versioning step.

Before:

rule-validate verifies noise, correctness, PR copy, and review feedback.

After:

rule-validate verifies noise, correctness, changesets, PR copy, and review feedback.

What changed

• Added changeset generation to the rule-validate skill description and pipeline summary.
• Documents when to run nr changeset, which packages to select, and when patch is appropriate.
• Adds changeset path or skip reason to the validation output template.

Test plan

• Not run; docs-only skill update.

Eval results

RDE was not run; this only updates agent guidance and does not change a React Doctor rule implementation.

Changeset

Skipped; docs-only skill update with no published package behavior change.

Made with Cursor

---

Note

Low Risk
Docs-only skill guidance plus a cosmetic progress-message string change; no rule logic, auth, or release behavior changes.

Overview
Extends the rule-validate agent skill so validation explicitly covers changesets before PR copy: when to run nr changeset, package selection, default patch bumps for user-facing rule work, skip rules for docs-only work, and a changeset path or skip reason in the validation output template.

Also updates the lint scan progress line in run-inspect from Scanning (n/m)... to Scanning files (n/m)... for clearer CLI feedback during file scans.

^{Reviewed by Cursor Bugbot for commit e7f7163. Bugbot is set up for automated code reviews on this repo. Configure here.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.