docs(claude): improve /tackle-pr-comment reference scheme#304
Conversation
Uses letters (A, B, C) for feedback items and numbers (1, 2, 3) for implementation steps to avoid confusion when discussing specific items in scratchpads. Previously, mixing "Step X" and "item Y" references caused confusion when discussing feedback. Now "Feedback B" clearly refers to analysis items while "Step 2" refers to implementation steps. Changes: - Letters for feedback items, numbers for implementation steps - Explicit ACCEPT/IGNORE decision with reason for each feedback item - Steps list which feedback items they address (can be multiple) - Clear flow: ACCEPT → Implementation Plan, IGNORE → commit message's "Ignored Feedback" Benefits: - Unambiguous references when discussing specific items - Every feedback item has explicit disposition and clear destination - Traceability from reviewer feedback through to implementation or commit message
|
Warning Rate limit exceeded
⌛ 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 |
Uses letters (A, B, C) for feedback items and numbers (1, 2, 3) for implementation steps to avoid confusion when discussing specific items in scratchpads.
Previously, mixing "Step X" and "item Y" references caused confusion when discussing feedback. Now "Feedback B" clearly refers to analysis items while "Step 2" refers to implementation steps.
Changes:
Benefits: