feat: recognize bunx oxlint and versioned bunx tsc in single-file verification

[YuniorGlez]

Description

The Single-File Verification assessor missed the two commands Bun-based TypeScript projects actually document:

• bunx oxlint <file> — oxlint (oxc.rs, Rust-based linter) was not in the lint patterns at all.
• bunx tsc@7 --noEmit <file> — the existing tsc --noEmit <file> pattern requires the literal binary name; TypeScript 7 (the Go port) is invoked versioned as tsc@7 through bunx, so it never matched.

Type of Change

• New feature (non-breaking change which adds functionality)

Related Issues

No related issues (no existing Bun-support issue found; see sibling PRs #531, #532, #534).

Changes Made

• New lint pattern: (?:bunx\s+)?oxlint\s+<file>
• New typecheck pattern: (?:bunx\s+)?tsc@<version>\s+--noEmit\s+<file>
• Unit tests: bunx oxlint recognition, versioned bunx tsc recognition, and full score when both are documented.

Testing

• Unit tests pass (pytest) — 21 passed (verification suite), 178 total
• Manual testing performed — verified against a real Bun repo (Next.js base template, single-file 30/100 → 100/100)
• No new warnings or errors — ruff clean

Checklist

• My code follows the project's code style
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published

Additional Notes

TypeScript 7 (native Go port) is distributed as tsc@7 via bunx/npx, so versioned invocations are the standard form in current TS7 projects.

[coderabbitai]

Warning

Review limit reached

@YuniorGlez, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 500e5c8a-348d-4d0c-bcf6-7d0542ec696d

📥 Commits

Reviewing files that changed from the base of the PR and between 3f4c01b and 3c35eb1.

📒 Files selected for processing (2)

• src/agentready/assessors/verification.py
• tests/unit/test_assessors_verification.py

---

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.}

[jwm4]

Thanks for the PR! The two new patterns work correctly. I verified that the unit tests really do test them: if you remove either pattern, its test fails, which is exactly what we want. I also checked the patterns against real CLAUDE.md files from GitHub that mention oxlint, and none of them match incorrectly.

A few things need to happen before I can merge:

1. Rebase onto the latest main. Another PR recently added more tools to the same pattern lists you edited, so your branch now has a merge conflict. The conflict is easy to resolve: keep both your new patterns and the recently added ones.

2. Run black . and commit the result. That is why CI is failing. The formatter wants to rewrap both of the files you changed.

3. Add your new tools to the documentation. The file docs/attributes.md has a "Single-File Verification" section that lists every command the assessor recognizes. Please add oxlint and the versioned tsc form to that list. In this repo, docs and assessor changes are expected to land in the same PR.

4. Cover tsc@latest too. Your version pattern only matches numeric versions like tsc@7 or tsc@5.6. People also write bunx tsc@latest --noEmit file.ts or tsc@next, and those won't match. Changing \d+(?:\.\d+)* to something like [\w.-]+ after the @ covers all of them.

5. Optional: drop the (?:bunx\s+)? prefix. It has no effect. The regex search is not anchored to the start of the line, so the pattern already matches oxlint file.ts wherever it appears, including right after bunx. None of the other patterns in the list mention runners like npx or bunx for the same reason. Removing it keeps things consistent, but it does no harm if you prefer to keep it.

This comment is from Bill Murdock, written with assistance from Claude Code.