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

Prepare Invokta Release

by vinilana in vinilana/invokta

Prepare Invokta versioned releases on dedicated release branches with synchronized package metadata, changelog and validation evidence, complete repository gates, and one cohesive commit.

MITAuto-check passedDevelopment

Install Prepare Invokta Release

skills CLI
$ npx skills add vinilana/invokta --skill prepare-invokta-release -a claude-code

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

GitHub CLI
$ gh skill install vinilana/invokta prepare-invokta-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/vinilana/invokta.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prepare-invokta-release .claude/skills/prepare-invokta-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
prepare-invokta-release
GitHub stars
139
Token cost
~1.1k tokens
SKILL.md length
543 words
Files
2
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

Prepare Invokta versioned releases on dedicated release branches with synchronized package metadata, changelog and validation evidence, complete repository gates, and one cohesive commit.

  • Works in 5 steps: Read… → Inspect the working tree, current… → Select the next semantic version from… → …
  • Asked to prepare
  • SKILL.md covers Establish the release branch, Synchronize release metadata, Run the release gates and Commit and hand off
  • Calls yarn and git

What it does

Prepare Invokta Release is an agent skill from vinilana/invokta. Prepare Invokta versioned releases on dedicated release branches with synchronized package metadata, changelog and validation evidence, complete repository gates, and one cohesive commit. Use when asked to prepare, cut, stage, or validate an Invokta release or release candidate.

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 Development, covering Changelog and release notes. The repository describes itself as: A TypeScript framework for reusable domain AI capabilities across direct, CLI, and MCP transports. The licence is MIT.

When your agent uses it

  • Asked to prepare
  • Validate an Invokta release
  • Release candidate

Example prompts

  • “/prepare-invokta-release”

Workflow steps

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

  1. Read .agents/skills/invokta-delivery/SKILL.md, docs/README.md, the
  2. Inspect the working tree, current branch, local and remote mainline refs,
  3. Select the next semantic version from the compatibility of the Unreleased
  4. Confirm the intended mainline base. If local main and origin/main
  5. Create or switch to chore/release-X.Y.Z from the confirmed mainline before

What it can do on your machine

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

    • yarn
    • git

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

  • Network

    No URLs in SKILL.md. Its commands use yarn and 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

Prepare Invokta Release loads about 1.1k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 543 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 vinilana/invokta at commit f1e2f04, republished under its MIT licence (© vinilana). 543 words, ~1,102 tokens.

Download SKILL.mdSave it as .claude/skills/prepare-invokta-release/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
prepare-invokta-release
description
Prepare Invokta versioned releases on dedicated release branches with synchronized package metadata, changelog and validation evidence, complete repository gates, and one cohesive commit. Use when asked to prepare, cut, stage, or validate an Invokta release or release candidate.

Prepare an Invokta Release

Establish the release branch

  1. Read .agents/skills/invokta-delivery/SKILL.md, docs/README.md, the release gates in docs/implementation-plan-and-acceptance-criteria.md, and the ADRs represented by the unreleased changes.
  2. Inspect the working tree, current branch, local and remote mainline refs, recent tags, CHANGELOG.md, and commits since the latest release. Preserve unrelated changes and stop if they make the release slice ambiguous.
  3. Select the next semantic version from the compatibility of the Unreleased changes and the repository's prior release policy. Request a decision when the correct increment is ambiguous.
  4. Confirm the intended mainline base. If local main and origin/main diverge, resolve the base explicitly before continuing.
  5. Create or switch to chore/release-X.Y.Z from the confirmed mainline before editing any release file. Never prepare or commit a release on main.

