Pull Guard

Pull Guard is a maintainer cockpit for the age of coding agents. It scans open pull requests in a GitHub repository, builds a local cache, analyzes the patch and metadata, then turns the queue into something maintainers can actually reason about. Instead of showing a flat list of PRs, Triage groups similar contribution attempts into semantic clusters, detects AI-flood patterns, ranks the strongest candidate in each cluster, estimates contributor trust based on past PR history, and flags patch-text mismatches where the PR description says one thing but the diff does another. It also highlights low-value patterns like README-only noise, generic descriptions, dependency changes without usage, lockfile churn, untested core changes, and repeated shallow edits across many contributors. The product is CLI-first with a visual report for demos and day-to-day review. Maintainers can run a scan, inspect duplicate clusters, compare two PRs, ask for an explanation of a specific change, review AI-flood waves, and use the dashboard to decide where their attention is most valuable. Pull Guard stays read-only by default: it does not label, close, or comment unless a maintainer explicitly asks for a dry-run plan. At its best, PUll Guard gives maintainers what GitHub does not: a way to see intent, duplication, trust, patch quality, and review priority across the entire queue.