verify-pr

Execute repository-defined verification skills against a PR head and collect results.

292|39|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/warpdotdev/oz-for-oss --skill verify-pr-warpdotdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-pr
Source: https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/verify-pr
Command: npx skills add https://github.com/warpdotdev/oz-for-oss --skill verify-pr-warpdotdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill coordinates repository-defined PR verification workflows, running the discovered verification skills for a pull request and compiling a consolidated verification report without mutating the PR.

Core Features & Use Cases

  • Orchestrates execution of all discovered verification skills for a PR
  • Aggregates outcomes into verification_report.json with clear per-skill status
  • Uploads useful artifacts from verification runs while keeping PR mutations off-limits

Quick Start

Run the /oz-verify slash-command for a PR to execute all discovered verification skills and generate verification_report.json.

Frequently Asked Questions about verify-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull-request verification and collect CI results without mutating the branch?

Pull-request verification orchestration executes discovered verification skills against the PR head and aggregates outcomes into verification_report.json. It performs non-mutating checks and collects artifacts while keeping the PR branch untouched.

What is the best way to consolidate multiple CI verification checks into a single report for a pull request?

Consolidating CI verification checks involves orchestrating repository-defined verification skills and aggregating their outcomes into verification_report.json. This provides a clear per-skill status and collects useful artifacts from the verification runs.

How does non-mutating verification orchestration work for pull requests?

Non-mutating verification orchestration identifies the PR and the set of verification skills to run, then executes them against the PR head. It collects results and uploads artifacts while ensuring no mutations are applied to the pull request.

Do I need explicit verification skill metadata to run PR verification orchestration?

Yes, PR verification orchestration requires explicit verification skill metadata and a trusted fetch-script context. These prerequisites allow the orchestrator to discover and execute the correct repository-defined verification skills.

Can I use this PR verification orchestration for workflows that only require artifact collection?

Yes, this orchestration applies to workflows that require non-mutating verification orchestration and artifact collection. It executes verification skills and uploads useful artifacts without applying mutations to the pull request.

Why does my PR verification orchestration skip certain repository-defined checks?

PR verification orchestration only runs discovered verification skills that have explicit metadata defined. If a verification skill lacks the required metadata, it will not be discovered or executed during the orchestration process.