Dev10x:qa-scope

Analyze Pull Requests for QA risks and generate test cases.

7|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-qa-scope-dev10x-guru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dev10x:qa-scope
Source: https://github.com/Dev10x-Guru/Dev10x-Claude/tree/main/skills/qa-scope
Command: npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-qa-scope-dev10x-guru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, linear-mcp, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of identifying QA needs in PRs, assessing regression risks, and creating test cases for automated testing.

Core Features & Use Cases

  • Automated PR QA Analysis: Assess PRs for potential issues, checking coverage gaps and required manual tests.
  • Risk Classification: Classify changes into risk levels and create QA sub-tickets accordingly.
  • E2E Coverage Mapping: Identify existing e2e tests and gaps for PR changes.
  • Test Case Generation: Automatically generate regression test cases and E2E scenarios.

Quick Start

Use the command /Dev10x:qa-scope <PR URL or number> to analyze the PR and create QA sub-tickets for the identified needs.

Frequently Asked Questions about Dev10x:qa-scope

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

FAQPage Schema
How do I automate QA analysis and test case generation for pull requests?

Automate PR QA analysis by evaluating code changes to identify regression risks, map e2e coverage gaps, and generate regression test cases automatically. This streamlines identifying required manual tests and creates corresponding QA sub-tickets.

How does PR regression risk classification work for e2e coverage mapping?

Regression risk classification assesses PR changes to categorize risk levels and identify e2e coverage gaps. It checks for existing e2e tests matching the modifications, enabling targeted creation of regression test cases and QA sub-tickets.

Can I use GitHub CLI and Linear MCP to automate QA sub-ticket creation?

Yes, PR QA analysis integrates GitHub CLI to fetch pull request details and Linear MCP to create QA sub-tickets. This automates tracking regression risks and coverage gaps directly within your project management workflow.

Do I need Python to generate E2E test scenarios from PR changes?

Yes, Python is required to run the custom analysis scripts that evaluate PR changes and generate E2E test scenarios. These scripts automate coverage gap identification and regression test case creation.

What's the best way to integrate automated test case generation into a CI/CD pipeline?

Integrate test case generation into CI/CD pipelines by triggering automated PR QA analysis on code review. This identifies coverage gaps and regression risks, outputting generated E2E scenarios and QA sub-tickets.

How do I identify E2E test coverage gaps in a GitHub pull request?

Identify e2e test coverage gaps by analyzing PR changes against existing e2e tests. The analysis maps modifications to current test scenarios, highlighting uncovered areas and generating regression test cases to fill the gaps.