positron-qa-verify

Generates QA verification guides from GitHub issues and pull requests for Positron.

4.2k|179|Updated May 24, 2022
One-click install
npx skills add https://github.com/posit-dev/positron --skill positron-qa-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: positron-qa-verify
Source: https://github.com/posit-dev/positron/tree/main/.claude/skills/positron-qa-verify
Command: npx skills add https://github.com/posit-dev/positron --skill positron-qa-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manually writing QA verification guides for bug fixes and features is time-consuming and error-prone, requiring testers to dig through GitHub issues, PR discussions, and code diffs to identify test scenarios and edge cases.

Core Features & Use Cases

  • Automated Guide Generation: Fetches GitHub issues and linked PRs via the GitHub CLI, then produces structured verification guides with primary scenarios, edge cases, and regression checks.
  • Context Extraction: Mines issue comments and PR descriptions for edge cases, platform-specific notes, and related issues, and reviews code diffs for PRs under 500 lines.
  • Verification Comment Templates: Generates ready-to-paste verification comments with auto-detected Positron and OS versions via a cross-platform detection script.
  • Use Case: A QA engineer assigned issue #4567 from the verification board runs the skill to instantly receive a complete markdown test guide with setup steps, expected behavior, and regression checks.

Quick Start

Ask the assistant to generate a QA verification guide for Positron issue 4567.

Frequently Asked Questions about positron-qa-verify

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

FAQPage Schema
How do I generate a QA verification guide for a GitHub issue?

Provide an issue number or URL (e.g., 4567 or a full GitHub link) and the skill fetches the issue, finds linked PRs, and writes a verification guide to the output directory. It extracts test scenarios, edge cases, and regression checks automatically.

What tools are required to create test scenarios from GitHub PRs?

You need the GitHub CLI (gh) authenticated with access to the posit-dev/positron repository. The skill uses gh commands to fetch issues, PR details, comments, and diffs in parallel.

Does the skill review code diffs for every pull request?

No, it only fetches the code diff for PRs under 500 lines of changes (additions plus deletions). For larger PRs, it relies on the PR description and comments instead to keep execution fast.

Can I auto-detect Positron and OS versions for verification comments?

Yes, the included detect_versions.sh script detects Positron version, build number, and OS version across macOS, Linux, and Windows. It returns JSON with empty values on failure and never prompts or blocks.

What output format does the verification guide use?

Guides are markdown files saved as verify-issue-{number}-{timestamp}.md in the skill's output directory. They follow a structured template with issue summary, root cause, test scenarios with checkboxes, and testing context.