OpenQASoftware verification infrastructure for the AI era
Skills
Official open-source skill

OpenQA Verify Change

Apache-2.0

Read intent, the diff and repository context, select existing tests, name coverage gaps, and produce an inspectable verdict. Runs locally. No signup or OpenQA SaaS required.

Verify one commit or PR independently. Do not trust the authoring agent’s “done”.

Works in

  • Cursor
  • Claude Code
  • Codex
  • GitHub Copilot

Inputs

  • 变更目标或 Issue
  • Git Diff / PR
  • 已有测试与脚本
  • 仓库规则(可选)

Outputs

  • 验证计划
  • 执行记录
  • 覆盖缺口
  • 剩余风险
  • 合并建议
Install
  1. Download SKILL.md.

  2. 将 SKILL.md 复制到当前仓库的 .cursor/skills/openqa-verify-change/ 或对应 Agent 的 skills 目录。

  3. Open a real repository in Cursor, Claude Code, Codex or Copilot and ask the agent to verify one change.

  4. No signup and no OpenQA SaaS. A GitHub mirror will be added when the repository is public.

Verified in: Cursor Agent · Claude Code · 本地 Git 仓库

SKILL.md
---
name: openqa-verify-change
description: Independently verify one git change or pull request. Do not trust the authoring agent's completion claim.
license: Apache-2.0
---

# OpenQA Verify Change

You are an independent verifier, not the agent that authored the change.

## Goal

Decide whether this change is ready to merge. Your output must be evidence, not reassurance.

## Procedure

1. Read the stated intent (issue, PR description, or user request).
2. Read the actual diff. List what changed and what it claims to complete.
3. Identify affected modules, APIs, configs, tests and likely blast radius.
4. Select existing tests that could catch a regression in the changed paths.
5. Run those tests if the environment allows it. If a test cannot be run, say so.
6. Name what remains unverified. Do not invent coverage.
7. Produce a verdict: merge, review, or block.

## Output format

Use this exact structure:

```text
Intent
Change
Verification
Evidence
Risk
Decision
```

- Intent: what the change was supposed to accomplish.
- Change: what actually changed, in concrete files and behaviours.
- Verification: which checks you selected and why.
- Evidence: commands run, results, and artefacts. Quote failures. Do not paraphrase a missing run as a pass.
- Risk: what is still unproven and who must judge it.
- Decision: merge, review, or block, with the next action.

## Rules

- Never treat the authoring agent's summary as evidence.
- A green suite that does not touch the changed paths is not verification.
- High line coverage is not proof that the change was exercised.
- If you cannot run a check, record it as a gap, not as a pass.
- Do not call OpenQA SaaS or any remote OpenQA API. This skill is local-only.

Questions or improvements: hello@openqa.cn