[Fix] Two-pass review provenance 및 정형 자격요건 필터 보강 - #223
Conversation
- Candidate Review decision을 sanitized analysis candidateId 기준으로 검증 - Review strength를 sanitized strength quote 기반으로 제한 - Review missingKeyword를 sanitized keyword/source 기반으로 제한 - 입력 후보 없는 review 출력 제거 및 provenance WARN 로그 추가 - 사회복지사·청소년상담사 등 정형 자격요건 누락 키워드 제외 보강 - Spring Boot·포토샵 등 실무 역량은 정형 자격요건으로 오인하지 않도록 테스트 추가 - Candidate Generation 프롬프트에 도구·실무·문제 해결 기반 strength recall 규칙 추가 - EV-02, EV-15 유형 positive strength 예시 추가
|
Warning Review limit reached
Next review available in: 16 minutes 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: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
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 |
✨ 어떤 이유로 PR를 하셨나요?
📋 세부 내용 - 왜 해당 PR이 필요한지 작업 내용을 자세하게 설명해주세요
📸 작업 화면 스크린샷
🚨 관련 이슈 번호 [#150 ]