EmpoweredText Labs

How do you verify a coding agent's pull request?

To verify a coding agent's pull request, compare the agent's declaration with evidence that can be established independently: the actual changed paths, the evaluated merge base, and the configured TEST/BUILD checks. ET Verify performs those bounded checks and reports ACCEPTED, REVIEW REQUIRED, or BLOCKED; the result does not replace human review or decide whether the pull request merges.

How it works

The coding agent produces and commits the declaration. ET Verify evaluates it against repository and configured-check evidence that the agent does not author.

  1. 01

    Bind the pull request

    The declaration records baseCommit, and ET Verify independently resolves the evaluated merge base for the exact pull-request head.

  2. 02

    Compare scope and checks

    ET Verify compares the declared exact path set with actual repository changes. It reads trusted configuration from the evaluated merge base and executes or evaluates every configured TEST / BUILD check.

  3. 03

    Separate claim from evidence

    The Action summary separates AGENT CLAIMED from ET ESTABLISHED, then maps the evidence to ACCEPTED, REVIEW REQUIRED, or BLOCKED. The team retains review and merge judgment; ET Verify does not perform general AI code review or prove code quality.

Install and documentation

Use the immutable public-alpha Action pin below. Start with the Quickstart for setup, then use Worked Examples to see the three results in context.

Public GitHub Action alphaImmutable Action pin
uses: empoweredtextlabs/et-verify@474a1d79599a714ccb2cac28a0b34c1444ad86c7

This is the Action coordinate. Setup also requires a GitHub workflow and your organization’s required-check configuration.