Use it when your goal in software development and repositories is clear and you can limit it to the data and actions it actually needs.
github-pr-workflow
github-pr-workflow is a skill related to software development and repositories. It helps the agent understand code or work with a software project instead of only giving generic advice.
What does it add to Hermes?
github-pr-workflow is a skill related to software development and repositories. It helps the agent understand code or work with a software project instead of only giving generic advice.
The registry does not provide a sufficient English description, so we show only sourced metadata and do not infer undocumented capabilities.
Do not add it merely to experiment when Hermes already has a simpler path, or when you cannot review its source and permissions.
Best for users who want a repeatable way of working inside Hermes.
Try it on a disposable repository with read-only access and ask for a summary of one file with its path.
This entry was indexed from قائمة تحريرية موثقة المصدر. Our explanation interprets the type and domain without inventing a capability not present upstream.
Community data linked to its source. We have not tested it in your environment; follow the source and begin with a limited scope.
Inspect, install, then test.
- 01Open the source
Match the publisher, license, and description to your need. Check the real update history.
- 02Review permissions and secrets
Never paste a secret value into this site. Use environment-variable names and grant the smallest scope.
- 03Copy setup only after review
The controls below copy text. They do not execute commands on your device.
- 04Test with a non-sensitive task
Inspect the visible tools, then exclude write or delete tools you do not need.
Review the command, then copy it.
/github-pr-workflowHermes Belarabi does not execute this command. Installation happens on your device and remains subject to Hermes scanning and your review.