Agent skill

Release New Version

by fastrepl in fastrepl/anarlog

Coordinate focused release skills to prepare, publish, and verify Anarlog stable desktop releases and affected public surfaces, plus mobile distribution when requested.

MITAuto-check passed

Install Release New Version

skills CLI
$ npx skills add fastrepl/anarlog --skill release-new-version -a claude-code

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

GitHub CLI
$ gh skill install fastrepl/anarlog release-new-version --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/fastrepl/anarlog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-new-version .claude/skills/release-new-version && 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-new-version
GitHub stars
9.5k
Token cost
~2.2k tokens
SKILL.md length
1,002 words
Files
3 (incl. references)
Skills in repo
32
Repo updated
First seen
Licence
MIT

At a glance

Coordinate focused release skills to prepare, publish, and verify Anarlog stable desktop releases and affected public surfaces, plus mobile distribution when requested.

  • Works in 6 steps: Record the requested version,… → Read the five surface skills and current… → When desktop is in scope, follow Desktop… → …
  • SKILL.md covers Scope and authorization, Release Surface Review, Execution order and Final Checks
  • Calls gh

What it does

Release New Version is an agent skill from fastrepl/anarlog. Coordinate focused release skills to prepare, publish, and verify Anarlog stable desktop releases and affected public surfaces, plus mobile distribution when requested.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/desktop.md` and `references/mobile.md`).

The repository describes itself as: Open source Granola AI Alternative. The licence is MIT.

Example prompts

  • “/release-new-version”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Record the requested version, platforms/channel, prior published versions, and
  2. Read the five surface skills and current workflows. Implement and validate
  3. When desktop is in scope, follow Desktop release procedures for native CI,
  4. Publish required backward-compatible hosted dependencies through Release API
  5. After verified app availability, complete Release Docs publication.
  6. Complete each affected skill's shipped/live checks and the release record below.

What it can do on your machine

Read from SKILL.md and the folder at commit 385e117. 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:

    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use 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 New Version loads about 2.2k tokens when it runs, and up to ~6.9k if it reads all its reference files. Until then it costs about 47 tokens; SKILL.md has 1,002 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.9k

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 fastrepl/anarlog at commit 385e117, republished under its MIT licence (© fastrepl). 1,002 words, ~2,211 tokens.

Download SKILL.mdSave it as .claude/skills/release-new-version/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
release-new-version
description
Coordinate focused release skills to prepare, publish, and verify Anarlog stable desktop releases and affected public surfaces, plus mobile distribution when requested.
metadata.internal
true

Release a New Version

Use this skill when preparing, publishing, or verifying an Anarlog release. This is the coordinator: read all five focused skills below for the surface review, then execute their required work within the requested release scope. The user does not need to invoke each skill or ask separately for the changelog. Repository paths are relative to the checkout root; workflow filenames below and in the child skills refer to .github/workflows/.

Scope and authorization

  • For desktop preparation or publication, require the user's explicit stable desktop version. For mobile-only distribution, require the mobile version and explicit store destination; no desktop version or desktop release work is required. Publish only a verified candidate merged into main, never the combined GitButler workspace. Nightly publication is retired; preserve historical tags and installed-client compatibility.
  • A desktop or mobile publication request includes its own changelog, affected public surfaces, and website publication. Desktop releases also include the existing Microsoft Store lane. Preparation alone does not authorize publication. Mobile submission requires an explicit destination. There is no Mac App Store release lane; do not recreate one.
  • Child skills inherit session authorization and scope. Continue already authorized publication without asking again. They do not authorize unrelated deployments, announcements, emails, customer-data resets, or store agreements.
  • Review every surface; update only those with drift. Keep API, website, plugin, and mobile versions independent. Record reuse evidence, inapplicability with a reason, or explicit user deferral with impact. Do not redeploy unchanged services merely to refresh timestamps. A website build before desktop publication cannot expose the new changelog and is not reusable evidence for that publication step.
  • Preserve the 2–3 working-day candidate use period, final stable package checks, exact source/provenance requirements, and downgrade compatibility in the desktop procedure. Honor an explicit owner exception without claiming the skipped checks occurred. Broad QA through qa-critical-ux or qa-cli-mcp-api is separate and runs only when requested; packaging and release verification remain required.

Release Surface Review

Review the full product diff since the previous published release of the requested product, not only each surface's own paths. Also compare each independently published surface with its live revision so previously unshipped changes are included. Implement required updates before freezing the candidate. Document intentional capability differences or explicit deferrals; do not silently omit CLI, MCP, or docs support for a new product feature.

SkillOwns
Release DocsChangelog preparation, website publication after the app release, live index/page checks, Mintlify guides, examples, and discovery.
Release APIAPI/generated contracts, hosted services, billing, hosted database, compatibility, deployment, and live operations.
Release CLICommands, help/output, shared agent access, packaged CLI, install/update path, and shared agent packages.
Release MCPLocal and hosted protocols, tools/resources, schemas, authentication, and shipped runtime checks.
Release TelemetryProduct events, crash reporting, consent/redaction, release attribution, delivery, and symbolication.

CLI and MCP share one agent-package review. Reuse evidence and publish shared packages once. Each skill returns decisions, candidate/published revisions, checks, live or artifact evidence, and unresolved work.

Show full SKILL.md (517 more words)Show less

Execution order

  1. Record the requested version, platforms/channel, prior published versions, and candidate source in the matching Linear release issue. Follow Anarlog workflow; keep one release record.
  2. Read the five surface skills and current workflows. Implement and validate needed changes, including the Desktop or Mobile changelog for each requested stream. Prepare Mobile notes before freeze; record availability only after verifying the build is available to the intended store/tester audience. Merge release preparation to main, then freeze its exact SHA. A new source change requires renewed affected verification; do not mix runs or artifacts from different candidates.
  3. When desktop is in scope, follow Desktop release procedures for native CI, CloudSync source rebuilds, staging use, first-attempt stable dry run, packaged verification, upgrade/restart, immutable tags, and publication. Follow Mobile store distribution only when requested.
  4. Publish required backward-compatible hosted dependencies through Release API before dependent clients. Publish other affected surfaces through their owning skills; verify actual workflow SHAs and terminal results.
  5. After verified app availability, complete Release Docs publication. For desktop, reuse a successful post-publication Linux APT web deploy that includes the notes; otherwise dispatch web_cd.yaml within the existing release authorization. Follow it to completion and verify the full version page and public index. For mobile, merge the verified availability record before the website build. Do not leave this for a user reminder, separate request, or later release.
  6. Complete each affected skill's shipped/live checks and the release record below. If a workflow fails, inspect gh run view <run-id> --log-failed. Report the concrete unfinished step; do not label the overall release complete while required publication or verification remains pending without explicit deferral.

Final Checks

Record applicable checks in the release issue with links to existing evidence rather than duplicate routine comments. For mobile-only distribution, mark desktop version, staging, artifacts, Desktop changelog, and desktop store checks not applicable; review affected shared surfaces and complete the mobile checks.

  • Explicit stable version, candidate SHA, staging run and actual-use evidence, owner exceptions, first-attempt dry-run and publish URLs/head SHAs.
  • Immutable desktop_v<version> tag, GitHub/CrabNebula publication, asset hashes/signatures, final stable install/upgrade/restart, and updater/download routes.
  • Packaged CLI version on each shipped platform, installer/update resolution, CLI/API CI and contracts, local stdio MCP and hosted MCP checks.
  • Hosted API, billing, and Postgres deployment/reuse decisions; source revisions, run URLs, versions where applicable, and affected live behavior.
  • Website deployment URL/SHA after app publication, changelog version URL and index content, published Mintlify docs/skill/LLM indexes, and agent-package/catalog version and installation evidence when affected.
  • Telemetry update/reuse decisions, consent checks, shipped version attribution, destination delivery and symbolication evidence where affected.
  • Microsoft Store submission versus certification/availability, Linux APT results versus AUR availability, and any pending external processing.
  • When mobile was requested: source/version, build IDs/numbers, hashes, submission URLs, TestFlight processing/group availability, Google Play track/version code, verified Mobile publication record, and live Mobile changelog page/index.
  • Reasons for unchanged/not-applicable surfaces, explicit deferrals and impact, native coverage gaps, unavailable checks, and unresolved incidents. Publication does not by itself establish customer recovery or fix every known incident.

App publication, overall release completion, and store approval are separate facts. Report them accurately; never make the user discover a missing publication.

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

Files

SKILL.md and 2 other files (references) in .agents/skills/release-new-version of fastrepl/anarlog.

  • SKILL.md
  • references/desktop.md
  • references/mobile.md

Open the folder on GitHubat commit 385e117

Compare with similar skills

Release New Version 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 New Version compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release New Version this skillfastrepl/anarlog9.5k—~2.2kAutomated safety check: PassMIT
Publishcode-yeongyu/oh-my-openagent70k—~5.5kAutomated safety check: WarnCustom licence
Social Publisheraffaan-m/ECC275k1 repos~1.1kAutomated safety check: PassMIT
Publishyc-software/qm15k—~2.2kAutomated safety check: WarnMIT
Social Publishingwshobson/agents40k—~914Automated safety check: PassMIT
PublishQ00/ouroboros6.2k—~2.7kAutomated safety check: PassMIT

Similar skills

  • Publish

    code-yeongyu/oh-my-openagent

    Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts.

    70k GitHub stars~5.5k tokensUpdated today
    DevOps & CloudAuto-check: warnings
  • Social Publisher

    affaan-m/ECC

    Agent-driven scheduling and publishing of social media posts across 13 platforms via SocialClaw.

    275k GitHub starsUsed in 1 repo~1.1k tokens
    Writing & ContentAuto-check passed
  • Publish

    yc-software/qm

    Publish a long-lived internal web app, site, or dashboard from the agent computer.

    15k GitHub stars~2.2k tokensUpdated today
    DevOps & CloudAuto-check: warnings
  • Social Publishing

    wshobson/agents

    Schedule and publish social media posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via the SocialClaw API.

    40k GitHub stars~914 tokensUpdated 3 days ago
    Writing & ContentAuto-check passed
  • Publish

    Q00/ouroboros

    Publish Seed specification as GitHub Issues for team-based project management

    6.2k GitHub stars~2.7k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • Audit Preparation

    sickn33/agentic-awesome-skills

    Audit preparation register: required document, period covered, request and receipt dates, preparer and reviewer, auditor queries and adjustments.

    47k GitHub starsUsed in 1 repo~5.3k tokens
    Legal & ComplianceAuto-check passed

More from fastrepl/anarlog

All 32 skills in this repo
  • But

    fastrepl/anarlog

    Use only in the Anarlog repository when the active checkout branch is exactly gitbutler/workspace.

    9.5k GitHub stars~5.8k tokensUpdated today
    Auto-check passed
  • Create PRs

    fastrepl/anarlog

    Use only in the Anarlog repository when the active checkout branch is exactly gitbutler/workspace.

    9.5k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Fix Ready PRs

    fastrepl/anarlog

    Inspect every open non-draft PR for CI failures and unresolved Cursor Bugbot findings, then fix them on the existing PR branches.

    9.5k GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • No Use Effect

    fastrepl/anarlog

    Avoid direct React useEffect usage when writing or reviewing React components and hooks.

    9.5k GitHub stars~825 tokensUpdated today
    Auto-check passed
  • QA Critical UX

    fastrepl/anarlog

    QA Anarlog's critical Pro user journey on a signed staging candidate — onboarding, responsive launch, microphone and system-audio capture, automated summaries, and cloud sync.

    9.5k GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Reactive Sqlite UI

    fastrepl/anarlog

    Build SQLite-backed reactive UI in apps/desktop using stable patterns for reads, selection, forms, writes, and loading states.

    9.5k GitHub stars~699 tokensUpdated today
    Auto-check passed

Questions about Release New Version

What does Release New Version do?

Coordinate focused release skills to prepare, publish, and verify Anarlog stable desktop releases and affected public surfaces, plus mobile distribution when requested. Release New Version is an agent skill from fastrepl/anarlog. Coordinate focused release skills to prepare, publish, and verify Anarlog stable desktop releases and affected public surfaces, plus mobile distribution when requested.

How do I install Release New Version in Claude Code?

Run `npx skills add fastrepl/anarlog --skill release-new-version -a claude-code`. Or copy the skill folder (.agents/skills/release-new-version in fastrepl/anarlog) into .claude/skills/release-new-version in your project. Claude Code loads it when a task matches its description.

How do I install Release New Version in Codex?

Run `npx skills add fastrepl/anarlog --skill release-new-version -a codex`. Or copy the skill folder (.agents/skills/release-new-version in fastrepl/anarlog) into .agents/skills/release-new-version in your project. Codex loads it when a task matches its description.

Can I use Release New Version 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 fastrepl/anarlog --skill release-new-version -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-new-version, .gemini/skills/release-new-version, .github/skills/release-new-version and .opencode/skills/release-new-version in your project.

What does Release New Version need to run?

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

Does Release New Version access the network?

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

Is Release New Version 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 New Version use?

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

How many tokens does Release New Version use?

About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.7k tokens, read only when the agent opens those files.

What are the alternatives to Release New Version?

Skills that share tags, products or a category with Release New Version: Publish (code-yeongyu/oh-my-openagent, 70k stars), Social Publisher (affaan-m/ECC, 275k stars), Publish (yc-software/qm, 15k stars) and Social Publishing (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release New Version?

fastrepl (a GitHub organization) maintains it in fastrepl/anarlog, which has 9,452 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 8, 2026.

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