better-dsh 0.2.5-c → 0.2.5-e

package/docs/80_upstream-docs-and-skills/hermes-dev-skill/src/docs/guides/webhook-github-pr-review.md

@@ -1,336 +0,0 @@
----
-sidebar_position: 11
-sidebar_label: "GitHub PR Reviews via Webhook"
-title: "Automated GitHub PR Comments with Webhooks"
-description: "Connect Hermes to GitHub so it automatically fetches PR diffs, reviews code changes, and posts comments — triggered by webhooks with no manual prompting"
----
-
-# Automated GitHub PR Comments with Webhooks
-
-This guide walks you through connecting Hermes Agent to GitHub so it automatically fetches a pull request's diff, analyzes the code changes, and posts a comment — triggered by a webhook event with no manual prompting.
-
-When a PR is opened or updated, GitHub sends a webhook POST to your Hermes instance. Hermes runs the agent with a prompt that instructs it to retrieve the diff via the `gh` CLI, and the response is posted back to the PR thread.
-
-:::tip Want a simpler setup without a public endpoint?
-If you don't have a public URL or just want to get started quickly, check out [Build a GitHub PR Review Agent](./github-pr-review-agent.md) — uses cron jobs to poll for PRs on a schedule, works behind NAT and firewalls.
-:::
-
-:::info Reference docs
-For the full webhook platform reference (all config options, delivery types, dynamic subscriptions, security model) see [Webhooks](/user-guide/messaging/webhooks).
-:::
-
-:::warning Prompt injection risk
-Webhook payloads contain attacker-controlled data — PR titles, commit messages, and descriptions can contain malicious instructions. When your webhook endpoint is exposed to the internet, run the gateway in a sandboxed environment (Docker, SSH backend). See the [security section](#security-notes) below.
-:::
-
----
-
-## Prerequisites
-
-- Hermes Agent installed and running (`hermes gateway`)
-- [`gh` CLI](https://cli.github.com/) installed and authenticated on the gateway host (`gh auth login`)
-- A publicly reachable URL for your Hermes instance (see [Local testing with ngrok](#local-testing-with-ngrok) if running locally)
-- Admin access to the GitHub repository (required to manage webhooks)
-
----
-
-## Step 1 — Enable the webhook platform
-
-Add the following to your `~/.hermes/config.yaml`:
-
-```yaml
-platforms:
-  webhook:
-    enabled: true
-    extra:
-      port: 8644          # default; change if another service occupies this port
-      rate_limit: 30      # max requests per minute per route (not a global cap)
-
-      routes:
-        github-pr-review:
-          secret: "your-webhook-secret-here"   # must match the GitHub webhook secret exactly
-          events:
-            - pull_request
-
-          # The agent is instructed to fetch the actual diff before reviewing.
-          # {number} and {repository.full_name} are resolved from the GitHub payload.
-          prompt: |
-            A pull request event was received (action: {action}).
-
-            PR #{number}: {pull_request.title}
-            Author: {pull_request.user.login}
-            Branch: {pull_request.head.ref} → {pull_request.base.ref}
-            Description: {pull_request.body}
-            URL: {pull_request.html_url}
-
-            If the action is "closed" or "labeled", stop here and do not post a comment.
-
-            Otherwise:
-            1. Run: gh pr diff {number} --repo {repository.full_name}
-            2. Review the code changes for correctness, security issues, and clarity.
-            3. Write a concise, actionable review comment and post it.
-
-          deliver: github_comment
-          deliver_extra:
-            repo: "{repository.full_name}"
-            pr_number: "{number}"
-```
-
-**Key fields:**
-
-| Field | Description |
-|---|---|
-| `secret` (route-level) | HMAC secret for this route. Falls back to `extra.secret` global if omitted. |
-| `events` | List of `X-GitHub-Event` header values to accept. Empty list = accept all. |
-| `prompt` | Template; `{field}` and `{nested.field}` resolve from the GitHub payload. |
-| `deliver` | `github_comment` posts via `gh pr comment`. `log` just writes to the gateway log. |
-| `deliver_extra.repo` | Resolves to e.g. `org/repo` from the payload. |
-| `deliver_extra.pr_number` | Resolves to the PR number from the payload. |
-
-:::note The payload does not contain code
-The GitHub webhook payload includes PR metadata (title, description, branch names, URLs) but **not the diff**. The prompt above instructs the agent to run `gh pr diff` to fetch the actual changes. The default `hermes-webhook` toolset is deliberately constrained (web search/extract, vision, clarify — **no terminal**) because webhook payloads can carry untrusted content. To let this route run `gh`, add a per-route toolset grant: `toolsets: ["terminal", "web"]` on the route config — see [Per-route toolsets](/docs/user-guide/messaging/webhooks#per-route-toolsets).
-:::
-
----
-
-## Step 2 — Start the gateway
-
-```bash
-hermes gateway
-```
-
-You should see:
-
-```
-[webhook] Listening on 0.0.0.0:8644 — routes: github-pr-review
-```
-
-Verify it's running:
-
-```bash
-curl http://localhost:8644/health
-# {"status": "ok", "platform": "webhook"}
-```
-
----
-
-## Step 3 — Register the webhook on GitHub
-
-1. Go to your repository → **Settings** → **Webhooks** → **Add webhook**
-2. Fill in:
-   - **Payload URL:** `https://your-public-url.example.com/webhooks/github-pr-review`
-   - **Content type:** `application/json`
-   - **Secret:** the same value you set for `secret` in the route config
-   - **Which events?** → Select individual events → check **Pull requests**
-3. Click **Add webhook**
-
-GitHub will immediately send a `ping` event to confirm the connection. It is safely ignored — `ping` is not in your `events` list — and returns `{"status": "ignored", "event": "ping"}`. It is only logged at DEBUG level, so it won't appear in the console at the default log level.
-
----
-
-## Step 4 — Open a test PR
-
-Create a branch, push a change, and open a PR. Within 30–90 seconds (depending on PR size and model), Hermes should post a review comment.
-
-To follow the agent's progress in real time:
-
-```bash
-tail -f "${HERMES_HOME:-$HOME/.hermes}/logs/gateway.log"
-```
-
----
-
-## Local testing with ngrok
-
-If Hermes is running on your laptop, use [ngrok](https://ngrok.com/) to expose it:
-
-```bash
-ngrok http 8644
-```
-
-Copy the `https://...ngrok-free.app` URL and use it as your GitHub Payload URL. On the free ngrok tier the URL changes each time ngrok restarts — update your GitHub webhook each session. Paid ngrok accounts get a static domain.
-
-You can smoke-test a static route directly with `curl` — no GitHub account or real PR needed.
-
-:::tip Use `deliver: log` when testing locally
-Change `deliver: github_comment` to `deliver: log` in your config while testing. Otherwise the agent will attempt to post a comment to the fake `org/repo#99` repo in the test payload, which will fail. Switch back to `deliver: github_comment` once you're satisfied with the prompt output.
-:::
-
-```bash
-SECRET="your-webhook-secret-here"
-BODY='{"action":"opened","number":99,"pull_request":{"title":"Test PR","body":"Adds a feature.","user":{"login":"testuser"},"head":{"ref":"feat/x"},"base":{"ref":"main"},"html_url":"https://github.com/org/repo/pull/99"},"repository":{"full_name":"org/repo"}}'
-SIG=$(printf '%s' "$BODY" | openssl dgst -sha256 -hmac "$SECRET" -hex | awk '{print "sha256="$2}')
-
-curl -s -X POST http://localhost:8644/webhooks/github-pr-review \
-  -H "Content-Type: application/json" \
-  -H "X-GitHub-Event: pull_request" \
-  -H "X-Hub-Signature-256: $SIG" \
-  -d "$BODY"
-# Expected: {"status":"accepted","route":"github-pr-review","event":"pull_request","delivery_id":"..."}
-```
-
-Then watch the agent run:
-```bash
-tail -f "${HERMES_HOME:-$HOME/.hermes}/logs/gateway.log"
-```
-
-:::note
-`hermes webhook test <name>` only works for **dynamic subscriptions** created with `hermes webhook subscribe`. It does not read routes from `config.yaml`.
-:::
-
----
-
-## Filtering to specific actions
-
-GitHub sends `pull_request` events for many actions: `opened`, `synchronize`, `reopened`, `closed`, `labeled`, etc. The `events` list filters by the `X-GitHub-Event` header value, and route-level `filters` can narrow by payload fields such as `action`.
-
-The prompt in Step 1 already handles this by instructing the agent to stop early for `closed` and `labeled` events.
-
-:::warning The agent still runs and consumes tokens
-The "stop here" instruction prevents a meaningful review, but the agent still runs to completion for every `pull_request` event regardless of action. Prefer filtering before the agent wakes:
-
-```yaml
-filters:
-  - field: "action"
-    in: ["opened", "synchronize", "reopened"]
-```
-
-For high-volume repositories, you can still filter upstream with a GitHub Actions workflow that calls your webhook URL conditionally.
-:::
-
-> There is no Jinja2 or conditional template syntax. `{field}` and `{nested.field}` are the only substitutions supported. Anything else is passed verbatim to the agent.
-
----
-
-## Using a skill for consistent review style
-
-Load a [Hermes skill](/user-guide/features/skills) to give the agent a consistent review persona. Add `skills` to your route inside `platforms.webhook.extra.routes` in `config.yaml`:
-
-```yaml
-platforms:
-  webhook:
-    enabled: true
-    extra:
-      routes:
-        github-pr-review:
-          secret: "your-webhook-secret-here"
-          events: [pull_request]
-          prompt: |
-            A pull request event was received (action: {action}).
-            PR #{number}: {pull_request.title} by {pull_request.user.login}
-            URL: {pull_request.html_url}
-
-            If the action is "closed" or "labeled", stop here and do not post a comment.
-
-            Otherwise:
-            1. Run: gh pr diff {number} --repo {repository.full_name}
-            2. Review the diff using your review guidelines.
-            3. Write a concise, actionable review comment and post it.
-          skills:
-            - review
-          deliver: github_comment
-          deliver_extra:
-            repo: "{repository.full_name}"
-            pr_number: "{number}"
-```
-
-> **Note:** Only the first skill in the list that is found is loaded. Hermes does not stack multiple skills — subsequent entries are ignored.
-
----
-
-## Sending responses to Slack or Discord instead
-
-Replace the `deliver` and `deliver_extra` fields inside your route with your target platform:
-
-```yaml
-# Inside platforms.webhook.extra.routes.<route-name>:
-
-# Slack
-deliver: slack
-deliver_extra:
-  chat_id: "C0123456789"   # Slack channel ID (omit to use the configured home channel)
-
-# Discord
-deliver: discord
-deliver_extra:
-  chat_id: "987654321012345678"  # Discord channel ID (omit to use home channel)
-```
-
-The target platform must also be enabled and connected in the gateway. If `chat_id` is omitted, the response is sent to that platform's configured home channel.
-
-Valid `deliver` values: `log` · `github_comment` · `telegram` · `discord` · `slack` · `signal` · `sms`
-
----
-
-## GitLab support
-
-The same adapter works with GitLab. GitLab uses `X-Gitlab-Token` for authentication (plain string match, not HMAC) — Hermes handles both automatically.
-
-For event filtering, GitLab sets `X-GitLab-Event` to values like `Merge Request Hook`, `Push Hook`, `Pipeline Hook`. Use the exact header value in `events`:
-
-```yaml
-events:
-  - Merge Request Hook
-```
-
-GitLab payload fields differ from GitHub's — e.g. `{object_attributes.title}` for the MR title and `{object_attributes.iid}` for the MR number. The easiest way to discover the full payload structure is GitLab's **Test** button in your webhook settings, combined with the **Recent Deliveries** log. Alternatively, omit `prompt` from your route config — Hermes will then pass the full payload as formatted JSON directly to the agent, and the agent's response (visible in the gateway log with `deliver: log`) will describe its structure.
-
----
-
-## Security notes
-
-- **Never use `INSECURE_NO_AUTH`** in production — it disables signature validation entirely. It is only for local development.
-- **Rotate your webhook secret** periodically and update it in both GitHub (webhook settings) and your `config.yaml`.
-- **Rate limiting** is 30 req/min per route by default (configurable via `extra.rate_limit`). Exceeding it returns `429`.
-- **Duplicate deliveries** (webhook retries) are deduplicated via a 1-hour idempotency cache. The cache key is `X-GitHub-Delivery` if present, then `X-Request-ID`, then a millisecond timestamp. When neither delivery ID header is set, retries are **not** deduplicated.
-- **Prompt injection:** PR titles, descriptions, and commit messages are attacker-controlled. Malicious PRs could attempt to manipulate the agent's actions. Run the gateway in a sandboxed environment (Docker, VM) when exposed to the public internet.
-
----
-
-## Troubleshooting
-
-| Symptom | Check |
-|---|---|
-| `401 Invalid signature` | Secret in config.yaml doesn't match GitHub webhook secret |
-| `404 Unknown route` | Route name in the URL doesn't match the key in `routes:` |
-| `429 Rate limit exceeded` | 30 req/min per route exceeded — common when re-delivering test events from GitHub's UI; wait a minute or raise `extra.rate_limit` |
-| No comment posted | `gh` not installed, not on PATH, or not authenticated (`gh auth login`) |
-| Agent runs but no comment | Check the gateway log — if the agent output was empty or just "SKIP", delivery is still attempted |
-| Port already in use | Change `extra.port` in config.yaml |
-| Agent runs but reviews only the PR description | The prompt isn't including the `gh pr diff` instruction — the diff is not in the webhook payload |
-| Can't see the ping event | Ignored events return `{"status":"ignored","event":"ping"}` at DEBUG log level only — check GitHub's delivery log (repo → Settings → Webhooks → your webhook → Recent Deliveries) |
-
-**GitHub's Recent Deliveries tab** (repo → Settings → Webhooks → your webhook) shows the exact request headers, payload, HTTP status, and response body for every delivery. It is the fastest way to diagnose failures without touching your server logs.
-
----
-
-## Full config reference
-
-```yaml
-platforms:
-  webhook:
-    enabled: true
-    extra:
-      port: 8644               # listen port (default: 8644)
-      secret: ""               # optional global fallback secret
-      rate_limit: 30           # requests per minute per route
-      max_body_bytes: 1048576  # payload size limit in bytes (default: 1 MB)
-
-      routes:
-        <route-name>:
-          secret: "required-per-route"
-          events: []            # [] = accept all; otherwise list X-GitHub-Event values
-          prompt: ""            # {field} / {nested.field} resolved from payload
-          skills: []            # first matching skill is loaded (only one)
-          deliver: "log"        # log | github_comment | telegram | discord | slack | signal | sms
-          deliver_extra: {}     # repo + pr_number for github_comment; chat_id for others
-```
-
----
-
-## What's Next?
-
-- **[Cron-Based PR Reviews](./github-pr-review-agent.md)** — poll for PRs on a schedule, no public endpoint needed
-- **[Webhook Reference](/user-guide/messaging/webhooks)** — full config reference for the webhook platform
-- **[Build a Plugin](/developer-guide/plugins)** — package review logic into a shareable plugin
-- **[Profiles](/user-guide/profiles)** — run a dedicated reviewer profile with its own memory and config

package/docs/80_upstream-docs-and-skills/hermes-dev-skill/src/docs/guides/work-with-skills.md

@@ -1,290 +0,0 @@
----
-sidebar_position: 12
-title: "Working with Skills"
-description: "Find, install, use, and create skills — on-demand knowledge that teaches Hermes new workflows"
----
-
-# Working with Skills
-
-Skills are on-demand knowledge documents that teach Hermes how to handle specific tasks — from generating ASCII art to managing GitHub PRs. This guide walks you through using them day to day.
-
-For the full technical reference, see [Skills System](/user-guide/features/skills).
-
----
-
-## Finding Skills
-
-Every Hermes installation ships with bundled skills. See what's available:
-
-```bash
-# In any chat session:
-/skills
-
-# Or from the CLI:
-hermes skills list
-```
-
-This shows a compact list with names and descriptions:
-
-```
-ascii-art         Generate ASCII art using pyfiglet, cowsay, boxes...
-arxiv             Search and retrieve academic papers from arXiv...
-github-pr-workflow Full PR lifecycle — create branches, commit...
-plan              Plan mode — inspect context, write a markdown...
-excalidraw        Create hand-drawn style diagrams using Excalidraw...
-```
-
-### Searching for a Skill
-
-```bash
-# Search by keyword
-/skills search docker
-/skills search music
-```
-
-### The Skills Hub
-
-Official optional skills (heavier or niche skills not active by default) are available via the Hub:
-
-```bash
-# Browse official optional skills
-/skills browse
-
-# Search the hub
-/skills search blockchain
-```
-
----
-
-## Using a Skill
-
-Every installed skill is automatically a slash command. Just type its name:
-
-```bash
-# Load a skill and give it a task
-/ascii-art Make a banner that says "HELLO WORLD"
-/plan Design a REST API for a todo app
-/github-pr-workflow Create a PR for the auth refactor
-
-# Just the skill name (no task) loads it and lets you describe what you need
-/excalidraw
-```
-
-You can also trigger skills through natural conversation — ask Hermes to use a specific skill, and it will load it via the `skill_view` tool.
-
-### Progressive Disclosure
-
-Skills use a token-efficient loading pattern. The agent doesn't load everything at once:
-
-1. **`skills_list()`** — compact list of all skills (~3k tokens). Loaded at session start.
-2. **`skill_view(name)`** — full SKILL.md content for one skill. Loaded when the agent decides it needs that skill.
-3. **`skill_view(name, file_path)`** — a specific reference file within the skill. Only loaded if needed.
-
-This means skills don't cost tokens until they're actually used.
-
----
-
-## Installing from the Hub
-
-Official optional skills ship with Hermes but aren't active by default. Install them explicitly:
-
-```bash
-# Install an official optional skill
-hermes skills install official/research/arxiv
-
-# Install from the hub in a chat session
-/skills install official/creative/songwriting-and-ai-music
-
-# Install SKILL.md and its referenced support files from an HTTP(S) URL
-hermes skills install https://sharethis.chat/SKILL.md
-/skills install https://example.com/SKILL.md --name my-skill
-```
-
-What happens:
-1. The skill directory is copied to `~/.hermes/skills/`
-2. It appears in your `skills_list` output
-3. It becomes available as a slash command
-
-:::tip
-Installed skills take effect in new sessions. If you want it available in the current session, use `/reset` to start fresh, or add `--now` to invalidate the prompt cache immediately (costs more tokens on the next turn).
-:::
-
-### Verifying Installation
-
-```bash
-# Check it's there
-hermes skills list | grep arxiv
-
-# Or in chat
-/skills search arxiv
-```
-
----
-
-## Plugin-Provided Skills
-
-Plugins can bundle their own skills using namespaced names (`plugin:skill`). This prevents name collisions with built-in skills.
-
-```bash
-# Load a plugin skill by its qualified name
-skill_view("superpowers:writing-plans")
-
-# Built-in skill with the same base name is unaffected
-skill_view("writing-plans")
-```
-
-Plugin skills are **not** listed in the system prompt and don't appear in `skills_list`. They're opt-in — load them explicitly when you know a plugin provides one. When loaded, the agent sees a banner listing sibling skills from the same plugin.
-
-For how to ship skills in your own plugin, see [Build a Hermes Plugin → Bundle skills](/developer-guide/plugins#bundle-skills).
-
----
-
-## Configuring Skill Settings
-
-Some skills declare configuration they need in their frontmatter:
-
-```yaml
-metadata:
-  hermes:
-    config:
-      - key: tenor.api_key
-        description: "Tenor API key for GIF search"
-        prompt: "Enter your Tenor API key"
-        url: "https://developers.google.com/tenor/guides/quickstart"
-```
-
-When a skill with config is first loaded, Hermes prompts you for the values. They're stored in `config.yaml` under `skills.config.*`.
-
-Manage skill config from the CLI:
-
-```bash
-# Interactive config for a specific skill
-hermes skills config gif-search
-
-# View all skill config
-hermes config get skills.config --json
-```
-
----
-
-## Creating Your Own Skill
-
-Skills are just markdown files with YAML frontmatter. Creating one takes under five minutes.
-
-### 1. Create the Directory
-
-```bash
-mkdir -p ~/.hermes/skills/my-category/my-skill
-```
-
-### 2. Write SKILL.md
-
-```markdown title="~/.hermes/skills/my-category/my-skill/SKILL.md"
----
-name: my-skill
-description: Brief description of what this skill does
-version: 1.0.0
-metadata:
-  hermes:
-    tags: [my-tag, automation]
-    category: my-category
----
-
-# My Skill
-
-## When to Use
-Use this skill when the user asks about [specific topic] or needs to [specific task].
-
-## Procedure
-1. First, check if [prerequisite] is available
-2. Run `command --with-flags`
-3. Parse the output and present results
-
-## Pitfalls
-- Common failure: [description]. Fix: [solution]
-- Watch out for [edge case]
-
-## Verification
-Run `check-command` to confirm the result is correct.
-```
-
-### 3. Add Reference Files (Optional)
-
-Skills can include supporting files the agent loads on demand:
-
-```
-my-skill/
-├── SKILL.md                    # Main skill document
-├── references/
-│   ├── api-docs.md             # API reference the agent can consult
-│   └── examples.md             # Example inputs/outputs
-├── templates/
-│   └── config.yaml             # Template files the agent can use
-└── scripts/
-    └── setup.sh                # Scripts the agent can execute
-```
-
-Reference these in your SKILL.md:
-
-```markdown
-For API details, load the reference: `skill_view("my-skill", "references/api-docs.md")`
-```
-
-### 4. Test It
-
-Start a new session and try your skill:
-
-```bash
-hermes chat -q "/my-skill help me with the thing"
-```
-
-The skill appears automatically — no registration needed. Drop it in `~/.hermes/skills/` and it's live.
-
-:::info
-The agent can also create and update skills itself using `skill_manage`. After solving a complex problem, Hermes may offer to save the approach as a skill for next time.
-:::
-
----
-
-## Per-Platform Skill Management
-
-Control which skills are available on which platforms:
-
-```bash
-hermes skills
-```
-
-This opens an interactive TUI where you can enable or disable skills per platform (CLI, Telegram, Discord, etc.). Useful when you want certain skills only available in specific contexts — for example, keeping development skills off Telegram.
-
----
-
-## Skills vs Memory
-
-Both are persistent across sessions, but they serve different purposes:
-
-| | Skills | Memory |
-|---|---|---|
-| **What** | Procedural knowledge — how to do things | Factual knowledge — what things are |
-| **When** | Loaded on demand, only when relevant | Injected into every session automatically |
-| **Size** | Can be large (hundreds of lines) | Should be compact (key facts only) |
-| **Cost** | Zero tokens until loaded | Small but constant token cost |
-| **Examples** | "How to deploy to Kubernetes" | "User prefers dark mode, lives in PST" |
-| **Who creates** | You, the agent, or installed from Hub | The agent, based on conversations |
-
-**Rule of thumb:** If you'd put it in a reference document, it's a skill. If you'd put it on a sticky note, it's memory.
-
----
-
-## Tips
-
-**Keep skills focused.** A skill that tries to cover "all of DevOps" will be too long and too vague. A skill that covers "deploy a Python app to Fly.io" is specific enough to be genuinely useful.
-
-**Let the agent create skills.** After a complex multi-step task, Hermes will often offer to save the approach as a skill. Say yes — these agent-authored skills capture the exact workflow including pitfalls that were discovered along the way.
-
-**Use categories.** Organize skills into subdirectories (`~/.hermes/skills/devops/`, `~/.hermes/skills/research/`, etc.). This keeps the list manageable and helps the agent find relevant skills faster.
-
-**Update skills when they go stale.** If you use a skill and hit issues not covered by it, tell Hermes to update the skill with what you learned. Skills that aren't maintained become liabilities.
-
----
-
-*For the complete skills reference — frontmatter fields, conditional activation, external directories, and more — see [Skills System](/user-guide/features/skills).*