New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Release Sync

by iii-hq in iii-hq/workers

Organize worker release tags into Linear release waves — one team document plus one release/<date label per same-day batch of worker releases, with shipped MOT issues labeled and linked.

Apache-2.0Auto-check passedDevelopment

Install Release Sync

skills CLI
$ npx skills add iii-hq/workers --skill release-sync -a claude-code

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

GitHub CLI
$ gh skill install iii-hq/workers release-sync --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/iii-hq/workers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release-sync .claude/skills/release-sync && 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-sync
GitHub stars
113
Token cost
~1.1k tokens
SKILL.md length
552 words
Files
1
Skills in repo
19
Repo updated
First seen
Licence
Apache-2.0

At a glance

Organize worker release tags into Linear release waves — one team document plus one release/<date label per same-day batch of worker releases, with shipped MOT issues labeled and linked.

  • Works in 5 steps: Collect pending tags → Group into waves → Gather changes per tag → …
  • Development work in your project
  • SKILL.md covers Prerequisites, 1. Collect pending tags, 2. Group into waves and 3. Gather changes per tag, plus 3 more sections
  • Calls git and gh

What it does

Release Sync is an agent skill from iii-hq/workers. Organize worker release tags into Linear release waves — one team document plus one release/<date label per same-day batch of worker releases, with shipped MOT issues labeled and linked. Use after cutting worker releases, or any time to catch up or backfill. Trigger: /release-sync [tag ...]

Its SKILL.md is about 1.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 Development. It works with Git. The licence is Apache-2.0.

When your agent uses it

  • Development work in your project

Example prompts

  • “/release-sync”

Workflow steps

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

  1. Collect pending tags
  2. Group into waves
  3. Gather changes per tag
  4. Write to Linear (per wave)
  5. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 72ae6ab. 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 Sync loads about 1.1k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 552 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~1.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 iii-hq/workers at commit 72ae6ab, republished under its Apache-2.0 licence (© iii-hq). 552 words, ~1,062 tokens.

