Release Engineering

Community

thiientv

release-engineering

Prepares and controls software releases with risk classification, CI quality gates, artifact provenance, feature flags, staged rollout, measurable promotion and rollback thresholds, post-deploy verification, and cleanup. Use for deployment pipelines, launch readiness, canaries, production rollout, release automation, or rollback planning. Not for merely merging a completed development branch or proving one local change.

Overview

Publisher	thiientv
Repository	`godmode`
Skill name	`release-engineering`
Stars	99
Forks	76
Bundled files	3
License	MIT
Links	Skill source Repository Homepage

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.
3 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by thiientv on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/thiientv/godmode/tree/main/skills/release-engineering
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.

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/thiientv/godmode.git /tmp/godmode
mkdir -p .claude/skills
cp -r /tmp/godmode/skills/release-engineering .claude/skills/release-engineering

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Release Engineering 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 Engineering 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 Engineering 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 Engineering

Turn a release into a sequence of evidence-backed decisions rather than one irreversible event.

Build the release contract

Record the artifact/version, environments, owner, change scope, affected users, data or contract changes, dependencies, risk class, maintenance window, and success metrics. Use release-record.md for the go/no-go and rollout record.

Establish gates

Require checks proportional to risk: build and tests, contract and migration proof, security findings, performance budgets, smoke paths, accessibility or visual checks, artifact signing/provenance, monitoring, and a tested recovery path. A green generic pipeline is not proof of the release's critical behavior.

Roll out safely

Separate deployment from exposure with a flag or routing control when practical.
Start with internal, shadow, canary, or low-percentage traffic.
Compare errors, latency, saturation, business outcomes, and support signals against a pre-release baseline.
Promote only after the observation window and all gates pass.
Roll back or disable immediately when a predefined threshold is crossed.
Verify recovery, communicate status, and preserve the timeline.

For canaries and production observation windows, use post-deploy-verification.md. Confirm the deployed build marker, run critical browser journeys through browser-testing, and record each promote, hold, or rollback decision against fresh baseline evidence.

Use immutable artifacts across environments. Keep release credentials out of logs and command lines. Require explicit authority for production mutation.

Close the release

Verify critical paths after deployment, monitor delayed jobs and regional effects, remove stale flags and compatibility paths on schedule, update release notes, and create owned follow-ups for non-blocking debt. Never substitute a successful deployment command for an observation window. Use incident-response if live impact begins and safe-migrations for stateful cutovers.

Completion condition

The intended artifact reached the intended audience, promotion evidence and remaining limits are recorded, rollback readiness was real, and temporary release controls have owners and expiry dates.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Release Engineering AI skill do?

Why use Release Engineering on TypingMind?

Because you install it once and use it with any model. Release Engineering 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 Engineering in TypingMind?

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

Which AI models can use Release Engineering?

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 Engineering?

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

Is the Release Engineering AI skill free?

Yes. It is published on GitHub by thiientv under the MIT license. 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

Pinecone

NousResearch

OrganizationPopular

Managed vector DB for production RAG and search.

Qdrant

Vector search engine for production RAG systems.

Tensorrt Llm

High-throughput LLM inference on NVIDIA GPUs.

Internal Comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Release Engineering

Build the release contract

Establish gates

Roll out safely

Close the release

Completion condition

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now