docs: add guideline to keep docs/attributes.md in sync with scorer changes#425
docs: add guideline to keep docs/attributes.md in sync with scorer changes#425jwm4 wants to merge 1 commit into
Conversation
…anges Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
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. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Enterprise Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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 |
📈 Test Coverage Report
Coverage calculated from unit tests only |
Summary
Adds a guideline to the Agent Guidelines section of CLAUDE.md requiring that
any change to how an assessor scores (thresholds, partial credit rules,
recognized paths, pass/fail conditions) is accompanied by a matching update
to docs/attributes.md in the same PR.
Motivation
PR #419 updated the partial-credit gate for
architecture_decisionsfrom anOR condition to an AND condition, but the corresponding docs/attributes.md
entry was not updated in the same commit — it had to be caught and fixed
separately. This guideline prevents that from happening again.
🤖 Generated with Claude Code under the supervision of Bill Murdock