smithery/jeremylongshore

windsurf-release-automation

Execute automate release processes with semantic versioning. Activate when users mention "release automation", "version bump", "changelog generation", "semantic release", or "publish release". Handles release engineering automation. Use when working with windsurf release automation functionality. Trigger with phrases like "windsurf release automation", "windsurf automation", "windsurf". '

Installation

$ npx skills add smithery/jeremylongshore --skill windsurf-release-automation

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/jeremylongshore · top by installs.

npx skills add smithery/jeremylongshore

Browse all from smithery/jeremylongshore

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
LicenseMIT
CompatibilityDesigned for Claude Code
Allowed toolsRead,Write,Edit,Bash(cmd:*)
Declared agents claude-code windsurf

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,014 B
  • docs SUMMARY.md 426 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Windsurf Release Automation

Overview

This skill enables automated release workflows within Windsurf using Cascade AI. It analyzes commits to determine semantic version bumps, generates comprehensive changelogs, manages Git tags, and publishes releases.

Prerequisites

  • Windsurf IDE with Cascade enabled
  • Git repository with commit history
  • Conventional commits or consistent commit format
  • npm/yarn/pnpm for JavaScript projects (or equivalent)
  • CI/CD pipeline for automated publishing (optional)

Instructions

  1. Configure Version Strategy
  2. Set Up Automation
  3. Prepare Release
  4. Execute Release
  5. Post-Release Tasks

See ${CLAUDESKILLDIR}/references/implementation.md for detailed implementation guide.

Output

  • Updated version in package.json
  • Generated CHANGELOG.md entry
  • Git tag for release version
  • Published package to registry
  • Release notes for distribution

Error Handling

See ${CLAUDESKILLDIR}/references/errors.md for comprehensive error handling.

Examples

See ${CLAUDESKILLDIR}/references/examples.md for detailed examples.

Resources