dev10x:qa-scope
/dev10x:qa-scope
Analyze a PR for QA needs, check e2e coverage gaps, and create QA sub-tickets when manual testing or new e2e tests are needed. TRIGGER when: PR needs QA analysis for coverage gaps or manual test requirements. DO NOT TRIGGER when: executing QA test cases (use dev10x:qa-self), or PR has no user-facing changes.
- Author
- dev10x-guru ↗
- Repository
- dev10x-claude ↗
- Licence
- MIT
- Last repository change
- 12.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 12.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Analyze a PR for QA needs, check e2e coverage gaps, and create QA sub-tickets when manual testing or new e2e tests are needed. TRIGGER when: PR needs QA analysis for coverage gaps or manual test requirements. DO NOT TRIGGER when: executing QA test cases (use dev10x:qa-self), or PR has no user-facing changes.
Original author description
Analyze a PR for QA needs, check e2e coverage gaps, and create QA sub-tickets when manual testing or new e2e tests are needed. TRIGGER when: PR needs QA analysis for coverage gaps or manual test requirements. DO NOT TRIGGER when: executing QA test cases (use dev10x:qa-self), or PR has no user-facing changes.
How it works
- Orchestration
- Overview
- Prerequisites
- Workflow
- Integration with Other Skills
- Example Usage
SKILL.md preview
--- name: dev10x:qa-scope description: > Analyze a PR for QA needs, check e2e coverage gaps, and create QA sub-tickets when manual testing or new e2e tests are needed. TRIGGER when: PR needs QA analysis for coverage gaps or manual test requirements. DO NOT TRIGGER when: executing QA test cases (use dev10x:qa-self), or PR has no user-facing changes. user-invocable: true invocation-name: dev10x:qa-scope allowed-tools: - AskUserQuestion - Bash(gh pr diff:*) - Bash(grep:*) - mcp__plugin_dev10x_cli__pr_detect - mcp__claude_ai_Linear__list_issues - mcp__claude_ai_Linear__get_issue - mcp__claude_ai_Linear__save_issue --- # QA Scope - PR Quality Assurance Assessment ## Orchestration This skill follows `references/task-orchestration.md` patterns. Create a task at invocation, mark completed when done: **REQUIRED: Create a task at invocation.** Execute at startup: 1. `TaskCreate(subject="Analyze PR for QA needs", activeForm="Analyzing QA scope")` Mark completed when done: `TaskUpdate(taskId, status="completed")` ## Overview Analyzes a PR for QA needs by assessing regression risk, checking existing e2e test coverage in the project's e2e suite, identifying gaps, and creating QA sub-tickets in Linear when manual testing or new e2e scenarios are needed. **Use when:** - A PR is ready for merge and needs QA assessment - You want to check if a change needs manual QA testing - `/dev10x:gh-pr-monitor` triggers Phase 2.5 (automatic) **Do NOT use for:** - Test-only PRs (no production code changes) - Documentation-only changes - CI/config changes with no runtime impact ## Prerequisites **Required:** - PR number, URL, or branch name (will auto-detect from current branch) **Available context:** - `$E2E_ROOT` — the project's e2e test repository, resolved at Phase 3.0. There is no fixed path: this skill ships with every project, and the suite lives wherever that project keeps it - Linear MCP — ticket and team management - GitHub CLI — PR details ## Workflow ### Phase 1: Gather PR Context #### 1.1 Identify PR Accept input as PR URL, PR number, or auto-detect from current branch. One call resolves all four values: ``` mcp__plugin_dev10x_cli__pr_detect(pr="<URL, bare number, or empty>") ``` It returns `PR_NUMBER`, `REPO`, `PR_URL` and `BRANCH`. Take `BRANCH` from the response rather than from local git — in a multi-worktree checkout the local branch is not necessarily the PR's head. #### 1.2 Extract Ticket ID Parse ticket ID from branch name following `username/TICKET-ID/[worktree/]description` convention: ```bash TICKET_ID=$(echo "$BRANCH" | grep -oP '[A-Z]+-\d+') ``` #### 1.3 Fetch PR Diff ```bash gh pr diff $PR_NUMBER # cli-friction: allow raw-gh-pr — no MCP diff wrapper exists; declared in allowed-tools ``` Identify changed modules by examining file paths in the diff. Map each changed file to its bounded context (e.g., `src/payments/` → payments, `src/square_oauth/` → square_oauth). #### 1.4 Fetch Linear Ticket Use Linear MCP to retrieve: - Title and description - Parent ticket (if sub-ticket) - Labels and team - Related tickets **Store the Linear issue ID** — it will be used as `parent` when creating the QA sub-ticket in Phase 5.1. Look up by the ticket identifier parsed in Step 1.2 (e.g. search for `JIRA-5345` or `PAY-133`). #### 1.5 Check for Existing QA Sub-Tickets Before doing any risk assessment, check if QA work already exists: 1. Use Linear MCP `list_issues` to find sub-tickets with "QA" in the title under the parent ticket 2. If existing QA tickets are found → list them in the assessment and note "QA already tracked" 3. Check if the PR has 100% unit test coverage for all new code paths If existing QA tickets cover the changed area AND unit tests are comprehensive, set the recommendation to "No new ticket needed" and skip to Phase 4 presentation. *Why?* Recommending a new QA ticket without checking existing ones causes redundant work. Unit test coverage at 100% on a guard clause / defensive check (no UI impact) often makes a separate QA ticket unnecessary. Turn 16 of the PAY-58 pr:monitor session. ### Phase 2: Assess QA Risk Classify the change into a risk level based on what was changed. #### Risk Classification Matrix | Risk Level | Criteria | QA Action | |------------|----------|-----------| | **Low** | Config-only, docs, test-only, CI changes | No QA ticket needed | | **Medium** | New scope/permission, refactoring with tests, admin changes | QA regression ticket | | **High** | Payment flow changes, new features, DB migrations, external API changes | QA regression + e2e coverage ticket | #### Decision Factors Evaluate each factor and aggregate: | Factor | Risk Contribution | |--------|------------------| | Touches `payments/` or money calculation code | +High | | Modifies external API integrations (Square, Motor, PartsTech) | +High | | Includes DB migrations | +Medium-High | | Changes OAuth scopes or authentication | +Medium-High | | Adds new user-facing feature | +High | | Refactors existing code with full test coverage | +Medium | | Modifies admin/config only | +Medium | | Test-only or config-only changes | Low (stop here) | | PR has 100% unit test coverage for new code | Reduces risk one level | #### Risk Reduction - Full unit test coverage for all new code paths → reduce risk by one level - Changes isolated to a single module with no cross-cutting concerns → reduce risk by one level - Existing e2e coverage already exercises the changed path → reduce risk by one level ### Phase 3: Check E2E Coverage #### 3.0 Locate the E2E Suite Resolve `$E2E_ROOT` before searching anything. In order: 1. An `e2e_root` entry for this repo in the project's qa-scope config (3-tier resolution, `references/config-resolution.md`) 2. A sibling checkout whose name ends in `-e2e` under the same parent directory as the repo under review 3. A `features/` directory inside the repo under review **When none of the three resolves, stop and say so.** Report the coverage check as "not performed — no e2e suite found" and let risk stand on the Phase 2 assessment alone. Do NOT report "no existing coverage": a suite that was never searched and a suite with no matching scenarios produce the same empty result, and only one of them justifies filing a new-tests ticket. #### 3.1 Map Changed Modules to E2E Features When the project keeps a coverage map, look up the changed modules' feature files, tags, and step definitions there rather than searching the whole suite. `references/e2e-coverage-map.md` is a **worked example from one project**, not a map of yours — a project's own map belongs at tier 1 or 2. With no map, skip to 3.2. #### 3.2 Search for Existing Coverage Search the resolved suite for scenarios that exercise the changed code paths: ```bash # Search feature files for relevant keywords grep -r "keyword" "$E2E_ROOT/features/" --include="*.feature" # Search step definitions for relevant steps grep -r "keyword" "$E2E_ROOT/features/steps/" --include="*.py" # Check page objects for relevant UI interactions grep -r "keyword" "$E2E_ROOT/tests/pages/" --include="*.py" ``` Layouts differ — `tests/pages/` in particular is a convention, not a standard. A path that does not exist is a miss to work around, not evidence of missing coverage. #### 3.3 Identify Gaps Compare what the PR changes against what existing e2e tests cover: - **Covered:** existing scenarios test the changed behavior → note which ones - **Partially covered:** existing scenarios test related but not exact behavior → note gaps - **Not covered:** no existing e2e scenarios for the changed area → flag for new tests ### Phase 4: Present Assessment Format and present the QA verdict to the user for approval before creating any tickets. #### Verdict Format ``` QA Assessment for PR #<number> Risk: <Low | Medium | High> Reason: <1-line summary of why this risk level> Changed Modules: - <module 1> (<risk contribution>) - <module 2> (<risk contribution>) E2E Coverage: Existing: <what's already covered> Gap: <what's missing> Gap: <what's missing> Recommendation: <No QA needed | QA regression ticket | QA regression + e2e ticket> Regression Test Cases: 1. <test case> 2. <test case> 3. <test case> New E2E Scenarios Needed: 1. <scenario description> 2. <scenario description> Create QA sub-ticket? (y/n) ``` **REQUIRED: Call `AskUserQuestion`** (do NOT use plain text) to get approval: - **"Create QA sub-ticket"** → proceed to Phase 5 - **"Skip QA"** → end with summary - **"Edit assessment"** → let user modify before creating #### Pre-Creation Check: Search for Existing QA Tickets Before creating a new ticket, check if one already exists: 1. Use Linear MCP `list_issues` to find sub-tickets with "QA" in the title under the parent ticket 2. If an existing QA ticket covers the changed area, note it in the assessment and ask whether a new ticket is needed or the existing one is sufficient 3. If the existing ticket is On Hold or Out of Scope, it may still be referenced from the PR description without creating a duplicate *Why?* PAY-616 session found QA-202 (On Hold) covering the same domain. Creating a duplicate would be noisy and confusing. ### Phase 5: Create QA Sub-Ticket (if approved) #### 5.1 Determine Ticket Structure Create the QA ticket as a sub-ticket of the PR's Linear ticket. Use the Linear issue ID retrieved in Step 1.4 as the `parent` parameter. This links the QA ticket to the feature ticket in Linear's hierarchy. #### 5.2 Create Linear Ticket **Ticket destination routing** — choose based on user instruction: | User says | Destination | How | |-----------|-------------|-----| | (default, no instruction) | Linear **QA** team | `team: "QA"` (id: `c89229e5-8aeb-4934-8575-aa9f18c22e99`) | | "JIRA team ticket" | Linear **JIRA Sync** team | `team: "JIRA Sync"` (id: `0c456d25-e332-4210-992e-65f668a5080e`) — auto-syncs to Jira application | | "JIRA ticket" (no "team") | Jira application directly | Use Jira REST API with credentials from MEMORY.md | Use Linear MCP `create_issue`: ``` Team: <see routing table above> Title: QA: <PR ticket title> Parent: <PR's Linear issue ID from Step 1.4> Description: <structured test plan — see format below> ``` #### 5.3 Ticket Description Format ```markdown ## Context PR: <PR URL> Ticket: <parent ticket ID and title> Risk: <level> ## Changed Areas - <module>: <what changed> ## Regression Test Cases - [ ] <test case 1> - [ ] <test case 2> - [ ] <test case 3> ## E2E Coverage Gaps Existing coverage: <summary> New scenarios needed: - [ ] <scenario 1> - [ ] <scenario 2> ## Related Resources - <links to relevant admin pages, API docs, Square docs, etc.> ``` #### 5.4 Ask About Assignment **REQUIRED: Call `AskUserQuestion`** (do NOT use plain text) to ask who to assign. Offer the project's QA assignee when its config names one, otherwise offer the tracker's own candidates (team members already assigned to QA tickets) — never a name hardcoded here, which belongs to one deployment's staffing and not to every project the plugin ships to. #### 5.5 Report Completion Output the created ticket ID and URL. ## Integration with Other Skills ``` dev10x:qa-scope ├── Uses: Linear MCP (ticket data, create sub-ticket) ├── Uses: GitHub CLI (PR diff, PR details) ├── Reads: $E2E_ROOT (e2e coverage check, resolved at Phase 3.0) ├── References: references/e2e-coverage-map.md (worked example) ├── Called by: pr:monitor (Phase 2.5) └── Standalone: /qa-scope <PR URL or number> ``` ## Example Usage ### Standalone ``` /qa-scope https://github.com/example-org/app-pos/pull/1169 /qa-scope 1169 /qa-scope # auto-detect from current branch ``` ### Via pr:monitor Triggered automatically in Phase 2.5 when CI passes and PR has approval. ### Example Output ``` QA Assessment for PR #1169 Risk: Medium Reason: Adds new Square OAuth scope (DEVICES_READ) — changes external API authorization Changed Modules: - square_oauth/ (OAuth scope change → Medium-High) E2E Coverage: Existing: square.feature covers invoice + payment link flows Gap: No terminal device pairing/listing tests Gap: No OAuth re-authorization flow tests Recommendation: Create QA regression ticket Regression Test Cases: 1. Verify existing Square OAuth authorization still works 2. Verify legacy token refresh includes new scope 3. Verify terminal checkout flow unaffected 4. Verify new OAuth authorization includes DEVICES_READ New E2E Scenarios Needed: 1. OAuth re-authorization flow after scope change 2. Terminal device listing in POS settings Create QA sub-ticket? (y/n) ```
Files in this package (3)
- SKILL.md 12 KB
- evals/evals.json 5 KB
- references/e2e-coverage-map.md 7 KB
Versions
The database has no other skills named dev10x:qa-scope.
Database snapshot: 13.11.2026 · package version 4f097bc5bae9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100coverage
Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing". - 84analyze-test-coverage
Analyze test coverage gaps and prioritize what to test next. Use this skill whenever the user says "analyze test coverage", "what's our test coverage", "find gaps in test coverage", "which code isn't tested", "improve test coverage", "show me a coverage report", "coverage… - 100smart-test
Find test gaps and generate tests for uncovered code. Triggers on: generate tests, write tests, test coverage, find untested code, test gaps, smart test, what needs testing. - 100test-plan
Plan and check testing for a feature: map each acceptance criterion to a test at the right level, find gaps, write the missing tests, and run end-to-end checks of the main flows. Use when a feature needs a test strategy or before review. - 100generate-test-cases
Use when the user asks to analyze code for test coverage, list what test cases are needed, or review testing strategy — WITHOUT generating actual test code. - 100automated-test-planning
Produce a standalone test plan by analyzing code for test coverage gaps and edge cases. Use when you need to create, generate, or draft a test plan for a branch, need to analyze test coverage, or need to identify what tests to write for specific files or directories. Does not…