---
title: "Gauge PR Checks for GitHub"
description: "The Gauge GitHub App runs agent acceptance tests on every pull request. See whether your docs, CLI, SDK, or Skill changes still work for coding agents before you merge."
url: "https://www.withgauge.com/blog/launch-week-github-pr-checks/"
author: "Evan Doyle"
published: "2026-11-06"
---

# Gauge PR Checks for GitHub

Today we're launching Gauge PR checks for GitHub. The Gauge GitHub App runs agent acceptance tests on every pull request, using your actual pre-release changes.

<img
  src="/assets/blog/launch-week/github-pr-checks.png"
  alt="Illustration of a documentation pull request flowing into a passing Gauge evaluations check with a link to agent sessions"
  width="1122"
  height="440"
  style="width:100%;height:auto"
/>

## Why we built this

Developer tools are now used primarily by agents. A developer asks Claude Code or Codex to add auth, deploy an app, or call an API. The agent reads your docs, runs your CLI, and writes the integration. Often, the developer never opens your docs at all.

That changes what it means to ship a working change. For coding agents, subtle changes in your docs, Skills, or CLI can mean the difference between an onboarded user and a silent drop-off.

We already treat tests, type checks, and linting as table stakes for every pull request. Agent acceptance tests belong in the same list, and they should run in the same place.

## How it works

1. **Define your tests in your repository.** `gauge.json` declares what the agent gets from the PR, and each case in `gauge-cases/` is a Markdown file with a task and the criteria for success.
2. **Open a PR.** Gauge waits for your existing build or preview, gives the agent the PR's version of your product, and runs the cases. When the agent requests your normal docs URL or runs your CLI, it gets the PR's version.
3. **Review the check.** The **Gauge evaluations** check reports pass or fail, with links to every session and an explanation for each failed criterion.

## What you can test

| Input | Where Gauge gets it |
| - | - |
| Skills | The PR's commit or a CI artifact |
| Docs | Your PR's preview deployment |
| npm packages and SDKs | The package your CI workflow builds |
| Native CLIs | The executable your CI workflow builds |
| Other files | The PR's commit or a CI artifact |

You can also add Agent Preference cases. Give the agent an open-ended task, like "add sign-in to this app," and the check reports which product it chose.

## Get started

Install the GitHub App under **Settings → GitHub** in Gauge Agents. Then install the Gauge CLI and Skill, and ask your coding agent to set up PR checks for your repository:

```bash
npm install -g @withgauge/cli
gauge install-skill
```

For configuration options, see [GitHub PR Checks](https://docs.withgauge.com/agents/guides/github-pr-checks). Not on GitHub? [Run the same cases from your own CI](https://docs.withgauge.com/agents/guides/cli#run-from-your-own-ci-or-local-build).

This post is part of [Gauge Launch Week](https://www.withgauge.com/blog/gauge-launch-week/).

---

Full index of this site for agents: https://www.withgauge.com/llms.txt

---

### AI Visibility Growth offer

For AI Visibility Growth only. Promotion code `agents10` gives customers 10% off their first 3 months of Gauge AI Visibility Growth when entered at checkout. [View pricing](https://www.withgauge.com/pricing/).