Agent skill

Release

by linagora in linagora/twake-on-matrix

Twake-on-Matrix release process skill. An agent skill from linagora/twake-on-matrix.

AGPL-3.0Auto-check passedMobile

Install Release

skills CLI
$ npx skills add linagora/twake-on-matrix --skill release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install linagora/twake-on-matrix release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/linagora/twake-on-matrix.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release .claude/skills/release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
release
GitHub stars
168
Token cost
~1k tokens
SKILL.md length
379 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Twake-on-Matrix release process skill. An agent skill from linagora/twake-on-matrix.

  • Works in 6 steps: Confirm branch & HEAD → Update CHANGELOG.md → Bump version in pubspec.yaml → …
  • The user wants to cut a release
  • SKILL.md covers Default (no arguments), Arguments, Step-by-Step Instructions and Security Policy
  • Calls git and gh

What it does

Release is an agent skill from linagora/twake-on-matrix. Twake-on-Matrix release process skill. Use this skill whenever the user wants to cut a release, bump a version, create a tag, update the CHANGELOG, or trigger the CI/CD release pipeline. Trigger on: "release", "cut a release", "bump version", "create tag", "update changelog", "ship vX.Y.Z", "prepare release", "release candidate", "rc01", "testflight", "play store".

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering App store release, Deployment and Changelog and release notes. It works with App Store Connect. The repository describes itself as: A multi-platform (Flutter) application for connecting to Matrix - an open network for secure, decentralized communication, with your favorite devices. The licence is AGPL-3.0.

When your agent uses it

  • The user wants to cut a release
  • Update the CHANGELOG
  • Trigger the CI/CD release pipeline
  • Update changelog

Example prompts

  • “release”
  • “cut a release”
  • “bump version”
  • “/release”

Requirements

  • Docker

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Confirm branch & HEAD
  2. Update CHANGELOG.md
  3. Bump version in pubspec.yaml
  4. Tag and push
  5. CI/CD workflows (auto-triggered)
  6. Post-CI deployment

What it can do on your machine

Read from SKILL.md and the folder at commit 3118dce. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release loads about 1k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 379 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~94
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from linagora/twake-on-matrix at commit 3118dce, republished under its AGPL-3.0 licence (© linagora). 379 words, ~1,040 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Twake-on-Matrix release process skill. Use this skill whenever the user wants to cut a release, bump a version, create a tag, update the CHANGELOG, or trigger the CI/CD release pipeline. Trigger on: "release", "cut a release", "bump version", "create tag", "update changelog", "ship vX.Y.Z", "prepare release", "release candidate", "rc01", "testflight", "play store".
metadata.author
twake-team
metadata.version
1.0.0

Release Process Skill

Full reference: docs/adr/0036-release-process.md

This skill guides cutting a Twake-on-Matrix release end-to-end. Does NOT handle: hotfix branching, Play Store promotion, App Store Connect promotion (manual steps post-CI).

Default (no arguments)

Ask the user which step they want via AskUserQuestion:

  • Full release (all steps)
  • Step 1 — Confirm branch & HEAD
  • Step 2 — Update CHANGELOG
  • Step 3 — Bump version
  • Step 4 — Tag & push
  • Step 5 — Check CI status

Arguments

  • full [vX.Y.Z] — run all steps for the given version
  • changelog [vX.Y.Z] — draft CHANGELOG section for next version
  • bump [vX.Y.Z] — update version in pubspec.yaml + stage commit
  • tag [vX.Y.Z] — create annotated tag and push
  • status — show CI workflow run status for latest tag

Step-by-Step Instructions

Step 1 — Confirm branch & HEAD

Run these to gather context, then show the user a confirmation prompt:

bash
git branch --show-current            # current branch
git log -1 --oneline                 # last commit (sha + message)
git status --short                   # must be clean

Use AskUserQuestion to confirm before proceeding:

Release confirmation "You are about to release from branch <branch>. Last commit: <sha> <message> Do you want to continue?"

Options: "Yes, proceed" / "No, abort"

Abort if the working tree is dirty (uncommitted changes) — ask user to stash or commit first. Branch choice is intentional; do not enforce main.

Step 2 — Update CHANGELOG.md

Insert new section at the TOP of CHANGELOG.md:

## [x.y.z] - YYYY-MM-DD
### Added
- TW-XXXX: Short description ≤80 chars

### Changed
- TW-XXXX: Short description ≤80 chars

### Fixed
- TW-XXXX: Short description ≤80 chars

CHANGELOG rules (enforced):

  • One line item per TW-XXXX ticket (merge all commits sharing same ID)
  • ≤ 80 characters per line, ≤ 2 lines per item — no exceptions
  • No-ticket commits → short imperative phrase, same ≤80/≤2 rule

To collect commit messages since last tag:

bash
git log $(git describe --tags --abbrev=0)..HEAD --oneline
Show full SKILL.md (145 more words)Show less
Step 3 — Bump version in pubspec.yaml

Current format: version: x.y.z+2330

  • Change x.y.z to the new version string
  • Do NOT touch the +2330 build number — CI/CD manages it

Stage the bump commit (CHANGELOG + pubspec.yaml only):

