Skill Detail

Enforce pull-request approval policy with Policy Bot

Codify complex GitHub review rules, evaluate pull requests, and expose approval status as a required check.

Code Quality & ReviewMulti-Framework
Code Quality & Review Multi-Framework Security Reviewed
โญ 1k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill enforce-pull-request-approval-policy-with-policy-bot Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Policy Bot GitHub App, GitHub repository, policy.yml
Install & setup
Deploy Policy Bot as a GitHub App, configure the required repository permissions and webhook, add a policy.yml file to each repository, and make the Policy Bot status check required where merge gating is needed.
Author
Palantir
Publisher
Organization
Last updated
Jul 6, 2026
Quick brief

Use Policy Bot when an agent or operator needs to enforce review policy that GitHub’s native required reviews cannot express cleanly. The workflow is to define policy.yml rules for users, teams, file paths, branches, conditions, and approval logic, let Policy Bot evaluate each pull request, then inspect the status check and detailed approval state before merging. Invoke this instead of using the product normally when the job is policy-as-code review enforcement and merge gating, not ordinary manual PR review. The boundary is pull-request approval policy evaluation for GitHub repositories; it is not a generic CI platform, code review bot, or GitHub SDK listing.

How it works

What this skill actually does

Inputs and prerequisites: Policy Bot GitHub App, GitHub repository, policy.yml.

Setup notes: Deploy Policy Bot as a GitHub App, configure the required repository permissions and webhook, add a policy.yml file to each repository, and make the Policy Bot status check required where merge gating is needed.

Source and verification boundary: use https://github.com/palantir/policy-bot as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.