qa-report

Generate concise QA reports for GitHub PRs in weshake-bank repositories.

Updated Aug 23, 2026

Search Tags:#automation #github #qa #quality #diff #pr #report

Ready to run

npx skills add https://github.com/wolfbela/claude-skill --skill qa-report-wolfbela

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-report
Source: https://github.com/wolfbela/claude-skill/tree/main/weshake/skills/qa-report
Command: npx skills add https://github.com/wolfbela/claude-skill --skill qa-report-wolfbela

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of QA reports for one or more GitHub PRs across weshake-bank repositories, saving time for QA teams and engineers.

Core Features & Use Cases

Identify PRs from user input and fetch key metadata (title, body, head branch, URL)
Analyze diffs to summarize changes and testing considerations
Produce a structured Markdown report suitable for QA validation and stakeholder review

Quick Start

Provide one or more PR numbers as input to generate a QA report for each PR.

Frequently Asked Questions about qa-report

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

FAQPage Schema

How do I automate QA reports for GitHub PRs?▼

Automate QA reports for GitHub PRs by providing PR numbers as input to fetch metadata like descriptions and changed files, then analyze diffs to summarize changes and testing considerations into a Markdown report.

How does analyzing PR diffs help with testing considerations?▼

Analyzing PR diffs helps with testing considerations by retrieving changed files and branch details via GitHub, then summarizing the code modifications to highlight specific areas requiring QA validation before merging.

Can I generate a single QA report for multiple GitHub pull requests?▼

Yes, you can generate a single QA report for multiple GitHub pull requests by identifying several PR numbers in your input, which retrieves descriptions, branches, and diffs for each PR into one structured Markdown output.

Do I need to provide repository URLs to fetch PR metadata using gh?▼

You do not need to provide repository URLs to fetch PR metadata using gh, because the tool locates the pull requests directly within the configured weshake-bank repositories using only the PR numbers.

What is the best way to summarize changed files for stakeholder review?▼

The best way to summarize changed files for stakeholder review is to analyze PR diffs and extract key metadata like title, head branch, and URL, producing a structured Markdown report suitable for validation.

Are there limitations when generating QA reports across different branches?▼

Limitations when generating QA reports across different branches include being restricted to locating pull requests within the weshake-bank repositories, requiring valid PR numbers to fetch diffs and metadata successfully.