claude-opus-4-5-migrat…
Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their…
Read-only QA report for an OPC desktop flow, CLI command, local URL, staging URL, or documented user journey. Does not modify code.
Claude Code
$ npx -y skills add LING71671/Open-ClaudeCode --skill gstack-qa-only --agent claude-code
Codex
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-qa-only -a codex -y
Cursor
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-qa-only -a cursor -y
Gemini CLI
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-qa-only -a gemini-cli -y
GitHub Copilot
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-qa-only -a github-copilot -y
OpenCode
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-qa-only -a opencode -y
Windsurf
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-qa-only -a windsurf -y
name: gstack-qa-only description: Read-only QA report for an OPC desktop flow, CLI command, local URL, staging URL, or documented user journey. Does not modify code. allowed-tools: - Read - Grep - Glob - Bash
Use this skill to test behavior and report bugs without changing files.
1. Define the target flow, environment, and success criteria. 2. Run the app, command, or URL using the existing project workflow. 3. Exercise the primary path and at least two edge paths. 4. Capture objective evidence: command output, logs, screenshots if available, request/response details, or UI text. 5. Separate product bugs from setup failures.
When testing OPC desktop, prefer:
Return a QA report:
Do not edit code in this workflow.
Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their…
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web…
Security audit workflow for OPC code, providers, plugins, Electron surfaces, local HTTP bridges, filesystem access, and command…
Update or audit OPC documentation after code changes. Use when behavior, setup, CLI flags, desktop workflow, provider support, or…
Systematic root-cause debugging for OPC work. Use when there is a bug, crash, regression, failing command, flaky behavior,…
Pre-landing code review for the current OPC branch or diff. Use before merging, shipping, or asking whether a change is safe.
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.