Dev10x-qa-scope

Analyze a PR to identify QA needs and e2e coverage gaps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-qa-scope-brave-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dev10x-qa-scope
Source: https://github.com/Brave-Labs/dev10x/tree/main/codex-skills/dev10x-qa-scope
Command: npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-qa-scope-brave-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA teams struggle to determine PR readiness, identify gaps in end-to-end (e2e) test coverage, and track QA work across Linear tickets.

Core Features & Use Cases

  • PR QA scoping: assesses regression risk and identifies missing e2e tests for changed code paths.
  • Coverage mapping: cross-references changed modules with the e2e-coverage-map to surface gaps.
  • Ticketing integration: creates QA sub-tickets in Linear MCP and links to parent feature tickets.
  • Prerequisites & workflow: auto-detects PR context, checks for existing QA work, and recommends actions.

Quick Start

Provide a PR URL or number, or allow auto-detection from your current branch, to run the QA scope.

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 PR QA scoping and e2e coverage gap analysis?

Automate PR QA scoping by analyzing changed modules against an e2e coverage map to identify regression risks and missing end-to-end tests. The workflow auto-detects PR context and checks existing QA tickets to recommend targeted testing actions.

How does e2e coverage mapping work for changed code paths in a PR?

E2e coverage mapping cross-references changed modules with a coverage map to surface gaps and enforce risk assessment. It identifies missing end-to-end test scenarios and recommends whether manual testing or new automated tests are required.

Can I use Linear MCP to create QA sub-tickets for missing e2e tests?

Yes, Linear MCP integration creates QA sub-tickets and links them to parent feature tickets. The system performs pre-creation checks to avoid duplicates and routes tickets directly through Linear MCP with optional Jira integration.

What do I need to provide to start a PR QA scope assessment?

Provide a PR URL or number to start the QA scope assessment, or allow auto-detection from your current branch. The system uses this input to map changed modules and check for existing QA work before recommending actions.

Does PR risk assessment for e2e coverage support Jira integration?

Yes, PR risk assessment and ticket routing support optional Jira integration alongside Linear MCP. The workflow enforces risk assessment and pre-creation checks before generating QA sub-tickets across these ticketing platforms.