Use cases
Run QA on an existing pull request
Use one Verify task to check a pull request on demand, with clear acceptance criteria and reviewable evidence, even when the PR was created outside Prinevo.
Validate an existing change on demand
Use this path when a PR already exists and you want focused QA before merge, after a correction, or before a release decision. You can request one run without enabling event-driven automation for every PR.
Provide the PR URL, target revision when relevant, expected behavior, acceptance criteria, and required test context. Make the target repositories and runtime dependencies available to the workspace.
Ask Verify to validate the PR
Connect GitHub or Bitbucket and an agent provider in Integrations. Select the repositories for your product and let Factory setup prepare them automatically. Review and merge any required setup PRs in their respective repositories. Configure models in Agents and compute in Settings.
- Open a new session and select Build.
- Type
@and choose Verify. - Provide the exact PR URL and observable acceptance criteria.
- Describe the checks and evidence needed, then submit.
@Verify validate [PR URL] against the latest revision.
Acceptance criteria:
- The primary user journey completes successfully.
- Invalid input is rejected with the expected message.
- The changed flow remains usable with the keyboard.
Run the relevant checks. Capture screenshots and a short flow recording
where useful, and report failures, blockers, and untested behavior.
Leave merge for the normal approval process.Use actual results to make the merge decision
Open Verification and inspect criteria, scenarios, execution results, and the evidence attached to this run. Confirm the checked revision matches the PR you intend to merge.
Resolve failing checks and missing prerequisites, then rerun the affected validation. A completed specialist task can still report a blocked or incomplete outcome; read the report rather than relying on completion status alone.