t-release

Automate version bumps, release tagging, and pushing release commits to git remotes.

64|6|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/timzaak/web-dev-skills --skill t-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: t-release
Source: https://github.com/timzaak/web-dev-skills/tree/main/skills/t-release
Command: npx skills add https://github.com/timzaak/web-dev-skills --skill t-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bump project version numbers, create a git tag, and push the release commit to the remote repository, eliminating manual, error-prone steps in the release process.

Core Features & Use Cases

  • Automated version bumps across version files with validation.
  • Create standardized git tags (vX.Y.Z) and push release commits to the remote.
  • Enforce release checks (clean working tree, non-conflicting tags) before publishing.

Quick Start

Run the release script with a target version to publish a new release.

Frequently Asked Questions about t-release

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

FAQPage Schema
How do I automate git versioning and release tagging for my repository?

Automated git versioning and release tagging handles version bumps, creates standardized vX.Y.Z tags, and pushes release commits to the remote repository. It eliminates manual steps by validating version files and enforcing a clean working tree before publishing.

What checks are enforced before pushing a git release tag?

Before pushing a git release tag, the workflow enforces release checks for a clean working tree and non-conflicting tags. These validations ensure the repository state is stable and the semantic versioning tag does not already exist on the remote.

How do I bump version numbers across multiple files for a release?

To bump version numbers across files, the automation script applies the target semantic version to your configured version files. It then creates commit messages and release tags, coordinating the git workflow across backend and frontend components.

Can I use automated semantic versioning for coordinated backend and frontend releases?

Yes, automated semantic versioning supports coordinated git workflows across backend and frontend components. It applies version bumps and release tagging uniformly, ensuring both components share the same release commit and tag.

What happens if my git working tree is not clean during version bumping?

If your git working tree is not clean during version bumping, the release process will fail its validation checks. Enforcing a clean working tree prevents accidentally including uncommitted changes in the release commit and tag.