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…
Update or audit OPC documentation after code changes. Use when behavior, setup, CLI flags, desktop workflow, provider support, or plugin surfaces changed.
Claude Code
$ npx -y skills add LING71671/Open-ClaudeCode --skill gstack-document-release --agent claude-code
Codex
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-document-release -a codex -y
Cursor
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-document-release -a cursor -y
Gemini CLI
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-document-release -a gemini-cli -y
GitHub Copilot
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-document-release -a github-copilot -y
OpenCode
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-document-release -a opencode -y
Windsurf
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-document-release -a windsurf -y
name: gstack-document-release description: Update or audit OPC documentation after code changes. Use when behavior, setup, CLI flags, desktop workflow, provider support, or plugin surfaces changed. allowed-tools: - Read - Grep - Glob - Bash - Edit - Write
Use this skill to keep docs aligned with shipped behavior.
1. Inspect the current diff and identify user-visible changes. 2. Map affected docs: README files, plugin READMEs, desktop docs, examples, settings, and scripts. 3. Check for stale commands, paths, model/provider names, environment variables, screenshots, and troubleshooting text. 4. Update only the docs that are directly affected. 5. Verify links, commands, and JSON snippets where practical.
Prefer Diataxis-style clarity:
Report:
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…
Systematic root-cause debugging for OPC work. Use when there is a bug, crash, regression, failing command, flaky behavior,…
Read-only QA report for an OPC desktop flow, CLI command, local URL, staging URL, or documented user journey. Does not modify…
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.