RepoGuard Push Gate

Stop agents from pushing to the wrong repo or branch before it happens

Problem

When coding agents work across multiple repositories, pushing changes to the wrong repo, wrong branch or straight past review is a real and frequent hazard. People are already building Claude Code hooks specifically to block pushes into the wrong repo, which proves the pain.

Solution

A lightweight set of hooks and pre-push checks: per repo you declare allowed remotes, branches and path patterns, and any push from an agent or human is validated and blocked with a clear explanation. Ships with installable config templates to keep setup trivial.

Users

Indie devs and small teams juggling many repos with heavy coding-agent use; teams that gave agents git push rights.

MVP

Install scripts for Claude Code, Codex and git hooks; per-repo allowed remotes/branches config; pre-push validation and blocking; readable failure reasons and fix suggestions; example configs included.

Revenue

Open-source CLI plus a paid team tier (central policy, audit logs, Slack alerts) at roughly $5–10 per seat per year.

Why now

Agents with push rights are now normal, yet mainstream tooling has almost no guardrails against wrong-repo pushes. Scattered hook solutions already exist, so the timing is right for a general product.