Synchronize release metadata

  1. Bump the root version and every public package version to X.Y.Z.
  2. Bump every exact internal @invokta/* dependency pin in public packages and examples. Update version assertions and protocol client self-identification constants that intentionally track the release.
  3. Search the repository for the previous version. Classify every match as current release metadata, historical release documentation, or an unrelated dependency before changing it.
  4. Synchronize committed example lockfiles. For unpublished Invokta packages, derive integrity values from the exact locally packed X.Y.Z artifacts; never retain old integrity hashes or invent new ones. Recheck the hashes if package contents change afterward.
  5. Move the Unreleased notes under ## [X.Y.Z] - YYYY-MM-DD, update the Unreleased comparison base, and add the release link. Preserve historical entries and write all release content in English.
  6. Refresh docs/validation-record.md only with evidence produced during this release run, including the review date, accepted ADRs, test totals, coverage, and audit count.

Do not change a public contract merely to prepare the release. If preparation reveals a missing or conflicting contract, stop and apply $invokta-contract-review before continuing.

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

Run the release gates

Run the canonical commands from a clean dependency state:

sh
yarn install --frozen-lockfile --non-interactive
yarn run check
yarn audit
cd apps/docs
yarn install --frozen-lockfile --non-interactive
yarn validate

Return to the repository root and then:

  1. Update the validation record with the exact results and stage only the cohesive release slice.
  2. Inspect git diff --cached, run git diff --cached --check, and confirm all package versions and internal pins equal X.Y.Z.
  3. Run yarn release:verify. This verifier archives the Git index, so release files must be staged first; unstaged changes are intentionally excluded.
  4. If a packed consumer tries to resolve @invokta/*@X.Y.Z from the registry, treat that as a pre-publish verifier defect. Record the failing command as RED, install the complete matching local tarball dependency closure in the fixture, and rerun the verifier for GREEN.
  5. Rerun yarn run check after any executable verifier change. Reinspect the staged diff and confirm the working tree has no unstaged release changes.

Do not claim readiness while any typecheck, lint, formatting, test, coverage, build, audit, documentation, package, or diff gate fails.

Commit and hand off

  1. Create one commit named chore(release): prepare X.Y.Z on the release branch.
  2. Confirm main still points to the confirmed mainline, the release branch contains the commit, and the working tree is clean.
  3. Report the version, branch, commit hash, RED/GREEN evidence or metadata-only exception, validation results, risks, and pending work.
  4. Do not tag, push, publish packages, or create a pull request unless the user explicitly requests that separate action.

© vinilana, 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/prepare-invokta-release of vinilana/invokta.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit f1e2f04

Compare with similar skills

Prepare Invokta 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.

Prepare Invokta Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prepare Invokta Release this skillvinilana/invokta139—~1.1kAutomated safety check: PassMIT
Simple Englishmoeru-ai/airi50k2 repos~4.6kAutomated safety check: PassMIT
StarRocks Release NotesStarRocks/starrocks12k—~1.9kAutomated safety check: NotesApache-2.0
Cutting A ReleaseTriliumNext/Trilium38k—~3.2kAutomated safety check: PassAGPL-3.0
Mole CLI Release Flowtw93/Mole70k—~2.6kAutomated safety check: PassGPL-3.0
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Simple English

    moeru-ai/airi

    Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.

    50k GitHub starsUsed in 2 repos~4.6k tokens
    DevelopmentAuto-check passed

  • StarRocks Release Notes

    StarRocks/starrocks

    Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.

    12k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check: notes

  • Cutting A Release

    TriliumNext/Trilium

    A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.

    38k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Mole CLI Release Flow

    tw93/Mole

    Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.

    70k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Release

    PrefectHQ/fastmcp

    Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.

    28k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed

More from vinilana/invokta

  • Invokta Delivery

    vinilana/invokta

    Deliver Invokta milestones and work items with TDD, adherence to versioned contracts and architecture, complete validation, and one cohesive commit per work item.

    139 GitHub stars~894 tokensUpdated 4 days ago
    Auto-check passed

  • Invokta Contract Review

    vinilana/invokta

    Review Invokta contracts for public APIs, acceptance criteria, errors, invariants, operational limits, compatibility, and architectural boundaries.

    139 GitHub stars~854 tokensUpdated 4 days ago
    Auto-check passed

Categories

Questions about Prepare Invokta Release

What does Prepare Invokta Release do?

Prepare Invokta versioned releases on dedicated release branches with synchronized package metadata, changelog and validation evidence, complete repository gates, and one cohesive commit. Prepare Invokta Release is an agent skill from vinilana/invokta. Prepare Invokta versioned releases on dedicated release branches with synchronized package metadata, changelog and validation evidence, complete repository gates, and one cohesive commit.

When should I use Prepare Invokta Release?

Prepare Invokta Release fits situations like: asked to prepare; validate an Invokta release; release candidate.

How do I install Prepare Invokta Release in Claude Code?

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

How do I install Prepare Invokta Release in Codex?

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

Can I use Prepare Invokta 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 vinilana/invokta --skill prepare-invokta-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/prepare-invokta-release, .gemini/skills/prepare-invokta-release, .github/skills/prepare-invokta-release and .opencode/skills/prepare-invokta-release in your project.

What does Prepare Invokta Release need to run?

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

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

Prepare Invokta 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 Prepare Invokta 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 Prepare Invokta Release?

Skills that share tags, products or a category with Prepare Invokta Release: Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars), Cutting A Release (TriliumNext/Trilium, 38k stars) and Mole CLI Release Flow (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prepare Invokta Release?

vinilana (a GitHub user) maintains it in vinilana/invokta, which has 139 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 5, 2026.

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