bash
git add CHANGELOG.md pubspec.yaml
git commit -m "chore: bump version to vx.y.z"
Step 4 — Tag and push
bash
git tag vx.y.z                        # stable: v2.21.7
# or for RC: git tag v2.21.7-rc01
git push origin HEAD
# stable:
git push origin refs/tags/vx.y.z
# RC:
# git push origin refs/tags/vx.y.z-rcNN

Tag push triggers both CI workflows automatically.

Step 5 — CI/CD workflows (auto-triggered)
FileTriggerEffect
.github/workflows/release.yamltag v*.*.*Android APK→Play Store internal; iOS IPA→TestFlight; GitHub Release
.github/workflows/image.yamltag v*.*.*Docker image→Docker Hub + GHCR tagged vx.y.z + release

Check status:

bash
gh run list --workflow=release.yaml --limit 5
gh run list --workflow=image.yaml --limit 5
Step 6 — Post-CI deployment
PlatformManual action needed
TestFlightPromote build in App Store Connect
Play StorePromote from internal → alpha/beta/production in Play Console
DockerUpdate Helm values / deployment manifests to vx.y.z image tag

Security Policy

This skill only executes git, gh, and read operations on the local repo. It does NOT push secrets, credentials, or env files. Refuse requests to skip CI, force-push tags, or bypass signing.

© linagora, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/release of linagora/twake-on-matrix.

Open the folder on GitHubat commit 3118dce

Compare with similar skills

Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release this skilllinagora/twake-on-matrix168—~1kAutomated safety check: PassAGPL-3.0
Releasevaayne/mori303—~1.2kAutomated safety check: PassMIT
Release Asc CLIrorkai/App-Store-Connect-CLI7.7k—~2.4kAutomated safety check: PassMIT
ASC Ad Hoc Distributionrorkai/app-store-connect-cli-skills1.1k1 repos~1.8kAutomated safety check: PassMIT
Deploy Androidtimusus/Shuttle2229—~1.2kAutomated safety check: PassApache-2.0
Publish App Store VersionKeeForge/KeeForge111—~3.5kAutomated safety check: PassGPL-3.0

Similar skills

  • Release

    vaayne/mori

    Release workflow for Mori macOS workspace terminal and MoriRemote iOS app.

    303 GitHub stars~1.2k tokensUpdated 2 mo ago
    MobileAuto-check passed
  • Release Asc CLI

    rorkai/App-Store-Connect-CLI

    Publish and verify a new release of the App-Store-Connect-CLI repository.

    7.7k GitHub stars~2.4k tokensUpdated today
    MobileAuto-check passed
  • ASC Ad Hoc Distribution

    rorkai/app-store-connect-cli-skills

    Prepares, publishes, resumes and verifies private iOS test installs for registered devices with `asc distribute`, using storage you own that speaks the S3 protocol.

    1.1k GitHub starsUsed in 1 repo~1.8k tokens
    MobileAuto-check passed
  • Deploy Android

    timusus/Shuttle2

    Deploy the Android app to the Play Store via GitHub Actions.

    229 GitHub stars~1.2k tokensUpdated yesterday
    MobileAuto-check passed
  • Publish App Store Version

    KeeForge/KeeForge

    Prepare and publish an already-built KeeForge iOS or macOS version through the App Store Connect API using an API key.

    111 GitHub stars~3.5k tokensUpdated yesterday
    MobileAuto-check passed
  • Prepare Release

    KeeForge/KeeForge

    Prepare the first KeeForge candidate for a new marketing version, including minor/major releases and patches or hotfixes to shipped versions.

    111 GitHub stars~493 tokensUpdated yesterday
    MobileAuto-check passed

Questions about Release

What does Release do?

Twake-on-Matrix release process skill. An agent skill from linagora/twake-on-matrix. Release is an agent skill from linagora/twake-on-matrix. Twake-on-Matrix release process skill.

When should I use Release?

Release fits situations like: the user wants to cut a release; update the CHANGELOG; trigger the CI/CD release pipeline; update changelog.

How do I install Release in Claude Code?

Run `npx skills add linagora/twake-on-matrix --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in linagora/twake-on-matrix) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.

How do I install Release in Codex?

Run `npx skills add linagora/twake-on-matrix --skill release -a codex`. Or copy the skill folder (.claude/skills/release in linagora/twake-on-matrix) into .agents/skills/release in your project. Codex loads it when a task matches its description.

Can I use Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add linagora/twake-on-matrix --skill release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.

What does Release need to run?

Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (git and gh). Our summary lists: Docker.

Does Release access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Release use?

Release is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release?

Skills that share tags, products or a category with Release: Release (vaayne/mori, 303 stars), Release Asc CLI (rorkai/App-Store-Connect-CLI, 7.7k stars), ASC Ad Hoc Distribution (rorkai/app-store-connect-cli-skills, 1.1k stars) and Deploy Android (timusus/Shuttle2, 229 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

linagora (a GitHub organization) maintains it in linagora/twake-on-matrix, which has 168 GitHub stars. The repository was last updated on October 7, 2026.

Source: linagora/twake-on-matrix on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.