GitHub Workflow

An OpenClaw plugin that manages your GitHub work without leaving your AI assistant. Pull requests to review, issues to triage, release notes to draft, weekly digests of what shipped — all in one place.

Current version: 0.2.0

What's new in 0.2.0

• New github_list_my_open_prs tool: see PRs you opened (grouped by status — awaiting review, in review, draft, stale). Different from list_review_prs which shows PRs others opened that need your review.
• github_summarize_pr now accepts "latest": omit the prNumber and the tool resolves to the most recently opened PR in the repo. Lets you say "summarize the latest PR in chris-openclaw/podcast-pipeline" without remembering the number.
• Friendly error handling: rate limits, expired tokens, missing repos, and permission errors all produce clear messages instead of cryptic stack traces.
• Better empty-state messages: when nothing is found, suggests other tools that might help.

See CHANGELOG.md for the full release history.

What it does

Six agent tools, all surfaced to the LLM:

Why this plugin

OpenClaw has plenty of plugins that observe your AI agent's behavior. This plugin observes your GitHub work and gives the agent the data it needs to actually help. The companion skill (github-workflow) teaches the agent when to call which tool and how to format the results.

Installation

1. Set up authentication

Create a GitHub Personal Access Token at github.com/settings/tokens with these scopes:

• repo (for private repos) or public_repo (for public-only)
• read:user (so the plugin knows who "you" are when listing review requests)

Set the token in your environment:

macOS/Linux (in ~/.bashrc or ~/.zshrc):

export GITHUB_TOKEN=ghp_yourTokenHere

Windows (PowerShell, system-level):

[Environment]::SetEnvironmentVariable("GITHUB_TOKEN", "ghp_yourTokenHere", "User")

Restart your terminal (and the OpenClaw gateway) after setting it.

2. Install the plugin

openclaw plugins install @chris-openclaw/github-workflow

Or install from a local clone for development (see DEVELOPMENT.md).

3. Configure default repos

In your OpenClaw config:

{
  "plugins": {
    "github-workflow": {
      "auth": {
        "method": "pat",
        "tokenEnv": "GITHUB_TOKEN"
      },
      "defaultRepos": [
        "chris-openclaw/ministry-weekly",
        "chris-openclaw/podcast-pipeline"
      ]
    }
  }
}

The defaultRepos list is what the cross-repo tools (github_list_review_prs, github_weekly_digest) use when you don't override them in the call.

4. Restart the gateway

openclaw gateway restart

You should see [github-workflow] Registered 5 tools. Default repos: N. Auth: OK. in the gateway logs.

Usage

The agent automatically picks the right tool based on what you ask:

"What PRs am I supposed to review?" → calls github_list_review_prs

"Summarize PR #42 in the ministry-weekly repo." → calls github_summarize_pr

"Triage open issues in chris-openclaw/podcast-pipeline. Anything stale?" → calls github_triage_issues

"Generate release notes for ministry-weekly between v1.0.0 and v1.1.0." → calls github_release_notes

"What shipped across my repos this week?" → calls github_weekly_digest

What's coming in v0.2

• GitHub App authentication (in addition to PATs)
• github_post_review with explicit approval gating
• Auto-detection of repos from the authenticated user's account
• Per-file commentary on the largest changes (better depth: "deep" mode)
• Webhook receiver so the agent can react to PR events in real time
• Multi-page issue triage for large repos

See CHANGELOG.md for the full release history.

Limits

• v0.1.0 is read-only. The plugin never posts comments, merges PRs, or modifies code.
• Token-bound: only sees repos the configured token can access.
• No webhook listener yet — all operations are on-demand.

Plugin metadata