docs: add cpp-linter to Used By, and restore a lost separator

[shenxianpeng]

Adds cpp-linter to the Used By row.

Two notes on it:

• The avatar is addressed by login (avatars.githubusercontent.com/cpp-linter)
  rather than by numeric id like the other nine. The numeric id is not
  reachable from this session, and the login form serves the same image
  (verified 200 image/png).
• I could not verify the usage itself from here — cpp-linter is outside this
  session's repository scope, so this rests on your own check, same as the
  rest of the row.

Also: a spacing bug that was already there

Extrawest was missing its trailing   , so it ran straight into
Chainlift with no gap:

... OpenCADC   Extrawest ExtrawestChainlift Chainlift   Mila ...

Every other entry has the separator; this one lost it. Only visible in the
rendered row, which is why it survived — the source lines look identical at a
glance.

Not changed

RLinf links to github.com/RLinf/RLinf (a repo) while all nine others link
to an org. The avatar is the org's, so this looks like an oversight — but it
is your curation and you may have pinned the specific repo deliberately, so I
left it. Say the word if it should point at the org.

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 45 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 2837b185-e4e9-4957-b25e-75403aa60bf0

📥 Commits

Reviewing files that changed from the base of the PR and between b78ea95 and 0f68d82.

📒 Files selected for processing (1)

• README.md

---

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

[github-actions]

Commit Check

✅ All 5 checks passed

Show all 5 checks

Commit message
  ✔ PR title (docs: add cpp-linter to Used By, and restore a lost separ...)
  ✔ Commit 1/1 (docs: add cpp-linter to Used By, and restore a lost separ...)
Branch
  ✔ Branch (claude/refresh-sample-output-602anc)
Author
  ✔ Author name (Xianpeng Shen)
  ✔ Author email (xianpeng.shen@gmail.com)

commit-check 2.13.1 · Rules reference