skills.rest
open-mercato
open-mercatoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

om-auto-qa-scenarios

Generates manual QA verification reports from merged GitHub pull requests as docs-only PRs.

1.7k|382|Updated Sep 10, 2025
Search Tags:#manual testing#regression#Automation#Documentation#gitHub#Pull Requests#QA report
One-click install
npx skills add https://github.com/open-mercato/open-mercato --skill om-auto-qa-scenarios
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-auto-qa-scenarios
Source: https://github.com/open-mercato/open-mercato/tree/main/.ai/skills/om-auto-qa-scenarios
Command: npx skills add https://github.com/open-mercato/open-mercato --skill om-auto-qa-scenarios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams struggle to translate a stream of merged pull requests into an actionable manual testing plan. This Skill turns a window of merged PRs into a prioritized, click-by-click verification report delivered as a docs-only PR against the develop branch.

Core Features & Use Cases

  • Flexible PR windows: Analyze merged PRs by date floor, PR-number floor, or the default last 7 days, with optional inclusion of open PRs.
  • Prioritized QA routes: Groups PRs into P0/P1/P2 testing areas with click paths, verification steps, and risk callouts mapped to priority and risk labels.
  • Dual artifacts: Writes both markdown and standalone HTML reports under .ai/analysis/ and ships them as a labeled docs-only PR.
  • Use Case: After a sprint, run the Skill to produce a QA sign-off checklist covering every PR merged into develop, so testers know exactly where to click and what regressions to watch for.

Quick Start

Ask the agent to generate a QA scenarios report for all PRs merged in the last 7 days and open it as a docs-only PR against develop.

Frequently Asked Questions about om-auto-qa-scenarios

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

FAQPage Schema
How do I generate a QA testing plan from merged GitHub pull requests?▼

Invoke the Skill with an optional window argument: a date, a PR number floor, or nothing for the last 7 days. It fetches merged PR metadata via the GitHub CLI, groups changes into prioritized QA areas, and opens a docs-only PR with markdown and HTML reports.

How are QA priorities P0, P1, and P2 assigned to pull requests?▼

Priorities map to existing priority-* labels on PRs, with P0 covering auth, money flows, and tenant-scope risks, P1 covering CRM and UI areas, and P2 covering docs and tooling. Risk labels adjust testing depth independently of priority.

Can I include open unmerged PRs in the QA report?▼

Yes, pass the --include-open flag to add open non-draft PRs to the report. They are labelled as not yet merged so QA can sanity-check upcoming changes alongside the merged window.

What happens if the QA report generation cannot finish in one run?▼

The Skill leaves the PR body marked Status: in-progress, updates the plan checklist with completed steps and commit SHAs, and posts a hand-off comment directing resumption via the om-auto-continue-pr Skill.

Does the QA report Skill run builds or tests before opening the PR?▼

No, docs-only runs skip build, test, and typecheck gates. Validation is limited to lint, git diff whitespace checks, and manual verification that every PR link in the artifacts resolves correctly.

Related Skills

Explore More Software Engineering Skills→
pingcappingcap
40.5k

tidb-pr-metadata-guard

Preserves TiDB pull request template structure while editing mutable PR metadata fields.

Official
Intermediate
Euraika-LabsEuraika-Labs
14

team-qa

Orchestrates end-to-end sprint QA with smoke checks, test plans, and sign-off reports.

Official
Advanced
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
dthuy62dthuy62

ck:test

Run automated tests, coverage checks, and build verification for web and Flutter applications.

Community
Advanced