chore: add format and lint to .md guides

[carderne]

follow on from #3977 #4056

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2618ce1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 41064c91-1557-42b5-ad14-1f4edae6e943

📥 Commits

Reviewing files that changed from the base of the PR and between 0026345 and 2618ce1.

📒 Files selected for processing (1)

• AGENTS.md

✅ Files skipped from review due to trivial changes (1)

• AGENTS.md

---

Walkthrough

Updated repository guidance in four docs. The changes replace generic linting references with oxfmt and oxlint, add a Code Style subsection with pnpm run format, pnpm run lint:fix, and pnpm run lint, and update the pull request checklist to require local formatting and lint fixes before pushing. The checklist also notes that the code-quality CI check enforces these rules.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description only references follow-on PRs and omits the required template sections, checklist, testing, changelog, and screenshots.	Fill in the full template: Closes # issue, checklist items, testing steps, changelog summary, and screenshots or N/A where applicable.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately summarizes the main change: adding formatting and linting guidance to markdown guides.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/format-lint-guidelines

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[devin-ai-integration]

Devin Review found 1 potential issue.

⚠️ 1 issue in files not directly in the diff

⚠️ Agent guidance file still references Prettier instead of oxfmt, contradicting all other updated docs (AGENTS.md:58)

The AGENTS.md file still tells agents that formatting is enforced using Prettier (AGENTS.md:58), while the updated CLAUDE.md, .claude/REVIEW.md, and CONTRIBUTING.md now all say oxfmt/oxlint — so agents following AGENTS.md will give wrong tooling advice.

Impact: Coding agents reading AGENTS.md will incorrectly believe Prettier is the formatter and may give users wrong instructions.

Incomplete documentation migration from Prettier to oxfmt

The PR's intent is a mechanical renaming of Prettier/ESLint → oxfmt/oxlint across documentation. The root package.json:21-23 confirms the actual tooling:

• "format": "oxfmt ."
• "lint": "oxlint"
• "lint:fix": "oxlint --fix"

But AGENTS.md:58 was not updated and still reads:

"Formatting is enforced using Prettier. Run pnpm run format before committing."

This creates contradictory guidance across the repo's special rule files.