Skip to content

Docs: bundle Dynamic Workflows usage skill - #137

Open
donovan-yohan wants to merge 1 commit into
mainfrom
feat/bundled-usage-skill
Open

Docs: bundle Dynamic Workflows usage skill#137
donovan-yohan wants to merge 1 commit into
mainfrom
feat/bundled-usage-skill

Conversation

@donovan-yohan

Copy link
Copy Markdown
Owner

Summary

  • add a plugin-provided usage skill at hermes-dynamic-workflows:dynamic-workflows
  • register the bundled skill from the plugin entrypoint while keeping older ctx compatibility
  • update README/DESIGN/CHANGELOG so the script facade docs match the current scriptPath / resumeFromRunId schema

Verification

  • python3 -m compileall -q __init__.py src/hermes_workflows tests
  • uv run --with pytest pytest -q tests/test_plugin_registration.py tests/test_validate.py tests/test_run.py tests/test_catalog.py
  • plugin-skill discovery smoke: skill_view('hermes-dynamic-workflows:dynamic-workflows') returned success and registered skill list included dynamic-workflows
  • git diff --check

Notes

  • Full uv run --with pytest pytest -q was 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.

@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@donovan-yohan, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 9 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: dcfd3fac-52e8-4332-8af3-ca20383ab9a0

📥 Commits

Reviewing files that changed from the base of the PR and between a7255d8 and e54d043.

📒 Files selected for processing (6)
  • CHANGELOG.md
  • DESIGN.md
  • README.md
  • __init__.py
  • skills/dynamic-workflows/SKILL.md
  • tests/test_plugin_registration.py
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/bundled-usage-skill

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@gemini-code-assist

Copy link
Copy Markdown

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant