Loading…
LoadingLoading…
LoadingTwo pull requests can each look reasonable in isolation and still need coordination before they land together. Veripsa Core is the advisory, GitHub-native, content-free pre-merge check that surfaces that relationship while the PRs are still open.
The risk is simple: two open PRs can each look reasonable in isolation, yet still need ordering attention before they land on main. Most tools inspect one PR at a time, so the relationship between open PRs is easy to miss.
Veripsa focuses on that pre-merge relationship. It does not claim a merge is safe; it gives reviewers an early signal when open PRs may need coordination.
A git merge conflict only fires on direct textual conflicts. Cross-PR overlap can be more subtle: each individual diff looks valid, but the two changes still interfere once they land together. CI catches that eventually, but often only by failing on main after the second PR is already in. An AI code reviewer reads one PR at a time. A merge queue serialises merges, but it is not designed to explain which open PRs are likely to interfere.
Parallel AI work increases the number of open PR relationships a reviewer must track. The useful signal is not a story about who made the change; it is whether open PRs deserve a landing-order check.
The category is pre-merge collision control — a GitHub check that evaluates open-PR context before changes land and flags likely overlap while the work is still reviewable. To be useful in an AI-agent workflow, it needs to run automatically, surface the signal inside GitHub where the agent and the human already are, and stay advisory — the human (or the merge queue) decides the merge order.
Adjacent categories do related work but don’t answer the question. Merge queues serialise merges but don’t know overlap. AI reviewers read one PR at a time. CI runs per-PR on a rebased tree, so cross-PR interference often surfaces only after the second PR is in. The shape that closes the gap is an advisory check for open PRs before they land.
Veripsa Core is a GitHub App. It uses minimal operational metadata needed to post advisory checks while keeping file bodies out of Veripsa storage.
On covered PRs, Core evaluates open-PR context in that repo. When likely overlap is observed, PRs see an advisory check — Clear, Heads up, Wait in line, or Unknown — with a suggested land order. The check is advisory by default; whether it gates a merge is a branch-protection decision you make later. See how it works for the per-PR walkthrough.
Free to install. Matching pull requests receive advisory checks after install. Source code is not stored or shown.
Install Veripsa Core