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

by gocronx-team in gocronx-team/gocron

Prepare or publish a safe gocron release by choosing a SemVer bump, updating AppVersion and migrations, invoking the complete verification gate, committing, checking CI, and creating an annotated tag.

MITAuto-check passedProduct & Project Management

Install Release

skills CLI
$ npx skills add gocronx-team/gocron --skill release -a claude-code

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

GitHub CLI
$ gh skill install gocronx-team/gocron 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/gocronx-team/gocron.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/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
808
Token cost
~1.1k tokens
SKILL.md length
582 words
Files
2
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

Prepare or publish a safe gocron release by choosing a SemVer bump, updating AppVersion and migrations, invoking the complete verification gate, committing, checking CI, and creating an annotated tag.

  • Works in 4 steps: Establish the release → Update version and migrations → Pass the mandatory gate → …
  • Asked to release
  • SKILL.md covers Compatibility evidence…, Performance evidence (required…, 1. Establish the release and 2. Update version and migrations, plus 2 more sections
  • Calls git

What it does

Release is an agent skill from gocronx-team/gocron. Prepare or publish a safe gocron release by choosing a SemVer bump, updating AppVersion and migrations, invoking the complete verification gate, committing, checking CI, and creating an annotated tag. Use when asked to release, 发版, bump the version, cut a release, 打 tag, or assess release readiness.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Product & Project Management, covering Feature launches and release readiness. The repository describes itself as: distributed scheduled task management system. The licence is MIT.

When your agent uses it

  • Asked to release
  • Bump the version
  • Assess release readiness

Example prompts

  • “/release”

Requirements

  • Docker

Workflow steps

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

  1. Establish the release
  2. Update version and migrations
  3. Pass the mandatory gate
  4. Publish only when requested

What it can do on your machine

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

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

  • Network

    No URLs in SKILL.md. Its commands use git, 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 1.1k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 582 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~77
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 gocronx-team/gocron at commit e76e9da, republished under its MIT licence (© gocronx-team). 582 words, ~1,112 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
release
description
Prepare or publish a safe gocron release by choosing a SemVer bump, updating AppVersion and migrations, invoking the complete verification gate, committing, checking CI, and creating an annotated tag. Use when asked to release, 发版, bump the version, cut a release, 打 tag, or assess release readiness.

Release gocron

Keep preparation separate from publication. A version-bump request authorizes the local version edit and verification, but not a push, merge, or tag unless the user also asks to publish the release.

Compatibility evidence (required)

Before tagging, record evidence for every affected case:

  • N frontend/client with N-1 and N backend;
  • N backend with N-1 and N frontend/client;
  • N gocron with N-1 and N gocron-node, in both directions;
  • N upgrading an existing SQLite, MySQL, and PostgreSQL database;
  • rolling upgrade with temporary N/N-1 HA members when HA is affected.

Use automated compatibility tests, previous-version fixtures, or a documented reproducible check. Current/current tests and a fresh install are not enough. If a case cannot remain compatible, stop before tagging: obtain explicit approval, use a major version, and document migration, deployment order, rollback limits, and recovery.

Performance evidence (required when affected)

  • Identify affected hot paths and record the workload, data size, environment, command, baseline, and release-candidate result.
  • Compare latency, throughput, memory/allocations, goroutines, query count, database writes, and migration duration as applicable.
  • Include SQLite concurrent read/write and lock behavior when database write frequency, logging, polling, migrations, or scheduler state changed.
  • Require a benchmark or regression test for a material fix or risk. Do not publish a material unexplained regression; an accepted tradeoff needs the user's explicit approval and release-note disclosure.

1. Establish the release

  • Inspect the current branch, working tree, latest v* tag, AppVersion, and changes since the latest release.
  • Never develop or commit directly on master; create or use a release branch.
  • Choose the SemVer bump from user-facing changes: features bump minor and fixes or chores bump patch. Ask when the intended version cannot be inferred safely. Honor an explicit version supplied by the user.
  • Check that the target version and vX.Y.Z tag do not already exist.
Show full SKILL.md (288 more words)Show less

2. Update version and migrations

  • Update AppVersion in cmd/gocron/gocron.go.
  • Update helm/gocron/Chart.yaml appVersion to the same application version. Increment the Chart version whenever the packaged Chart changes; the chart release workflow skips versions that have already been published.
  • If the release changes the schema, add the model to the Install tables slice where applicable, append a unique migration version id and matching upgradeForNNN function in internal/models/migration.go, add it to the upgrade chain, and add a migration test.
  • Derive the migration id using the repository's existing version conversion convention. Confirm it with ToNumberVersion; do not guess or reuse an id.
  • If there is no schema change, do not add an empty migration.
  • For migrations that rewrite existing data, tell the user to back up the database and include the impact in release notes.

3. Pass the mandatory gate

Invoke $verify and require every backend, frontend, lint, test, and Docker check to pass. Do not commit, merge, push, or tag while any check is failed, skipped, or unavailable.

Review the final diff and confirm AppVersion, Helm appVersion and Chart version, migration id, tests, and user-facing release notes agree.

4. Publish only when requested

  • Commit with chore(release): bump version to X.Y.Z; keep the subject under 100 characters and omit Co-Authored-By.
  • Push the branch and merge it into master according to the repository's normal review process.
  • Confirm the GitHub Actions CI run for the exact release commit is green.
  • Confirm local master, remote master, and the green CI SHA all identify the same commit.
  • Create and push an annotated tag: git tag -a vX.Y.Z -m "vX.Y.Z" followed by git push origin vX.Y.Z.
  • Confirm the tag-triggered release workflow starts successfully.

Never move or replace an existing release tag, and never tag an unverified commit.

© gocronx-team, 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 1 other file in .agents/skills/release of gocronx-team/gocron.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit e76e9da

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 skillgocronx-team/gocron808—~1.1kAutomated safety check: PassMIT
.NET MAUI Release Readinessdotnet/maui23k—~15kAutomated safety check: PassMIT
Release ValidationMesh-LLM/mesh-llm3.5k—~2.6kAutomated safety check: PassApache-2.0
Final Release Reviewopenai/openai-agents-python30k—~5.4kAutomated safety check: PassMIT
Final Release Reviewopenai/openai-agents-js3.9k—~4kAutomated safety check: PassMIT
Acceptance Demo GeneratorChachamaru127/claude-code-harness3.2k—~3.4kAutomated safety check: NotesMIT

Similar skills

  • .NET MAUI Release Readiness

    dotnet/maui

    Official

    Produces evidence-backed ship-readiness verdicts for .NET MAUI Servicing Releases and Previews, and drafts public-safe release handoff pages from the result.

    23k GitHub stars~15k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Release Validation

    Mesh-LLM/mesh-llm

    A skill your agent uses when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally…

    3.5k GitHub stars~2.6k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Final Release Review

    openai/openai-agents-python

    Official

    Assess a Python SDK release candidate or release plan against the previous release and recommend ship or block.

    30k GitHub stars~5.4k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Final Release Review

    openai/openai-agents-js

    Official

    Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.

    3.9k GitHub stars~4k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Acceptance Demo Generator

    Chachamaru127/claude-code-harness

    Renders a single HTML page showing each acceptance criterion as verified or not, with a ship, wait, or reject recommendation for non-engineers.

    3.2k GitHub stars~3.4k tokensUpdated 4 days ago
    Product & Project ManagementAuto-check: notes

  • Schematic

    blader/schematic

    Reverse engineer a detailed product and technical specification document from a git branch's implementation.

    240 GitHub stars~2.2k tokensUpdated 7 mo ago
    Product & Project ManagementAuto-check passed

More from gocronx-team/gocron

All 8 skills in this repo

  • Migration

    gocronx-team/gocron

    Create, review, or verify gocron database migrations across SQLite, MySQL, and PostgreSQL.

    808 GitHub stars~1.1k tokensUpdated 6 days ago
    Auto-check passed

  • Security Check

    gocronx-team/gocron

    Audit or harden gocron security across Go, pnpm workspaces, containers, authentication, authorization, secrets, command execution, SSRF, and dependency vulnerabilities.

    808 GitHub stars~690 tokensUpdated 6 days ago
    Auto-check passed

  • Dependency Update

    gocronx-team/gocron

    Review, apply, verify, or merge gocron dependency updates from Dependabot or manual requests.

    808 GitHub stars~891 tokensUpdated 6 days ago
    Auto-check passed

  • Scheduler Change

    gocronx-team/gocron

    Safely implement, diagnose, or review changes to gocron scheduling and task execution.

    808 GitHub stars~1.1k tokensUpdated 6 days ago
    Auto-check passed

  • API Feature

    gocronx-team/gocron

    Implement or review an end-to-end gocron HTTP API change. An agent skill from gocronx-team/gocron.

    808 GitHub stars~1.2k tokensUpdated 6 days ago
    Auto-check passed

  • Release

    gocronx-team/gocron

    Cut a gocron release — bump AppVersion, align the migration version id, run the full CI check locally, and tag only when everything is green.

    808 GitHub stars~586 tokensUpdated 6 days ago
    Auto-check passed

Categories

Questions about Release

What does Release do?

Prepare or publish a safe gocron release by choosing a SemVer bump, updating AppVersion and migrations, invoking the complete verification gate, committing, checking CI, and creating an annotated tag. Release is an agent skill from gocronx-team/gocron. Prepare or publish a safe gocron release by choosing a SemVer bump, updating AppVersion and migrations, invoking the complete verification gate, committing, checking CI, and creating an annotated tag.

When should I use Release?

Release fits situations like: asked to release; bump the version; assess release readiness.

How do I install Release in Claude Code?

Run `npx skills add gocronx-team/gocron --skill release -a claude-code`. Or copy the skill folder (.agents/skills/release in gocronx-team/gocron) 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 gocronx-team/gocron --skill release -a codex`. Or copy the skill folder (.agents/skills/release in gocronx-team/gocron) 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 gocronx-team/gocron --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). Our summary lists: Docker.

Does Release access the network?

SKILL.md contains no URLs. Its commands use git, 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 MIT 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 1.1k tokens (SKILL.md is roughly 4.4k 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: .NET MAUI Release Readiness (dotnet/maui, 23k stars), Release Validation (Mesh-LLM/mesh-llm, 3.5k stars), Final Release Review (openai/openai-agents-python, 30k stars) and Final Release Review (openai/openai-agents-js, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

gocronx-team (a GitHub organization) maintains it in gocronx-team/gocron, which has 808 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 2, 2026.

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