Back to skills
SkillHub ClubShip Full StackFull Stack

release

Create a new release by bumping version, committing, and pushing a git tag. Use when the user wants to release a new version (e.g., "release 1.0.1", "release patch", "make a release", "bump version and release", "create version 2.0.0").

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars
18
Hot score
87
Updated
March 20, 2026
Overall rating
C3.0
Composite score
3.0
Best-practice grade
A92.0

Install command

npx @skill-hub/cli install joe-re-eyes-on-claude-code-release

Repository

joe-re/eyes-on-claude-code

Skill path: .claude/skills/release

Create a new release by bumping version, committing, and pushing a git tag. Use when the user wants to release a new version (e.g., "release 1.0.1", "release patch", "make a release", "bump version and release", "create version 2.0.0").

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: joe-re.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

  • Install release into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
  • Review https://github.com/joe-re/eyes-on-claude-code before adding release to shared team environments
  • Use release for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: release
description: Create a new release by bumping version, committing, and pushing a git tag. Use when the user wants to release a new version (e.g., "release 1.0.1", "release patch", "make a release", "bump version and release", "create version 2.0.0").
allowed_tools:
  - Bash
  - Read
  - Edit
---

# Release Workflow

Create a new release for Eyes on Claude Code.

## Arguments

The user may specify a version in one of these formats:
- **Explicit version**: `1.0.1`, `2.0.0`
- **Semver bump**: `patch`, `minor`, `major`

If not specified, ask the user which version type they want.

## Workflow

### 1. Determine New Version

If explicit version provided, use it directly.

If semver bump keyword provided:
```bash
# Get current version from package.json
node -p "require('./package.json').version"
```

Then calculate:
- `patch`: 1.0.0 → 1.0.1
- `minor`: 1.0.0 → 1.1.0
- `major`: 1.0.0 → 2.0.0

### 2. Update Version in Files

Update version in both files:

**package.json:**
```json
{
  "version": "NEW_VERSION"
}
```

**src-tauri/tauri.conf.json:**
```json
{
  "version": "NEW_VERSION"
}
```

### 3. Commit Version Bump

```bash
git add package.json src-tauri/tauri.conf.json
git commit -m "Bump version to NEW_VERSION"
```

### 4. Create and Push Tag

```bash
git tag vNEW_VERSION
git push origin main vNEW_VERSION
```

### 5. Report Success

Output the following:
- New version number
- Git tag created
- GitHub Actions URL: `https://github.com/joe-re/claude-code-session-manager/actions`
- Remind user to check the draft release on GitHub after the build completes

## Example User Requests

- "release 1.0.1"
- "release patch"
- "make a minor release"
- "bump version to 2.0.0 and release"
- "create a new release"

## Notes

- Always ensure working directory is clean before running
- GitHub Actions will automatically build for all platforms (macOS, Linux, Windows)
- The release is created as a draft - user must publish it manually on GitHub
release | SkillHub