release-workflow

Standard release workflow - Test, tag, push.

IndexedMIT

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/vincent119-release-workflow

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Standard release workflow - Test, tag, push. Supports Go, Python, Node.js, Bash, YAML projects.

Use cases: testing, productivity

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/release-workflow

What's inside

Skill name: release-workflow
Description: Standard release workflow - Test, tag, push. Supports Go, Python, Node.js, Bash, YAML projects.
License: MIT
Instructions: 82 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Release Workflow

Standard process for releasing new versions across different project types.

## Workflow Steps

### 1. Check Git Status

Ensure clean working directory:

```bash
git status --porcelain
```

### 2. Run Tests

Execute tests based on project type:

```bash
# Go
go test -v ./...

# Python
pytest

# Node.js
npm test

# Bash
bash -n script.sh

# YAML
yamllint .
```

### 3. Determine Version

Review existing tags and decide next version:

```bash
git tag --sort=-v:refname | head -n 5
```

**Ask user**: "What should the next version tag be? (e.g., v1.0.1)"

### 4. Create Tag

```bash
git tag <VERSION>
```

### 5. Push Tag

```bash
git push origin <VERSION>
```

### 6. Verify (Optional)

```bash
git ls-remote --tags origin | grep <VERSION>
```

## Version Guidelines

| Change Type | Version Bump | Example |
|------------|--------------|---------|
| Breaking changes | Major | v1.0.0 → v2.0.0 |
| New features | Minor | v1.0.0 → v1.1.0 |
| Bug fixes | Patch | v1.0.0 → v1.0.1 |

## Common Patterns

```bash
# Full workflow one-liner
git status --porcelain && \
go test -v ./... && \
git tag v1.0.1 && \
git push origin v1.0.1
```

From vincent119/ai-rules-kit, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Sep 8, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/vincent119/ai-rules-kit
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from vincent119

Cite this page

release-workflow skill. Agent Mart. https://agentmart.dev/skills/vincent119-release-workflow (last updated 2026-10-24)