windsurf-release-automation

jeremylongshore's avatarfrom jeremylongshore

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.

⭐878stars🔀101forks📁View on GitHub🕐Updated Jan 4, 2026

When & Why to Use This Skill

This Claude skill automates the end-to-end software release process by implementing semantic versioning and conventional commit analysis. It streamlines version bumping, generates comprehensive changelogs, and manages Git tags, ensuring a consistent and reliable release engineering workflow within the Windsurf IDE. By leveraging Cascade AI, it reduces manual overhead and minimizes human error in the software development lifecycle.

Use Cases

  • Automated Version Bumping: Automatically calculate the next semantic version (patch, minor, or major) by analyzing commit history and identifying breaking changes.
  • Changelog Generation: Maintain an up-to-date CHANGELOG.md by automatically categorizing new features, bug fixes, and improvements from commit messages.
  • Git Tag Management: Create and push standardized Git tags for every release to maintain a clear and searchable version history in the repository.
  • Package Distribution: Streamline the publishing of updated packages to registries like npm, yarn, or pnpm as part of a continuous delivery pipeline.
  • Workflow Standardization: Enforce conventional commit standards across development teams to ensure predictable and automated release cycles.
name"windsurf-release-automation"
description|
allowed-tools"Read,Write,Edit,Bash(cmd:*)"
version1.0.0
licenseMIT
author"Jeremy Longshore <jeremy@intentsolutions.io>"

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