Agent skill

Codemie Release

by codemie-ai in codemie-ai/codemie-code

Release a new version of CodeMie CLI. An agent skill from codemie-ai/codemie-code.

Apache-2.0Auto-check passedDevelopment

Install Codemie Release

skills CLI

$ npx skills add codemie-ai/codemie-code --skill codemie-release -a claude-code

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

GitHub CLI

$ gh skill install codemie-ai/codemie-code codemie-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/codemie-ai/codemie-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/codemie-release .claude/skills/codemie-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/

Paste into Claude Code

Install the "codemie-release" agent skill from https://github.com/codemie-ai/codemie-code/tree/main/.claude/skills/codemie-release into .claude/skills/codemie-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codemie-release", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/codemie-ai/codemie-code/tree/main/.claude/skills/codemie-release

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add codemie-ai/codemie-code --skill codemie-release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install codemie-ai/codemie-code codemie-release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/codemie-ai/codemie-code.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/codemie-release .agents/skills/codemie-release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "codemie-release" agent skill from https://github.com/codemie-ai/codemie-code/tree/main/.claude/skills/codemie-release into .agents/skills/codemie-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codemie-release", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add codemie-ai/codemie-code --skill codemie-release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install codemie-ai/codemie-code codemie-release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/codemie-ai/codemie-code.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/codemie-release .cursor/skills/codemie-release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "codemie-release" agent skill from https://github.com/codemie-ai/codemie-code/tree/main/.claude/skills/codemie-release into .cursor/skills/codemie-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codemie-release", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/codemie-ai/codemie-code.git --path .claude/skills/codemie-release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add codemie-ai/codemie-code --skill codemie-release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install codemie-ai/codemie-code codemie-release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/codemie-ai/codemie-code.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/codemie-release .gemini/skills/codemie-release && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "codemie-release" agent skill from https://github.com/codemie-ai/codemie-code/tree/main/.claude/skills/codemie-release into .gemini/skills/codemie-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codemie-release", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install codemie-ai/codemie-code codemie-release

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add codemie-ai/codemie-code --skill codemie-release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/codemie-ai/codemie-code.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/codemie-release .github/skills/codemie-release && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "codemie-release" agent skill from https://github.com/codemie-ai/codemie-code/tree/main/.claude/skills/codemie-release into .github/skills/codemie-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codemie-release", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add codemie-ai/codemie-code --skill codemie-release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install codemie-ai/codemie-code codemie-release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/codemie-ai/codemie-code.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/codemie-release .opencode/skills/codemie-release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "codemie-release" agent skill from https://github.com/codemie-ai/codemie-code/tree/main/.claude/skills/codemie-release into .opencode/skills/codemie-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codemie-release", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: codemie-release
GitHub stars: 294
Token cost: ~1.8k tokens
SKILL.md length: 468 words
Files: 1
Skills in repo: 9
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Release a new version of CodeMie CLI. An agent skill from codemie-ai/codemie-code.

Works in 12 steps: Get Commit Delta → Analyze Commit Types → Determine Version Bump → …
User says release
SKILL.md covers Pre-flight Checks, Analyze Commits and Determine…, Run Tests and Generate Release Notes, plus 2 more sections
Calls git, npm and gh

What it does

Codemie Release is an agent skill from codemie-ai/codemie-code. Release a new version of CodeMie CLI. Use when user says "release", "create release", "publish version", "bump version and release", or wants to publish a new version to npm. Handles version bumping, git tagging, pushing, and GitHub release creation with automatic version detection from conventional commits.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Commit messages and Changelog and release notes. It works with GitHub, Git and npm. The repository describes itself as: AI Run CodeMie CLI with analytics capabilities. The licence is Apache-2.0.

When your agent uses it

User says release
Publish version
Bump version and release
Wants to publish a new version to npm

Example prompts

“release”
“create release”
“publish version”
“/codemie-release”

Requirements

Node.js

Workflow steps

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

Get Commit Delta
Analyze Commit Types
Determine Version Bump
Calculate Target Version
Present Recommendation
Categorize Commits
Extract Concrete Details
Format Breaking Changes
Release Notes Template
Update Version
Commit Version Bump
Create Tag

What it can do on your machine

Read from SKILL.md and the folder at commit 0218c8d. 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
- npm
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, npm and 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

Codemie Release loads about 1.8k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 468 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~81
When it runs · the whole SKILL.md, loaded when a task matches: ~1.8k

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 codemie-ai/codemie-code at commit 0218c8d, republished under its Apache-2.0 licence (© codemie-ai). 468 words, ~1,803 tokens.