Download SKILL.mdSave it as .claude/skills/release-sync/SKILL.md (or your agent's skills folder).
name
release-sync
description
Organize worker release tags into Linear release waves — one team document plus one release/<date> label per same-day batch of worker releases, with shipped MOT issues labeled and linked. Use after cutting worker releases, or any time to catch up or backfill. Trigger: /release-sync [tag ...]

Release sync — worker tags → Linear release waves

One wave = all <worker>/vX.Y.Z tags created on the same UTC day. Each wave maps to one Linear document on team iii titled Release YYYY-MM-DD — the combined release note, one ## <worker> vX.Y.Z section per worker — plus a child label YYYY-MM-DD under the team label group release, applied to every shipped issue. (This is the free-plan model; Linear's native Releases feature requires Business+.)

Prerequisites

  • Linear MCP tools (the claude.ai Linear connector).
  • Team label group release on team iii (create once with create_issue_label, isGroup: true, if missing).

1. Collect pending tags

bash
git fetch --tags origin
git for-each-ref 'refs/tags/*/v*' --sort=creatordate \
  --format='%(refname:short) %(creatordate:short)'
  • Only consider tags that still exist on origin (git ls-remote --tags origin on doubt) — rolled-back local tags don't count.
  • With arguments: sync exactly those tags.
  • Without arguments: a tag is already synced iff it appears in the header tag list of an existing wave document (list_documents, query Release, team iii — each doc's first line lists its tags; that list is the idempotency record). Pending = every worker tag not found.
  • Skip -dry-run. tags. Include prereleases (-rc.N, -beta.N) and label them in the note.

2. Group into waves

Group pending tags by tag creation date (UTC day). If more than 3 waves would be written (typical of a first backfill), show the plan (date → tags) and get user confirmation before writing anything.

3. Gather changes per tag

  • Previous tag of the same worker: git tag -l '<worker>/v*' --sort=-v:refname → the entry after the current one.
  • Commits: git log --format='%h %s%n%b' <prev>..<tag> -- <worker>/ (first release of a worker: git log <tag> -- <worker>/).
  • Extract MOT-\d+ from subjects and bodies. For PR references (#N) with no MOT id, gh pr view N --json title,body and scan those too.
  • Judgment attachments: if a change clearly implements a known issue that was never referenced, find it via list_issues (title terms, team iii) and read the issue to verify it matches before labeling. Never invent or guess identifiers; when unsure, leave it off and flag it in the report.
Show full SKILL.md (227 more words)Show less

4. Write to Linear (per wave)

  1. Label: child label YYYY-MM-DD under group release (team iii, create_issue_label with parent: release; skip if it exists).
  2. Label every verified issue: read the issue's current labels first and pass the union to save_issue — never drop existing labels.
  3. Worker labels: also apply flat worker:<name> team labels (worker:shell, worker:console, ...) matching the worker commit ranges that referenced the issue — create missing ones lazily; same union rule. Flat, NOT a label group: Linear group children are mutually exclusive, and one issue often spans several workers.
  4. Document: save_document on team iii titled Release YYYY-MM-DD (update the existing one if present — look it up via list_documents). First line: the full tag list (idempotency record — always complete) and the wave label name. Body: a ## <worker> vX.Y.Z section per tag (collapse multiple same-day tags of one worker into ## <worker> vA → vB), 2–5 bullets each — what shipped, why it matters, breaking changes called out as Breaking:, shipped issues linked by URL. Plain changelog register; no internal workflow chatter.

5. Report

Table: wave date → document URL → tags → labeled issues. Flag tags where no issues were found and any judgment attachments made.

Rules

  • Never change issue status, never create issues, never remove existing labels from an issue.
  • Re-runs must converge: a late same-day tag merges into the existing wave document and the note is regenerated to include it.

© iii-hq, Apache-2.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-sync of iii-hq/workers.

Open the folder on GitHubat commit 72ae6ab

Compare with similar skills

Release Sync 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 Sync compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Sync this skilliii-hq/workers113—~1.1kAutomated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything86k1 repos~1.2kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Codebase Knowledge Graph Q&A

    Egonex-AI/Understand-Anything

    Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.

    86k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • Understand Explain

    Egonex-AI/Understand-Anything

    Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.

    86k GitHub starsUsed in 1 repo~1.3k tokens
    DevelopmentAuto-check passed

More from iii-hq/workers

All 19 skills in this repo

  • Cron

    iii-hq/workers

    Schedule any registered function on a 6- or 7-field cron expression with the standalone cron worker.

    113 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Email

    iii-hq/workers

    Send and read email from the iii engine — SMTP send, IMAP read, and real-time IDLE push as a subscribable trigger type.

    113 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • HTTP

    iii-hq/workers

    Expose registered functions as HTTP endpoints with the standalone http worker.

    113 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Kanban

    iii-hq/workers

    File-backed kanban board: create, read, move and comment on tickets by key or uuid, assign agent profiles, and wake on comments through the kanban:comment trigger instead of polling.

    113 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Pubsub

    iii-hq/workers

    Fire-and-forget topic pub/sub: broadcast an event with publish and every matching subscribe trigger receives it.

    113 GitHub stars~989 tokensUpdated today
    Auto-check passed

  • State

    iii-hq/workers

    Shared, adapter-backed key/value store addressed by scope and key, with a reactive state trigger so other functions can run on every create, update, or delete without polling.

    113 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Release Sync

What does Release Sync do?

Organize worker release tags into Linear release waves — one team document plus one release/<date label per same-day batch of worker releases, with shipped MOT issues labeled and linked. Release Sync is an agent skill from iii-hq/workers. Organize worker release tags into Linear release waves — one team document plus one release/<date label per same-day batch of worker releases, with shipped MOT issues labeled and linked.

When should I use Release Sync?

Release Sync fits situations like: development work in your project.

How do I install Release Sync in Claude Code?

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

How do I install Release Sync in Codex?

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

Can I use Release Sync 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 iii-hq/workers --skill release-sync -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-sync, .gemini/skills/release-sync, .github/skills/release-sync and .opencode/skills/release-sync in your project.

What does Release Sync need to run?

Going by SKILL.md and its folder, Release Sync needs the command-line tools its instructions call (git and gh).

Does Release Sync 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 Sync 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 Sync use?

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

How many tokens does Release Sync use?

About 1.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 Sync?

Skills that share tags, products or a category with Release Sync: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 86k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Sync?

iii-hq (a GitHub organization) maintains it in iii-hq/workers, which has 113 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 8, 2026.

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