[Automations] Optimize onboarding for GitHub Monitor, Slack Monitor, GitHub Code Review Bot automations

[jpelletier1]

Optimize onboarding for pre-built automations: GitHub Monitor, Slack Monitor, GitHub Code Review Bot

Overview

Three pre-built automations should be polished to ensure a smooth, out-of-the-box experience for new users:

• GitHub Monitor (github-repo-monitor)
• Slack Monitor (slack-channel-monitor)
• GitHub Code Review Bot (currently named "GitHub PR Review Copilot")

Goal

The goal of this ticket is group together several tasks for improving our pre-built automations ahead of launch June 15th.

Tasks

1. Rename "GitHub PR Review Copilot" → "GitHub Code Review Bot"

Update the display name / title wherever it appears (catalog entry, skill file, README, UI labels) to "GitHub Code Review Bot" for clarity and consistency.

2. Fix colon-containing filenames in skill initiator files (Windows compatibility)

Skill files that contain colons in their filenames (e.g. pr-reviewer:setup.md) break git checkout on Windows, resulting in a broken experience for Windows users.

Rename any such files to use hyphens instead of colons (e.g. pr-reviewer-setup.md) and update all references accordingly.

This PR fixes one scenario, but others likely exist among the pre-built automations: #317

3. Fix incorrect env var reference in github-repo-monitor skill

The github-repo-monitor skill references GITHUB_TOKEN, but the GitHub MCP Server in Agent Canvas uses GITHUB_PERSONAL_ACCESS_TOKEN. This mismatch causes the generated automation to fail on first run without extra manual steps.

All references should be updated to GITHUB_PERSONAL_ACCESS_TOKEN.

Reviewing this PR should address the issue: OpenHands/extensions#313

4. Fix GitHub Code Review Bot to correctly poll for new PRs

The skill that sets up the GitHub Code Review Bot (invoked via /pr-reviewer:setup) currently creates an automation that does not correctly gate conversation creation on the presence of a new PR. This avoids unnecessary agent runs and ensures each conversation is triggered by real work.

The generated automation should:

• Poll for open PRs that have not been reviewed yet (i.e., are new since the last poll)
• Only start a conversation when at least one new PR requiring review is found
• Skip the run silently when there are no new PRs

It should:

• Ask users for which repos to monitor
• Ask users if it should only do PR reviews on PRs that contain a specific label

A community member created a PR that may improve this experience: #1158

Things to update:

• Move the community member's prompt into a SKILL format

[enyst]

Ah, I just made it GitHub PR Review Agent 😅

My agent was called “bot” in Slack these days, and I cut its access to Slack 😂 so it doesn’t see and save in its memory such demotion, hah

[enyst]

J/K but same thing I guess? GitHub Code Review Agent

[jpelletier1]

Agent works for me! Just don't want to say "copilot" 😊