skills.rest
wooyek
wooyekCOMMUNITY
Explore all skills by this author →
Website𝕏@wooyekGitHub

dev10x-qa-scope

Analyze pull requests for QA needs and create Linear sub-tickets.

Updated Aug 27, 2026
Search Tags:#automation#testing#github#qa#linear#pr
One-click install
npx skills add https://github.com/wooyek/dev10x-ai --skill dev10x-qa-scope
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev10x-qa-scope
Source: https://github.com/wooyek/dev10x-ai/tree/main/codex-skills/dev10x-qa-scope
Command: npx skills add https://github.com/wooyek/dev10x-ai --skill dev10x-qa-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of assessing Pull Requests (PRs) for Quality Assurance (QA) needs, identifying potential risks, checking end-to-end (e2e) test coverage gaps, and creating necessary sub-tickets in Linear.

Core Features & Use Cases

  • PR Risk Assessment: Analyzes changes to determine regression risk (Low, Medium, High).
  • E2E Coverage Analysis: Checks existing e2e tests against changed code modules using a coverage map.
  • Sub-Ticket Creation: Generates QA sub-tickets in Linear for manual testing or new e2e scenarios.
  • Use Case: When a PR is ready for merge, use this Skill to automatically assess if it needs manual QA, if new e2e tests are required, and create a ticket for the QA team, linking it to the parent ticket.

Quick Start

Use the dev10x-qa-scope skill to analyze the current PR for QA needs and create a sub-ticket if necessary.

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 ticket creation in Linear from a GitHub Pull Request?▼

You can automate QA ticket creation by analyzing a Pull Request for regression risk and e2e test coverage gaps, then automatically generating a sub-ticket in Linear linked to the parent issue.

Does this tool assess regression risk and e2e test coverage for PRs?▼

Yes, it assesses regression risk by categorizing it as Low, Medium, or High, and checks existing end-to-end test coverage against changed code modules using a local coverage map.

Can I use a PR URL or branch name to trigger QA scope analysis?▼

You can trigger QA scope analysis by providing a PR number, PR URL, or letting the tool auto-detect the PR from your current Git branch to evaluate testing needs.

What is the best way to identify e2e test coverage gaps before merging a PR?▼

The best way to identify e2e test coverage gaps is referencing a local e2e coverage map against the changed modules in the PR to determine if new e2e scenarios are required.

Do I need GitHub CLI and Linear MCP to automate PR QA assessment?▼

Yes, automating PR QA assessment requires the GitHub CLI to fetch PR details and the Linear MCP to manage and create the necessary QA sub-tickets in your project tracking system.

Why create manual QA sub-tickets instead of just running automated e2e tests?▼

Creating manual QA sub-tickets is necessary when e2e coverage gaps are detected or regression risk is high, ensuring the QA team manually validates the changes before the PR merges.

Related Skills

Explore More Software Engineering Skills→
sunholo-datasunholo-data
33

Test Coverage Guardian

Analyze test coverage to identify gaps, dead code, and brittleness.

Community
Intermediate
hidonguyenhidonguyen

ck:test

Execute unit, integration, e2e, and UI tests across JavaScript/TypeScript, Python, Go, Rust, and Flutter projects.

Community
Advanced
kevintsengtwkevintsengtw
28

dotnet-testing-code-coverage-analysis

Measure and interpret .NET code coverage with Coverlet and ReportGenerator.

Community
Intermediate
zhuangfanupupzhuangfanupup

project-review

Review repository changes for architecture consistency and regression risk.

Community
Intermediate