[codex] add agent operating rules#39
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s contributor/agent guidance by adding a concise “Agent Operating Rules” section to AGENTS.md, while keeping the existing scraper workflow, parsing, and validation guidance intact.
Changes:
- Add a new “Agent Operating Rules” section covering scope control, convention matching, deterministic vs. LLM-appropriate tasks, and verification expectations.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - Tests should encode intent, not just exercise code paths. A test is weak if it | ||
| would keep passing after the relevant scraper behavior or business rule is | ||
| broken. | ||
| - Fail loud. Do not report success if records, tests, browser steps, payloads, or |
Summary
Validation