mergeproof

mergeproof is an evidence gate for pull requests. It uses a single YAML file in the repository to define what a change must prove before it merges, such as tests for touched modules, a green integration job, before/after links from a live environment, or a human who opened them. CI enforces the policy and reports on the pull request. Coding agents read the same file, so what they are told is what CI checks.

The tool emphasizes declaring rules rather than describing them. For example, a rule can state that when a change touches tools/**, it ships with changed integration tests if the tool has any. Evidence is verified at its source: trace links are looked up, tests must be in the diff, and the reviewer's sign-off is bound to the exact commit. mergeproof explain and a generated AGENTS.md section tell an agent what to produce before it opens the PR, but the agent cannot approve anything.

Reports appear where people look: a scorecard comment, a requireable commit status, and review comments on the files concerned. The tool is installed via pip, initialized with a starter YAML file, and integrated into workflows by requiring the mergeproof status. It is designed to address the problem that agentic development makes outcomes cheap to claim and expensive to verify, by requiring artifacts that someone else can open and check.