Download SKILL.mdSave it as .claude/skills/codemie-release/SKILL.md (or your agent's skills folder).

name: codemie-release
description: Release a new version of CodeMie CLI. Use when user says "release", "create release", "publish version", "bump version and release", or wants to publish a new version to npm. Handles version bumping, git tagging, pushing, and GitHub release creation with automatic version detection from conventional commits.

CodeMie Release

Automate the release process for CodeMie CLI following semantic versioning and conventional commits.

Pre-flight Checks

Before starting, verify:

Branch: Must be on main. If not, stop and ask user to switch.
Working directory: Check for uncommitted changes. Warn if present.

Current state: Determine what's already done:

bash

# Current version
grep '"version"' package.json | sed 's/.*"version": "\(.*\)".*/\1/'

# Latest tag
git describe --tags --abbrev=0 2>/dev/null

# Check if tag exists
git tag -l "v<VERSION>"

# Check if release exists
gh release view "v<VERSION>" 2>/dev/null

Analyze Commits and Determine Version

CRITICAL: Always analyze commits to determine the appropriate version bump based on conventional commit types.

1. Get Commit Delta

bash

# Get commits since last release (excluding version bump commits)
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null)
git log --pretty=format:"%s" ${LAST_TAG:+$LAST_TAG..HEAD} | grep -v "^chore: bump version"

2. Analyze Commit Types

Parse each commit message to identify type:

Conventional Commit Format: <type>(<scope>): <subject>

Types: feat, fix, docs, style, refactor, perf, test, chore, ci, revert
Scopes (optional): cli, agents, providers, assistants, config, proxy, workflows, ci, analytics, utils, deps, tests, skills

Breaking Changes: Check commit bodies for BREAKING CHANGE: footer

bash

# Check for breaking changes
git log --pretty=format:"%B" ${LAST_TAG:+$LAST_TAG..HEAD} | grep -q "BREAKING CHANGE:"

3. Determine Version Bump

Version bump rules (highest precedence wins):

MAJOR bump (x.0.0) - If any commit contains BREAKING CHANGE: in body
MINOR bump (0.x.0) - If any commit has feat: or feat(scope):
PATCH bump (0.0.x) - If only fix:, refactor:, perf:, docs:, style:, test:, chore:, ci:, revert:

4. Calculate Target Version

bash

# Current version from package.json
CURRENT=$(grep '"version"' package.json | sed 's/.*"version": "\(.*\)".*/\1/')

# Parse version parts (e.g., "0.0.35" → major=0, minor=0, patch=35)
IFS='.' read -r MAJOR MINOR PATCH <<< "$CURRENT"

# Apply bump based on commit analysis:
# - If BREAKING CHANGE found: MAJOR=$((MAJOR+1)), MINOR=0, PATCH=0
# - If feat: found: MINOR=$((MINOR+1)), PATCH=0
# - Otherwise: PATCH=$((PATCH+1))

TARGET_VERSION="$MAJOR.$MINOR.$PATCH"

5. Present Recommendation

Show the user:

Current version: e.g., 0.0.35
Commits analyzed: List of commit subjects
Detected bump type: MAJOR/MINOR/PATCH with explanation
Recommended version: e.g., 0.0.36
Ask user to confirm or provide alternative

Example output:

