playbooks

home / skills / jeremylongshore / claude-code-plugins-plus-skills / windsurf-release-automation

windsurf-release-automation skill

/plugins/saas-packs/skill-databases/windsurf/skills/windsurf-release-automation

This skill automates windsurf release workflows by applying semantic versioning, changelog generation, and publishing releases from commits.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill windsurf-release-automation

Review the files below or copy the command above to add this skill to your agents.

Files (5)
SKILL.md
2.0 KB
---
name: "windsurf-release-automation"
description: |
  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".
allowed-tools: "Read,Write,Edit,Bash(cmd:*)"
version: 1.0.0
license: MIT
author: "Jeremy Longshore <[email protected]>"
---

# 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. Cascade understands conventional commits to automatically categorize changes and highlight breaking changes for proper version increments.

## 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 `{baseDir}/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 `{baseDir}/references/errors.md` for comprehensive error handling.

## Examples

See `{baseDir}/references/examples.md` for detailed examples.

## Resources

- [Windsurf Release Automation](https://docs.windsurf.ai/features/release)
- [Semantic Release Documentation](https://semantic-release.gitbook.io/)
- [Conventional Commits](https://www.conventionalcommits.org/)

Overview

This skill automates release engineering for Windsurf projects using semantic versioning and conventional commits. It inspects commit history to determine version bumps, generates changelog entries, creates Git tags, and publishes releases to registries. The goal is reliable, repeatable releases integrated into CI/CD pipelines.

How this skill works

The skill analyzes commits according to Conventional Commits rules to classify changes as patch, minor, major, or breaking. It updates project version files (for example package.json), generates or appends a structured CHANGELOG.md entry, creates a Git tag, and can push and publish artifacts to configured registries. It integrates with Windsurf/Cascade automation and can be invoked manually or from CI with configurable strategies.

When to use it

  • When you need automated semantic versioning and changelog generation
  • Before merging release branches or tagging main for production release
  • To remove manual errors from version bumps and release notes
  • When publishing packages to npm or other registries
  • When you want CI-driven, repeatable release pipelines

Best practices

  • Adopt Conventional Commits across the team for consistent change classification
  • Define and document your version strategy (major/minor/patch rules) before enabling automation
  • Run the automation in a dry-run mode first to validate changelog and tag outputs
  • Integrate with CI/CD so publishing occurs only after successful tests and approval gates
  • Keep release configuration in repository and version-controlled for traceability

Example use cases

  • Automate version bumps and changelog generation on merge to main
  • Create a CI job that runs the skill, tags the repo, and publishes packages on successful builds
  • Generate release notes for product managers and publish a GitHub/GitLab release automatically
  • Perform a dry-run to preview the next version and changelog during a release planning meeting
  • Manage multiple package releases in monorepos by scanning commit scopes and bumping affected packages

FAQ

What commit format is required?

Conventional Commits or a consistent commit message format is required for reliable classification; otherwise you can configure custom parsing rules.

Can I preview changes before publishing?

Yes. Use the dry-run mode to generate the changelog and proposed version without modifying files, tags, or publishing artifacts.