메뉴
Determine which vscode-copilot-chat release tag to use for a Positron build
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 | pick-copilot-tag |
| disable-model-invocation | true |
| description | Determine which vscode-copilot-chat release tag to use for a Positron build |
Determine which microsoft/vscode-copilot-chat release tag is compatible with
a given Positron build by checking API proposal version compatibility.
Use this skill when:
gh) installed and authenticatedjq and python3 availableFrom the Positron repo root, run the script with no arguments. It will
automatically read package.json for the Code OSS version, extract proposals
from the source tree, discover compatible tag series, and check them all:
.claude/skills/pick-copilot-tag/scripts/check-proposals.sh
For checking against a built Positron app instead of the source tree:
.claude/skills/pick-copilot-tag/scripts/check-proposals.sh --app /Applications/Positron.app
To check against a specific Positron release (fetches both proposals and the Code OSS version from the release tag on GitHub):
.claude/skills/pick-copilot-tag/scripts/check-proposals.sh --positron-version 2026.03.0
To check a specific tag series (skips auto-discovery):
.claude/skills/pick-copilot-tag/scripts/check-proposals.sh --tag-series v0.37
Flags can be combined, e.g. --positron-version 2026.03.0 --tag-series v0.37.
The script outputs each tag as OK or BAD with specific mismatches. Report:
Use -v / --verbose to show the full proposals list instead of just the count.
Use --pre-releases to also check date-based pre-release tags (skipped by default).
Positron proposals: 9 versioned (from src/vs/.../extensionsApiProposals.ts)
Code OSS version: 1.109.0
Checking recent tag series for engine compatibility:
v0.36 -> ^1.108.0 (compatible)
v0.37 -> ^1.109.0 (compatible)
v0.38 -> ^1.110.0 (needs Code OSS >= 1.110.0)
--- v0.37 ---
Releases (10 tags):
BAD v0.37.9
chatHooks@6 (not in Positron)
chatParticipantPrivate@13 (Positron has chatParticipantPrivate@12)
BAD v0.37.6
chatHooks@6 (not in Positron)
OK v0.37.5
Pre-releases (41 tags, skipped -- use --pre-releases to check)
Latest compatible release: v0.37.5