Docs: bundle Dynamic Workflows usage skill - #137
Conversation
|
Warning Review limit reached
Next review available in: 9 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 (6)
✨ 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 |
|
Warning Gemini encountered an error creating the review. You can try again by commenting |
Summary
hermes-dynamic-workflows:dynamic-workflowsscriptPath/resumeFromRunIdschemaVerification
python3 -m compileall -q __init__.py src/hermes_workflows testsuv run --with pytest pytest -q tests/test_plugin_registration.py tests/test_validate.py tests/test_run.py tests/test_catalog.pyskill_view('hermes-dynamic-workflows:dynamic-workflows')returned success and registered skill list includeddynamic-workflowsgit diff --checkNotes
uv run --with pytest pytest -qwas also attempted; it hit existing timing/order-sensitive failures in background/Kanban/loop fixture tests unrelated to this docs/registration slice, while the touched registration tests and smoke checks pass.