skills.rest
kousaku-maron
kousaku-maronCOMMUNITY
Explore all skills by this author →
GitHub

tauri-release

Create and push Git version tags for Tauri desktop applications.

Updated Feb 18, 2026
Search Tags:#automation#git#versioning#deployment#release#tauri
One-click install
npx skills add https://github.com/kousaku-maron/Carbon --skill tauri-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tauri-release
Source: https://github.com/kousaku-maron/Carbon/tree/main/.claude/skills/tauri-release
Command: npx skills add https://github.com/kousaku-maron/Carbon --skill tauri-release

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of creating and pushing version tags for desktop applications, ensuring a consistent and reliable release workflow.

Core Features & Use Cases

  • Version Tagging: Manages version numbers according to defined rules and creates Git tags.
  • Release Automation: Pushes tags to the remote repository, triggering automated release workflows.
  • Use Case: When you've completed a new version of your Tauri application and are ready to deploy, this Skill helps you properly tag the release commit and push it to GitHub.

Quick Start

Use the tauri-release skill to create and push the next version tag for the application.

Frequently Asked Questions about tauri-release

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

FAQPage Schema
How do I automate version tagging and pushing for Tauri desktop app releases?▼

Automate Tauri desktop app releases by creating and pushing Git version tags according to rules defined in tauri.conf.json. The workflow checks branch status, pulls latest changes, verifies tag existence, and pushes the tag to trigger automated release pipelines.

What is the best way to manage versioning rules for Tauri application Git tags?▼

Tauri application versioning is managed through rules defined in the SKILL.md and tauri.conf.json files. The automation reads these configurations to determine the correct version number before creating the corresponding Git tag for the release commit.

Do I need Git installed to use Tauri release automation?▼

Git is required as a dependency for Tauri release automation. The process relies on Git workflows to check branch status, pull the latest changes, verify existing tags, and push the new version tag to the remote repository to trigger deployments.

Does the Tauri release workflow check for existing tags before pushing?▼

The Tauri release workflow verifies tag existence before pushing to prevent conflicts. It ensures the local branch is up to date by pulling the latest changes, then checks if the target version tag already exists in the repository history before creating and pushing a new one.

Can I trigger automated GitHub release workflows by pushing Tauri version tags?▼

Pushing Tauri version tags to the remote repository triggers automated release workflows. Once the versioning rules are applied and the tag is created from the updated branch, the push operation activates downstream GitHub Actions or similar CI/CD release pipelines.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
Conceptual-MachinesConceptual-Machines
195

release

Create and push a v-prefixed git tag on the main branch.

Official
Intermediate
EdgeAppEdgeApp
1

staging-cherry-pick

Cherry-pick non-merge commits from pull requests onto a staging branch.

Official
Advanced
amanmprojectsamanmprojects

bump-version

Bump semantic versions in package.json and create v-prefixed Git tags.

Community
Intermediate