/gstack-document-release
Update or audit OPC documentation after code changes. Use when behavior, setup, CLI flags, desktop workflow, provider support, or plugin surfaces changed.
$ npx -y skills add LING71671/Open-ClaudeCode --skill gstack-document-release --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/gstack-document-release
Context preview
The summary Claude sees to decide when to auto-load this skill.
Update or audit OPC documentation after code changes. Use when behavior, setup, CLI flags, desktop workflow, provider support, or plugin surfaces changed.
SKILL.md
gstack-document-release.SKILL.mdname: 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
gstack-document-release
Use this skill to keep docs aligned with shipped behavior.
Workflow
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.
Documentation Standard
Prefer Diataxis-style clarity:
- Tutorial: first successful path
- How-to: task-specific steps
- Reference: exact flags, settings, APIs, schemas
- Explanation: architecture and tradeoffs
Output
Report:
- Docs changed
- Behavior now documented
- Commands or snippets verified
- Known documentation gaps left for later
完整开源的 Claude Code 项目 - 基于 Anthropic 官方源码重建 🌐 Languages: 中文 | English
Repo: LING71671/Open-ClaudeCode
Other skills on open-claudecode.
- /claude-opus-4-5-migration
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 codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT
Open skill - /frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Open skill - /gstack-cso
Security audit workflow for OPC code, providers, plugins, Electron surfaces, local HTTP bridges, filesystem access, and command execution.
Open skill - /gstack-investigate
Systematic root-cause debugging for OPC work. Use when there is a bug, crash, regression, failing command, flaky behavior, provider issue, or unexplained output. Requires evidence before fixes.
Open skill - /gstack-qa-only
Read-only QA report for an OPC desktop flow, CLI command, local URL, staging URL, or documented user journey. Does not modify code.
Open skill - /gstack-review
Pre-landing code review for the current OPC branch or diff. Use before merging, shipping, or asking whether a change is safe.
Open skill