PR Automation - Approve Workflows

Approve pending GitHub Actions workflows and add /ok-to-test comments.

2|1|Updated Oct 31, 2025
One-click install
npx skills add https://github.com/stbenjam/claude-nine --skill pr-automation-approve-workflows
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: PR Automation - Approve Workflows
Source: https://github.com/stbenjam/claude-nine/tree/main/plugins/pr-automation/skills/approve-workflows
Command: npx skills add https://github.com/stbenjam/claude-nine --skill pr-automation-approve-workflows

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This Skill eliminates the manual, repetitive tasks of approving GitHub Actions workflows from external contributors and adding /ok-to-test comments to pull requests. It streamlines your PR review process, saving maintainers significant time and reducing complexity in busy open-source or team repositories.

Core Features & Use Cases

  • Automated Workflow Approval: Automatically approves pending GitHub Actions workflows from external contributors, ensuring CI/CD pipelines run without manual intervention.
  • /ok-to-test Commenting: Adds /ok-to-test comments to pull requests labeled "needs-ok-to-test", triggering Prow CI jobs or similar external testing systems.
  • Comprehensive Reporting: Provides a detailed summary of approved workflows, commented PRs, and timed-out runs, giving you full visibility into the automation process.
  • Use Case: A repository maintainer receives dozens of external pull requests daily. Instead of manually clicking "Approve and run" for each workflow and adding /ok-to-test comments, they can use this skill to process all pending items in one go, reclaiming hours of their day.

Quick Start

Approve all pending GitHub Actions workflows and add /ok-to-test comments for pull requests in the 'stbenjam/claude-nine' repository.

Frequently Asked Questions about PR Automation - Approve Workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub Actions workflow approvals for external contributors?▼

This Skill automates workflow approval by identifying pull requests labeled 'needs-ok-to-test' from external contributors, then approves pending GitHub Actions workflows and adds `/ok-to-test` comments in bulk. It eliminates manual clicking through the GitHub UI for each workflow, processing all pending items across multiple PRs in a single run.

Can I use GitHub CLI with PR automation tools?▼

Yes. This Skill uses the `gh` CLI alongside GitHub REST APIs to query pull requests and workflows, then execute approvals and comments. It requires `gh` authentication to your repository, making it compatible with any workflow that already uses GitHub's command-line tools.

What's the best way to handle `/ok-to-test` comments in open-source repositories?▼

Automated `/ok-to-test` commenting reduces manual overhead in busy open-source projects. This Skill detects PRs with the 'needs-ok-to-test' label and adds the comment automatically, triggering Prow CI jobs or similar external testing systems without maintainer intervention.

How do I approve multiple GitHub Actions workflows at once from my repository?▼

This Skill bulk-approves pending workflows by detecting your repository (from git config or arguments), authenticating via `gh`, querying all workflows awaiting approval, and approving them in a single operation. It generates a detailed summary showing all approved workflows, commented PRs, and timed-out runs.

Does workflow approval automation work with multiple repositories?▼

This Skill processes one repository per run but accepts the repository as an argument, allowing you to run it across multiple repositories in sequence or as part of a CI/CD pipeline. It auto-detects the current repository from git if no argument is provided.

What visibility do I get into the approval process?▼

The Skill provides comprehensive reporting including a structured summary of all approved workflows, PRs that received `/ok-to-test` comments, and any timed-out runs, giving you full transparency into what the automation processed.