القائمة
Generates clear, actionable verification guides for QA testing of Positron bug fixes and features
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Analyze e2e test failures from a GitHub Actions run. Provide a run ID or URL to download reports, extract traces/screenshots/logs, identify root causes, and get suggested actions. Works with both posit-dev/positron and posit-dev/positron-builds repos.
Generates well-structured PR bodies with dynamically fetched e2e test tags
Triage a specific Positron e2e test that is already failing or flaking in CI. Given a test name, surface its recent distinct failure modes from history, pull the evidence (trace, screenshots, logs) for each mode, and reason through the evidence to a root cause collaboratively with the engineer, landing on a concrete test fix or a product-bug repro. Test-centric counterpart to e2e-failure-analyzer (run-centric). For authoring a brand-new test, use author-e2e-tests.
Use when writing, debugging, or maintaining Playwright e2e tests for Positron -- new test files, test cases, flaky-test fixes, test infrastructure, or performance/metric tests.
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting session data.
Use when working on the Chat Customizations editor — the management UI for agents, skills, instructions, hooks, prompts, MCP servers, and plugins.
| name | positron-qa-verify |
| disable-model-invocation | true |
| description | Generates clear, actionable verification guides for QA testing of Positron bug fixes and features |
Analyzes GitHub issues and PRs to generate verification guides for manual QA testing.
gh) authenticatedCRITICAL: Run non-interactively without prompts.
AskUserQuestion - Always write to .claude/skills/positron-qa-verify/output/Issue number or URL:
4567#4567https://github.com/posit-dev/positron/issues/4567Run 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,authorgh pr list --repo posit-dev/positron --search "<number>" --state all --json number,titleFetch primary PR details:
gh pr view <pr-number> --repo posit-dev/positron --json title,body,comments,additions,deletions,urlFetch all related PRs/issues mentioned in the body in parallel.
Only for PRs < 500 lines (additions + deletions from Step 3):
gh pr diff <pr-number> --repo posit-dev/positronSkip diff for large PRs - use PR description and comments instead.
Search comments for #1234 references, additional test scenarios, edge cases, and platform-specific notes.
Create markdown file in .claude/skills/positron-qa-verify/output/verify-issue-{number}-{timestamp}.md
See references/verification_guide.md for format and examples.
After generating the guide, offer to create a verification comment template.
Only when user accepts:
scripts/detect_versions.sh to auto-detect Positron and OS versionsComment format:
.claude/skills/positron-qa-verify/output/verify-issue-{number}-{timestamp}.md
scripts/detect_versions.shFast, 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.