tmt-release

Manages tmux-team release lines, version synchronization, and prerelease verification procedures.

11|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/wkh237/tmux-team --skill tmt-release-wkh237
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tmt-release
Source: https://github.com/wkh237/tmux-team/tree/main/.agents/skills/tmt-release
Command: npx skills add https://github.com/wkh237/tmux-team --skill tmt-release-wkh237

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintaining long-lived release branches, promoting versions, and verifying native release artifacts involves many error-prone steps where a wrong branch mutation or premature publication can break the release line. This Skill encodes the branch policy, promotion gates, and verification procedures so release work stays consistent and auditable. ## Core Features & Use Cases - Long-lived branch policy enforcement: Keeps main as the active v5 line and v4 as a maintenance line anchored at a specific commit, with rules against force-pushing or repointing long-lived branches. - Release verification guidance: Directs archive, installer, upgrade, bootstrap, and publication work through the native release verification guide, including cargo-dist manifest ownership and multi-platform alpha checks. - Authorization boundaries: Treats tags, GitHub Releases, npm publishing, and dist-tags as separate operations requiring explicit authorization, never assumed. - Use Case: When preparing a v5.0.0-alpha release, use this Skill to confirm all four native verifiers pass on the reviewed commit, verify the draft-to-published GitHub release attestation, and only then update README installation instructions. ## Quick Start Ask the agent to prepare the tmux-team v5 prerelease readiness check following the release verification guide before any publication step.

Frequently Asked Questions about tmt-release

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

FAQPage Schema
How do I promote the tmux-team v5 release line?

Promotion requires passing Code quality, Unit tests, and Docker E2E checks on the recorded reviewed commit. For a public native alpha, all four final native verifiers must pass, and publication uses an immutable draft-to-published GitHub release with attestation verification.

How do I create a v4 maintenance fix for tmux-team?

A v4 maintenance fix requires a tracked issue, a dedicated branch and worktree, and a reviewable pull request. The v4 branch is rooted at commit 7056679dfa816a1acef8e7c978cf1733a578115b and is only created when explicitly requested.

Does this skill publish releases or npm packages automatically?

No. Tags, GitHub Releases, npm publishing, and npm dist-tags are separate operations requiring explicit authorization. The skill never assumes permission for any publication step.

Where is the native version number defined for tmux-team?

The native version is owned by rust/Cargo.toml and exposed through Cargo's package version, with no TypeScript fallback. Developer package versions and public release instructions must stay consistent when versions change.

Can I force-push or repoint the main or v4 branches?

No. Before any branch mutation you must verify the relevant remote refs and ancestry, and force-pushing or repointing a long-lived line is never allowed. This protects the integrity of the release lines.