releaselisted

# Release Skill Create a new version release using prefixed tag-based workflow for monorepo plugins. ## When to Use - User explicitly asks to "release" or "create a release" - User asks to "publish" or "ship" a new version - User asks to "tag" a version - User says "let's release v0.2.0" or similar ## Plugin Identification This is a **monorepo** with multiple plugins. First, identify which plugin to release: | Plugin | Version File | Tag Format | Example | |--------|-------------|------------|---------| | **Stash Downloader** | `plugins/stash-downloader/package.json` | `downloader-vX.Y.Z` | `downloader-v0.5.2` | | **Stash Browser** | `plugins/stash-browser/package.json` | `browser-vX.Y.Z` | `browser-v0.1.0` | If the user doesn't specify, ask which plugin to release. If both changed, release each separately. ## Pre-Release Checklist Before creating a release, verify: 1. On dev branch: `git branch --show-current` 2. No uncommitted changes: `git status` 3. Type-check passes: `npm run type-check` 4. Lint passes: `npm run lint` 5. Tests pass: `npm test -- --run` 6. Build succeeds: `npm run build` ## Release Process (Tag-Based) ### Step 1: Determine Version Bump 1. **Check current version**: Read the plugin's `package.json` version field 2. **Review commits since last tag**: `git log $(git describe --tags --match "downloader-v*" --abbrev=0)..HEAD --oneline` (or `browser-v*` for Browser) 3. **Determine bump type**: | Commit Types | Bump | Example | |--------------|-----