Refresh README/CONTRIBUTING and add AGENTS.md - #1
Conversation
Clarify demo usage and agent conventions for contributors. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Warning Review limit reached
Next review available in: 1 minute Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 43dcc27eb6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ``` | ||
|
|
||
| Per-language loading behavior: | ||
| - **Node.js / TypeScript**: these samples import `dotenv/config` and read `.env` from the current working directory. |
There was a problem hiding this comment.
Load
.env in the TypeScript health sample
When a user sets a non-default NPI_API_BASE_URL only in typescript/.env and runs npx tsx health.ts as instructed, typescript/health.ts does not import dotenv/config, so it silently checks the default production host instead. Either add the import to that sample or exclude it from this loading claim.
Useful? React with 👍 / 👎.
| # AGENTS.md | ||
|
|
||
| ## Shared coding quality expectations | ||
| - Reference: [Personal coding heuristics](C:/git/personal-ai/memory/coding-heuristics.md) |
There was a problem hiding this comment.
Check in the heuristics required by AGENTS
In a fresh clone—or on any machine without the author's C:/git/personal-ai directory—the required heuristics cannot be opened, and a repo-wide search confirms that no copy is included here. Because the next line makes reading them a prerequisite to coding, contributors and agents cannot comply; use a repository-relative, committed document instead.
AGENTS.md reference: AGENTS.md:L4-L5
Useful? React with 👍 / 👎.
Co-authored-by: Cursor <cursoragent@cursor.com>
Summary
Test plan