📦 Current version: 0.0.35
📊 Analyzed 3 commits since v0.0.35:
  - fix(utils): auto-update PATH during Claude installation on Windows (#120)
  - refactor(skills): relocate skills module to codemie-code agent (#117)

🔍 Detected: PATCH bump (only fixes and refactors found)
🎯 Recommended version: 0.0.36

Confirm release version 0.0.36?

Run Tests

After user confirms the version, run the full test suite before any commits.

bash

npm test

This runs unit tests, CLI integration tests, and agent tests (unit + cli + agent projects).

If tests fail: stop the release, report which suite failed, and do not proceed to the release steps. Ask the user how to proceed.

If tests pass: continue to Generate Release Notes and Release Steps.

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

Generate Release Notes

CRITICAL: Group commits by type and generate concrete, user-focused release notes.

1. Categorize Commits

bash

# Get full commit messages since last tag
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null)
git log --pretty=format:"%s|%b" ${LAST_TAG:+$LAST_TAG..HEAD} | grep -v "^chore: bump version"

Group commits by type:

✨ Features (feat)
🐛 Bug Fixes (fix)
⚡ Performance (perf)
♻️ Refactoring (refactor)
📚 Documentation (docs)
🔧 Maintenance (chore, ci, test, style)

2. Extract Concrete Details

For each commit:

Remove type prefix: feat(agents): add feature → add feature
Capitalize first letter: add feature → Add feature
Keep PR numbers: (#123)
Extract scope for context: feat(agents): → show as "[agents]"

3. Format Breaking Changes

If breaking changes exist:

markdown

## ⚠️ BREAKING CHANGES

- **[scope]**: Description of what broke and how to migrate

Extract from commit body after BREAKING CHANGE: line.

4. Release Notes Template

markdown

## What's Changed

### ✨ Features
- **[scope]**: Feature description (#PR)

### 🐛 Bug Fixes
- **[scope]**: Fix description (#PR)

### ⚡ Performance Improvements
- **[scope]**: Performance improvement (#PR)

### ♻️ Refactoring
- **[scope]**: Refactoring description (#PR)

### 📚 Documentation
- **[scope]**: Documentation change (#PR)

### 🔧 Maintenance
- **[scope]**: Maintenance task (#PR)

**Full Changelog**: https://github.com/codemie-ai/codemie-code/compare/${LAST_TAG}...v<VERSION>

Example concrete release notes:

markdown

## What's Changed

### 🐛 Bug Fixes
- **[utils]**: Auto-update PATH during Claude installation on Windows (#120)

### ♻️ Refactoring
- **[skills]**: Relocate skills module to codemie-code agent (#117)

**Full Changelog**: https://github.com/codemie-ai/codemie-code/compare/v0.0.35...v0.0.36

Release Steps

Execute each step, skipping if already completed:

1. Update Version

bash

npm version <VERSION> --no-git-tag-version

Skip if package.json already at target version.

2. Commit Version Bump

bash

git add package.json package-lock.json
git commit -m "chore: bump version to <VERSION>

🤖 Generated with release script"

Skip if commit message chore: bump version to <VERSION> exists in HEAD.

3. Create Tag

bash

git tag -a "v<VERSION>" -m "Release version <VERSION>"

Skip if tag v<VERSION> already exists.

4. Push to Origin

bash

git push origin main
git push origin "v<VERSION>"

5. Create GitHub Release

bash

# Create release with generated notes
gh release create "v<VERSION>" \
  --title "Release v<VERSION>" \
  --notes "<GENERATED_RELEASE_NOTES>" \
  --latest

Skip if release v<VERSION> already exists.

Use the concrete, categorized release notes generated in the previous section.

Completion

After successful release, inform user:

✅ Release v<VERSION> created successfully
🔄 Monitor GitHub Actions for npm publish
📦 Package will be available at: npm install @codemieai/code@<VERSION>
🔗 View release: https://github.com/codemie-ai/codemie-code/releases/tag/v<VERSION>

Files

Just SKILL.md in .claude/skills/codemie-release of codemie-ai/codemie-code.

Open the folder on GitHubat commit 0218c8d

Compare with similar skills

Codemie 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.

Codemie Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Codemie Release this skillcodemie-ai/codemie-code	294	—	~1.8k	Automated safety check: Pass	Apache-2.0	yesterday
Verdaccio Pull Request Workflowverdaccio/verdaccio	18k	—	~1.9k	Automated safety check: Pass	MIT	yesterday
Hunk Release Workflowmodem-dev/hunk	9.5k	—	~3.8k	Automated safety check: Pass	MIT	yesterday
Chinese Commit ConventionsjnMetaCode/superpowers-zh	8.3k	1 repos	~1.6k	Automated safety check: Pass	MIT	4 days ago
ZCF Release AutomationUfoMiao/zcf	6.1k	—	~3.4k	Automated safety check: Pass	MIT	1 mo ago
Git Changes ReporterNo-Trade-No-Life/Yuan	352	—	~1.2k	Automated safety check: Pass	MIT	5 mo ago

Similar skills

Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
18k GitHub stars~1.9k tokensUpdated yesterday
DevelopmentAuto-check passed
Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
9.5k GitHub stars~3.8k tokensUpdated yesterday
DevelopmentAuto-check passed
Chinese Commit Conventions
jnMetaCode/superpowers-zh
Reference for Chinese-language git commits and changelogs: Conventional Commits adapted for Chinese teams, with templates, breaking-change notes and issue links for several platforms.
8.3k GitHub starsUsed in 1 repo~1.6k tokens
DevelopmentAuto-check passed
ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
Git Changes Reporter
No-Trade-No-Life/Yuan
生成结构化 git 变更报告（JSON + Markdown）。使用此技能当用户提到"git 变更"、"commit 摘要"、"代码审查"、"release note"、"近期改动"、"每日摘要"，或需要分析指定 commit 区间的代码变更。包含三元组结构（设计意图、核心代码、影响范围）的语义化报告，适用于代码审查、发布说明、团队同步、CI/CD 等场景。
352 GitHub stars~1.2k tokensUpdated 5 mo ago
DevelopmentAuto-check passed
Release Workflow
Caldis/react-zmage
A skill your agent uses when the user wants to ship a new version of react-zmage to npm.
946 GitHub stars~3.6k tokensUpdated 4 mo ago
DevelopmentAuto-check: notes

More from codemie-ai/codemie-code

All 9 skills in this repo

Codemie Analytics
codemie-ai/codemie-code
CodeMie Analytics expert — use this skill whenever the user asks about CodeMie usage data, AI adoption metrics, user leaderboards, CLI insights, spending, LiteLLM costs, token usage, or wants to…
294 GitHub stars~7.5k tokensUpdated yesterday
Auto-check passed
Codemie HTML Report
codemie-ai/codemie-code
Build static HTML pages, reports, dashboards, and mockups that match the CodeMie UI design system.
294 GitHub stars~3.3k tokensUpdated yesterday
Auto-check passed
Msgraph
codemie-ai/codemie-code
Work with Microsoft 365 services via the Graph API — emails, calendar events, SharePoint sites (read and write), Teams chats and channel messages, OneDrive files, OneNote notebooks, Planner task…
294 GitHub stars~4.1k tokensUpdated yesterday
Auto-check passed
Codemie Assistant Builder
codemie-ai/codemie-code
Build, test and autonomously improve CodeMie platform assistants.
294 GitHub stars~3.3k tokensUpdated yesterday
Auto-check passed
Report Issue
codemie-ai/codemie-code
This skill should be used when the user wants to report a bug, file an issue, or suggest a feature for the CodeMie Code CLI tool (codemie-ai/codemie-code repository on GitHub).
294 GitHub stars~2.3k tokensUpdated yesterday
Auto-check: notes
Codemie Jira Assistant
codemie-ai/codemie-code
Business Analyst Assistant - expert to work with Jira. An agent skill from codemie-ai/codemie-code.
294 GitHub stars~489 tokensUpdated yesterday
Auto-check passed

Works with

Questions about Codemie Release

What does Codemie Release do?

Release a new version of CodeMie CLI. An agent skill from codemie-ai/codemie-code. Codemie Release is an agent skill from codemie-ai/codemie-code. Release a new version of CodeMie CLI.

When should I use Codemie Release?

Codemie Release fits situations like: user says release; publish version; bump version and release; wants to publish a new version to npm.

How do I install Codemie Release in Claude Code?

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

How do I install Codemie Release in Codex?

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

Can I use Codemie 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 codemie-ai/codemie-code --skill codemie-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/codemie-release, .gemini/skills/codemie-release, .github/skills/codemie-release and .opencode/skills/codemie-release in your project.

What does Codemie Release need to run?

Going by SKILL.md and its folder, Codemie Release needs the command-line tools its instructions call (git, npm and gh). Our summary lists: Node.js.

Does Codemie Release access the network?

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

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

Codemie Release is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Codemie Release use?

About 1.8k tokens (SKILL.md is roughly 7.2k 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 Codemie Release?

Skills that share tags, products or a category with Codemie Release: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Hunk Release Workflow (modem-dev/hunk, 9.5k stars), Chinese Commit Conventions (jnMetaCode/superpowers-zh, 8.3k stars) and ZCF Release Automation (UfoMiao/zcf, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Codemie Release?

codemie-ai (a GitHub user) maintains it in codemie-ai/codemie-code, which has 294 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.

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

Install Codemie Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

CodeMie Release

Pre-flight Checks

Analyze Commits and Determine Version

1. Get Commit Delta

2. Analyze Commit Types

3. Determine Version Bump

4. Calculate Target Version

5. Present Recommendation

Run Tests

Generate Release Notes

1. Categorize Commits

2. Extract Concrete Details

3. Format Breaking Changes

4. Release Notes Template

Release Steps

1. Update Version

2. Commit Version Bump

3. Create Tag

4. Push to Origin

5. Create GitHub Release

Completion

Files

Compare with similar skills

Similar skills

More from codemie-ai/codemie-code

Related

Questions about Codemie Release