Works in
- Cursor
- Claude Code
- Codex
- GitHub Copilot
Write intent, change, verification, evidence, risk and decision as reviewable Markdown. Use it as a PR comment, a local docs/qa/ record, or the start of a team asset. No SaaS required.
Turn one verification run into an inspectable acceptance report and a Markdown quality asset.
Works in
Inputs
Outputs
Download SKILL.md.
将 SKILL.md 复制到当前仓库的 .cursor/skills/openqa-acceptance-report/ 或对应 Agent 的 skills 目录。
Open a real repository in Cursor, Claude Code, Codex or Copilot and ask the agent to verify one change.
No signup and no OpenQA SaaS. A GitHub mirror will be added when the repository is public.
Verified in: Cursor Agent · Claude Code · 本地 Markdown 仓库
--- name: openqa-acceptance-report description: Write an inspectable software-change acceptance report in Markdown. Local only. No SaaS. license: Apache-2.0 --- # OpenQA Acceptance Report Write a change-acceptance record that another engineer can audit without talking to you. ## Goal Turn a verification run into a durable Markdown asset. The report is the product. ## File If the user does not specify a path, write: `docs/qa/acceptance/<date>-<short-change-id>.md` Never overwrite an existing report. Create a new file. ## Template ```markdown # Acceptance Record - Change: <PR, commit or branch> - Date: <ISO date> - Verifier: <agent or person> - Decision: merge | review | block ## Intent ## Change ## Verification ## Evidence ## Risk ## Decision ``` ## Rules - Every claim in Evidence must point to a command, log, screenshot or test name. - If a check was skipped, list it under Risk, not Evidence. - Decision must be one of: merge, review, block. - Keep the report short enough to read in five minutes. - Do not invent metrics, pass rates or coverage percentages. - Do not call OpenQA SaaS. This skill only writes local Markdown.
Questions or improvements: hello@openqa.cn