docs: 저장소 위생(repo hygiene) 규약 추가 - #13
Conversation
|
Warning Review limit reached
Next review available in: 40 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 (1)
📝 WalkthroughWalkthroughAdds a Korean repository hygiene convention describing repository scope, excluded content, retained documentation, agent guidance files, and a contributor decision question. ChangesRepository hygiene
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@policies/core.yaml`:
- Around line 33-37: Scope the repo.hygiene rule to product repositories only by
moving it into a product-specific PolicySet or adding the supported per-rule
repository scope; ensure infrastructure and private operational repositories are
excluded while preserving the rule’s existing statement and rationale.
- Around line 33-37: Update the repo.hygiene policy entry to either add
supported path or pattern checks that enforce its repository-content
requirements, or explicitly mark/document the rule as advisory rather than
machine-enforced. Preserve the existing statement and rationale, and follow the
check/advisory conventions used by the other PolicySet entries.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: d8427d01-9391-4e77-96f7-473ac3d0e2b2
📒 Files selected for processing (2)
docs/conventions/repo-hygiene.mdpolicies/core.yaml
제품(대개 OSS) 저장소에 인프라·운영 도구나 AI 세션 잡음을 넣지 않도록 하는 조직 규약을 rutter에 추가한다. 각 repo에 손으로 쓰는 대신 rutter가 소스가 되어
pilot apply로 배포한다(DRY·dogfood).docs/conventions/repo-hygiene.md— 무엇을 빼고(ops 도구·세션 잡음) 무엇을 남기는지(CI·CLAUDE.md·ADR·Why). 설계 근거(Why)는 잡음이 아님을 명시policies/core.yaml— PolicySet rulerepo.hygiene(info) 추가pilot package lint통과 (PolicySet 2개 · rule 6개).🤖 Generated with Claude Code
Summary by CodeRabbit