Uh oh!
There was an error while loading. Please reload this page.
feat: PR Creation Agent — Skill 3: validate-and-apply-labels (Complete) - #1981
Conversation
Warning Review limit reached
Next review available in:56 minutes Limit details: You’ve used all 1 included review currently available under your plan. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 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 |
✅ Template check passed after update. Thanks for fixing the PR description. |
❌ Branch Name Validation FailedThe branch name Required Format
Allowed Branch Types
Valid Examples
Invalid Examples
SolutionRename your branch to follow the pattern and update the PR. For more information, see docs/BRANCHING_STRATEGY.md. |
🔍 Reviewer Summary for PR #1981CI Status: ✅ Recommendations
|
…e Implementation) Complete implementation of label validation and application skill for PR Creation Agent Phase 3. - **validate-and-apply-labels.js** (~220 LOC): Validates and applies labels based on branch type and template context - **validate-and-apply-labels.test.js**: 33 tests, 100% passing, 97.5% code coverage - **Integration**: Works with Skill 1 (branchType) and Skill 2 (templateMetadata) - Label mapping for 30+ branch types (feat, fix, docs, hotfix, refactor, etc.) - Template context labels (meta:needs-more-info, meta:ready-for-review) - Canonical label validation with 30+ built-in labels - Custom configuration support for label mappings - WordPress-specific label support (wp:plugin, wp:theme, etc.) - Helpful warnings for bare type labels - 33 unit tests covering input validation, branch-to-label mapping, context labels, validation, custom config, WordPress labels, error handling, and integration - 97.5% statement coverage, 100% branch & function coverage - All 30+ branch types tested - Edge cases: empty metadata, special characters, very long labels - Phase 3: 3/6 skills complete (50%) - Skill 1 (validate-branch-name): ✅ 39 tests - Skill 2 (route-pr-template): ✅ 23 tests - Skill 3 (validate-and-apply-labels): ✅ 33 tests - Total: 95 tests, 97.88% coverage - Skills 4-6: Ready for implementation Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
49d9b87 to
b9cf6f2CompareUh oh!
There was an error while loading. Please reload this page.
Milestone Allocation |
Summary
Complete implementation of label validation and application skill for PR Creation Agent Phase 3.
Deliverables
Features
Test Coverage
Phase Progress
Integration Pipeline
Linked issues
Closes#1870
Changelog
Added
Changed
Checklist (Global DoD / PR)