Release logo

Release

Community
cubetribe
release

Release sprint workflow: version-at-release via tooling, CHANGELOG [Unreleased] flow, release invariant checks, tags, GitHub Releases, RCs. Authoritative law: docs/orchestrator/VERSIONING.md

Overview

Publishercubetribe
RepositoryClaudeCode_GodMode-On
Skill namerelease
Stars
54
Forks
10
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by cubetribe on GitHub. Read the source before you install it.

Installation

Install the Release AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/cubetribe/ClaudeCode_GodMode-On/tree/main/skills/release
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/cubetribe/ClaudeCode_GodMode-On.git /tmp/ClaudeCode_GodMode-On
mkdir -p .claude/skills
cp -r /tmp/ClaudeCode_GodMode-On/skills/release .claude/skills/release
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Release in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Release on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Release is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Release & Versioning (v9.0.0)

Authoritative law: docs/orchestrator/VERSIONING.md (ADR-004). This skill is the operational cheat sheet. The pre-v8.5 "Version-First" rule (bump before work) is retired.

The model in one look

plans/vX.Y.Z/PLAN.md + sprint files      ← what ships (target version = working label)
CHANGELOG.md [Unreleased]                ← accumulates one entry per sprint (writer: @scribe)
VERSION                                  ← single source of truth, written ONCE per release
scripts/version-bump.js <type>           ← bump + [Unreleased] promotion + full touchpoint sync
scripts/sync-version.js --check          ← all ~12 touchpoint files consistent?
scripts/release-check.js                 ← VERSION == CHANGELOG == tag == release?
release/vX.Y.Z → PR → merge commit       ← CI: release-consistency.yml
.github/workflows/release-tag.yml        ← annotated tag + DRAFT GitHub Release

During normal sprints

  • Do NOT touch VERSION, do NOT create dated CHANGELOG headings.
  • Each sprint ends with @scribe adding its entry under ## [Unreleased] (serialized).
  • Record the sprint's Version Relevance (none/patch/minor/major) in its sprint file.

Release sprint checklist

  • All sprints done; working tree clean; [Unreleased] non-empty
  • node scripts/release-check.js — resolve inherited drift (phantom releases) FIRST
  • Bump type = highest sprint Version Relevance (semver table in VERSIONING.md)
  • node scripts/version-bump.js <type> (use --dry-run first)
  • npm run version:check green, npm run release:check green (on release/* branch)
  • Release PR with the promoted CHANGELOG entry; CI green
  • Explicit user permission, then merge (merge commit)
  • Verify tag + draft release created (release-tag workflow); publish the draft
  • ROADMAP entry → released

Pre-releases / Release Candidates

  • Tag vX.Y.Z-rc.N (annotated) + GitHub Release with the pre-release flag.
  • CHANGELOG headings never carry the rc suffix — RC feedback rolls into the final entry.

Hard rules

  • NEVER reuse a version number (version-bump checks git tags).
  • NEVER push, tag, or publish without explicit user permission.
  • Only the release sprint writes VERSION; only @scribe writes CHANGELOG.
  • A merged release PR without tag+release is a defect — release-check.js flags it.

CC_GodMode — © 2025–2026 Dennis Westermann (dennis-westermann.de). Proprietary — not open source. Free for private, non-commercial use; redistribution or re-hosting outside GitHub is prohibited; attribution required. Official source: github.com/cubetribe/ClaudeCode_GodMode-On. See LICENSE.

Frequently asked questions

What does the Release AI skill do?

Release sprint workflow: version-at-release via tooling, CHANGELOG [Unreleased] flow, release invariant checks, tags, GitHub Releases, RCs. Authoritative law: docs/orchestrator/VERSIONING.md

Why use Release on TypingMind?

Because you install it once and use it with any model. Release is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Release in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cubetribe/ClaudeCode_GodMode-On/tree/main/skills/release. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Release?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Release?

As many as you like. As long as a model supports skills, you can use Release with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Release AI skill free?

It is published on GitHub by cubetribe. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