refactor: 조망 지도를 합성 대상에서 제외 - #14
Conversation
|
Warning Review limit reached
Next review available in: 15 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
docs/maps/(조직 저장소 조망)가 각 저장소의CLAUDE.md·AGENTS.md에 전문 삽입되고 있었다. 개별 저장소에서 작업하는 에이전트에게 "조직에 어떤 repo가 있나"는 규약이 아니라 노이즈이고, 저장소 위생 규약의 정신과도 어긋난다.변경
rutter.yaml:docs.maps제거 → conventions만 합성 (지도 파일은 이 저장소에 그대로 유지, 삭제 아님)README.md: conventions=합성 대상 / maps=참조 지식(합성 안 함)임을 명시policies/core.yaml:maps.update-firstrule의 대상이 rutter 저장소임을 문구에 명확히 (모든 저장소에 내려가는 rule이므로 오해 방지)검증
pilot package lint통과 (PolicySet 2개 · rule 5개)pilot diff로 합성 결과 확인 —docs/conventions/*2개만 포함, "조직 저장소 조망" 사라짐배경
조망 지도는 "매번 주입되는 규약"이 아니라 필요할 때 찾아보는 참조 지식이라, 별도 방식으로 관리하는 게 맞다는 판단.
🤖 Generated with Claude Code