skills.rest
zizzfizzix
zizzfizzixCOMMUNITY
Explore all skills by this author →
GitHub

auto-qa-scenarios

Generate a human QA report for merged pull requests grouped by product area.

Updated May 31, 2026
Search Tags:#GitHub#Pull Request#Automation#PR analysis#QA report
One-click install
npx skills add https://github.com/zizzfizzix/agentic-engineering-framework --skill auto-qa-scenarios
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-qa-scenarios
Source: https://github.com/zizzfizzix/agentic-engineering-framework/tree/main/core/ai/skills/auto-qa-scenarios
Command: npx skills add https://github.com/zizzfizzix/agentic-engineering-framework --skill auto-qa-scenarios

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, python, yaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of a human QA report for a window of merged pull requests, saving time and effort in creating and maintaining QA documentation.

Core Features & Use Cases

  • PR Analysis: Analyze merged pull requests, grouping them by product area and assigning priorities.
  • Report Generation: Create a detailed QA report that includes click paths, verification points, and risk callouts.
  • Documentation PR: Ship the report as a documentation-only PR against the default branch.
  • Use Case: After a batch of PRs are merged, use this Skill to automatically generate a QA report that outlines the testing plan and verifies the changes.

Quick Start

Run the auto-qa-scenarios skill to generate a QA report for the last 7 days of merged PRs.

Frequently Asked Questions about auto-qa-scenarios

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

FAQPage Schema
How do I generate a QA report for merged pull requests automatically?▼

To generate a QA report for merged pull requests, run the skill to analyze recent PR merges, group changes by product area, assign testing priorities, and automatically create a documentation PR against the default branch.

What is included in an automated PR analysis QA report?▼

An automated PR analysis QA report groups merged changes by product area, assigns testing priorities, and details click paths, verification points, and risk callouts to guide manual testing.

Do I need GitHub API access to automate QA documentation for pull requests?▼

Yes, GitHub API access via the gh CLI is required, along with specific environment variables defining branch names and the default branch, to fetch merged PR data and create the documentation PR.

Can I use Python and YAML to automate pull request QA reports?▼

Yes, this skill uses Python and YAML dependencies alongside the GitHub CLI to fetch merged PR data, group changes by product area, and structure the final QA report output.

What's the best way to group merged pull requests by product area for testing?▼

The best way to group merged pull requests by product area for testing is using an automation skill that analyzes PR metadata, assigns testing priorities, and outputs a structured QA report.

Why does automated QA report generation create a documentation PR instead of a static file?▼

Automated QA report generation creates a documentation PR against the default branch to ensure the testing plan, click paths, and risk callouts are version-controlled and reviewable directly within the repository.

Related Skills

Explore More Software Engineering Skills→
Nice-Wolf-StudioNice-Wolf-Studio

pull-request-management

Automate GitHub pull request workflows using the gh CLI.

Official
Intermediate
g2i-aig2i-ai
51

review

Review Git branches or pull requests and generate QA reports.

Official
Intermediate
PlagueHOPlagueHO
4

merge-dependabot-prs

Merge ready Dependabot PRs in parallel with status reports.

Community
Advanced
hffmnnjhffmnnj
39

atomic-commits

Create small, focused commits with one change per commit and meaningful messages.

Community
Basic