mcpField
P
positron-qa-verify

positron-qa-verify

github.com/posit-devTesting & quality4.3k57 installsUpdated today
Repository

About positron-qa-verify

Positron QA Verify analyzes Positron GitHub issues and pull requests to create manual QA verification guides. It helps testers derive scenarios and edge cases from ticket discussions and code changes.

Key features

  1. 01Fetches issue and PR details
  2. 02Analyzes related discussions
  3. 03Reviews small PR diffs
  4. 04Creates Markdown QA guides
  5. 05Detects version details on request

Use cases

  1. 01Preparing QA tests for a bug fix
  2. 02Deriving scenarios from a feature ticket
  3. 03Finding edge cases in PR discussions
  4. 04Drafting verification steps for a ticket

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/posit-dev/positron --skill positron-qa-verify

After installing, type/positron-qa-verifyin Claude Code to confirm it loaded.

Bundled filesreferences/verification_guide.mdscripts/detect_versions.sh

Details

From the project README

Positron QA Verify

Analyzes GitHub issues and PRs to generate verification guides for manual QA testing.

When to Use

Prerequisites

  • GitHub CLI (gh) authenticated
  • Working in the Positron repository

Execution Mode

CRITICAL: Run non-interactively without prompts.

  • Never use AskUserQuestion - Always write to .claude/skills/positron-qa-verify/output/
  • Version detection is best-effort - If it fails, use empty values silently
  • Fail fast - Don't block on timeouts or missing data

Input

Issue number or URL:

  • 4567
  • #4567
  • https://github.com/posit-dev/positron/issues/4567

Workflow

Steps 1 & 2: Fetch Issue and Find PRs (Parallel)

Run these in parallel with a single message containing multiple Bash tool calls:

  • gh issue view <number> --repo posit-dev/positron --json title,body,comments,url,labels,author
  • gh pr list --repo posit-dev/positron --search "<number>" --state all --json number,title
Step 3: Analyze PR Context

Fetch primary PR details:

  • gh pr view <pr-number> --repo posit-dev/positron --json title,body,comments,additions,deletions,url

Fetch all related PRs/issues mentioned in the body in parallel.

Step 4: Review Code Changes (Conditional)

Only for PRs < 500 lines (additions + deletions from Step 3):

  • gh pr diff <pr-number> --repo posit-dev/positron

Skip diff for large PRs - use PR description and comments instead.

Step 5: Extract Linked Issues

Search comments for #1234 references, additional test scenarios, edge cases, and platform-specific notes.

Step 6: Generate Verification Guide

Create markdown file in .claude/skills/positron-qa-verify/output/verify-issue-{number}-{timestamp}.md

See references/verification_guide.md for format and examples.

Step 7: Offer Verification Comment Template

After generating the guide, offer to create a verification comment template.

Only when user accepts:

  1. Run scripts/detect_versions.sh to auto-detect Positron and OS versions
  2. Generate comment template with scenarios from the guide
  3. Copy to clipboard

Comment format:

  • Single scenario (no edge cases/regressions): Simple bullet format
  • Multiple scenarios: Grouped format with Primary/Edge cases/Regression checks sections

Output

.claude/skills/positron-qa-verify/output/verify-issue-{number}-{timestamp}.md

Helper Scripts

scripts/detect_versions.sh

Fast, silent version detection (max 4 seconds):

./scripts/detect_versions.sh

Output:

{
  "positronVersion": "2026.02.0",
  "positronBuild": "10",
  "osVersion": "macOS 26.2",
  "detectionStatus": "success"
}

Never prompts or shows errors - returns empty values on failure.

Comments

Markdown supported