Automation Blueprints
Automation Blueprints
Start with meaning, then move to detail.
This lesson explains Automation Blueprints as part of Hermes internals and extension points. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Development Workflow, Nightly Backlog Triage, Automatic PR Code Review, then verify failure modes and version compatibility.
Know Python, Git, and basic project structure before changing code.
A clear outcome before you read.
- Understand Automation Blueprints without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Approval & sandbox
- Approval pauses a sensitive action before execution; sandboxing limits impact if something goes wrong.
- Automation
- Running work later or repeatedly with explicit success and failure conditions.
Ready-to-use automation blueprints — scheduled tasks, GitHub event triggers, API webhooks, and multi-skill workflows
What does the source say, and in what order?
- 01Development Workflow
Start here to understand the core idea or structure.
- 02Nightly Backlog Triage
Read this after the foundation, then connect it to the previous step.
- 03Automatic PR Code Review
Read this after the foundation, then connect it to the previous step.
- 04Docs Drift Detection
Read this after the foundation, then connect it to the previous step.
- 05Dependency Security Audit
Read this after the foundation, then connect it to the previous step.
- 06DevOps & Monitoring
Read this after the foundation, then connect it to the previous step.
- 07Deploy Verification
Read this after the foundation, then connect it to the previous step.
- 08Alert Triage
Read this after the foundation, then connect it to the previous step.
- 09Uptime Monitor
Read this after the foundation, then connect it to the previous step.
- 10Research & Intelligence
Finish here to verify the result and special cases.
Copy only after you understand the effect.
hermes cron create "0 2 * * *" \
"You are a project manager triaging the NousResearch/hermes-agent GitHub repo.
1. Run: gh issue list --repo NousResearch/hermes-agent --state open --json number,title,labels,author,createdAt --limit 30
2. Identify issues opened in the last 24 hours
3. For each new issue:
- Suggest a priority label (P0-critical, P1-high, P2-medium, P3-low)
- Suggest a category label (bug, feature, docs, security)
- Write a one-line triage note
4. Summarize: total open issues, new today, breakdown by priority
Format as a clean digest. If no new issues, respond with [hermes webhook subscribe github-pr-review \
--events "pull_request" \
--prompt "Review this pull request:
Repository: {repository.full_name}
PR #{pull_request.number}: {pull_request.title}
Author: {pull_request.user.login}
Action: {action}
Diff URL: {pull_request.diff_url}
Fetch the diff with: curl -sL {pull_request.diff_url}
Review for:
- Security issues (injection, auth bypass, secrets in code)
- Performance concerns (N+1 queries, unbounded loops, memory leaks)
- Code quality (naming, duplication, error handling)
- Missing tests for new behavior
Post a concise review. If the PR is a tplatforms:
webhook:
enabled: true
extra:
port: 8644
secret: "your-global-secret"
routes:
github-pr-review:
events: ["pull_request"]
secret: "github-webhook-secret"
prompt: |
Review PR #{pull_request.number}: {pull_request.title}
Repository: {repository.full_name}
Author: {pull_request.user.login}
Diff URL: {pull_request.diff_url}
Review for security, performance, and code quality.
skills: ["github-code-review"]
deliver: "github_comment"
delRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.