Restore creating-skills content policies - #30
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 Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe PR adds durable repository-content policies, propagates English-artifact and Korean-runtime requirements through delegated skill creation, expands lifecycle acceptance criteria, and adds tests for policy wording and language verification. ChangesCreating-skills policy enforcement
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
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
`@plugins/skill-set/evals/creating-skills/new-with-creator/graders/lifecycle.md`:
- Line 6: The lifecycle contract in
plugins/skill-set/evals/creating-skills/new-with-creator/graders/lifecycle.md:6
must require English content for the positive and negative eval files and every
generated repository artifact, not only SKILL.md. Update the assertions in
plugins/skill-set/tests/test-authoring-skills.sh:127-132 to verify this
English-artifact requirement, or add an end-to-end fixture that checks artifact
language.
In `@plugins/skill-set/skills/creating-skills/reference/checklist.md`:
- Line 32: Update the language checklist item in the creating-skills reference
to require that all user-facing runtime outputs—including conversations,
reports, summaries, errors, warnings, status updates, prompts, and generated PR
comments—use the detected user language, while durable repository content
remains in English.
🪄 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
Run ID: 39cf1437-2c5c-4a37-b143-5014ddabdf65
📒 Files selected for processing (6)
plugins/skill-set/evals/creating-skills/new-with-creator/graders/lifecycle.mdplugins/skill-set/evals/creating-skills/new-with-creator/prompt.mdplugins/skill-set/skills/creating-skills/SKILL.mdplugins/skill-set/skills/creating-skills/reference/checklist.mdplugins/skill-set/skills/creating-skills/reference/structure.mdplugins/skill-set/tests/test-authoring-skills.sh
Record the merged base ancestry after PR #30 so the new pull request contains only the shipping-pr policy changes.
Summary
creating-skillsTests
plugins/skill-set/tests/test-authoring-skills.shplugins/skill-set/tests/run.shSummary by CodeRabbit
Documentation
Tests