release

Automate UnityCTL releases with automated version bumps and GitHub changelogs.

15|2|Updated Nov 18, 2025
One-click install
npx skills add https://github.com/DirtybitGames/unityctl --skill release-dirtybitgames
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/DirtybitGames/unityctl/tree/main/.claude/skills/release
Command: npx skills add https://github.com/DirtybitGames/unityctl --skill release-dirtybitgames

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and error-prone process of creating new releases for the unityctl project, ensuring consistency and saving valuable developer time.

Core Features & Use Cases

  • Automated Version Bumping: Intelligently determines the next version number (major, minor, patch) based on code changes.
  • Build & Artifact Management: Executes build scripts and updates necessary project files.
  • Git Integration: Handles commits, tagging, and pushing to the remote repository.
  • GitHub Release Creation: Generates draft releases on GitHub with automated changelogs.
  • Use Case: Streamline the release cycle from code commit to published release notes, reducing manual overhead and potential mistakes.

Quick Start

Use the release skill to create a new patch version for unityctl.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub releases for a Unity package project?

You can automate GitHub releases by using a skill that analyzes code changes, bumps versions in Directory.Build.props, manages git commits and tags, and generates draft GitHub releases with changelogs.

How does automated version bumping work for unityctl builds?

Automated version bumping for unityctl works by analyzing code changes to intelligently determine the correct semantic version increment, updating the version properties in Directory.Build.props and Unity package files accordingly.

Do I need to manually write changelogs when creating a GitHub release?

You do not need to manually write changelogs for a GitHub release. The automation generates the changelog content and populates a draft release on GitHub automatically based on the analyzed code changes.

Can I use this to handle git commits and tagging during the release process?

Yes, you can use this to handle git integration during the release process. It automatically commits the updated version files, creates the necessary git tags, and pushes these changes to your remote repository.

What is the best way to manage versioning in Directory.Build.props before a release?

The best way to manage versioning in Directory.Build.props is through automated release scripts that evaluate code modifications and apply the correct major, minor, or patch version bumps directly to the file.