---
name: Document Release
slug: document-release
category: Writing
description: Document Release keeps README files, examples, settings, and related docs aligned with code changes. Use it after behavior, CLI flags, provider support, or plugin surfaces change.
github: "https://github.com/LING71671/Open-ClaudeCode/tree/main/plugins/gstack-workflows/skills/gstack-document-release"
language: TypeScript
stars: 945
forks: 1224
install: "npx degit https://github.com/LING71671/Open-ClaudeCode/tree/main/plugins/gstack-workflows/skills/gstack-document-release ~/.claude/skills/gstack-document-release"
installs_to: ~/.claude/skills/gstack-document-release
source_path: plugins/gstack-workflows/skills/gstack-document-release/SKILL.md
collection_size: 15
category_size: 1012
collection_url: "https://dirskills.com/collections/LING71671/Open-ClaudeCode"
added: 2026-08-21T05:15:31.441Z
last_synced: 2026-08-21T05:15:31.441Z
canonical_url: "https://dirskills.com/skills/document-release"
---

# Document Release

Document Release keeps README files, examples, settings, and related docs aligned with code changes. Use it after behavior, CLI flags, provider support, or plugin surfaces change.

**Install:**

```bash
npx degit https://github.com/LING71671/Open-ClaudeCode/tree/main/plugins/gstack-workflows/skills/gstack-document-release ~/.claude/skills/gstack-document-release
```

## README

# 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