crimson-release — community crimson-release, crimson, community, ide skills

v1.0.0

About this Skill

Ideal for Git-based AI Agents needing automated release management and version control. Run the Crimson release checklist (just check, uv version bump, uv lock), then create a conventional-commit release commit, tag it, and push. Default bump is minor (use dev bump when needed).

banteg banteg
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
30
Canonical Locale
en
Detected Body Locale
en

Ideal for Git-based AI Agents needing automated release management and version control. Run the Crimson release checklist (just check, uv version bump, uv lock), then create a conventional-commit release commit, tag it, and push. Default bump is minor (use dev bump when needed).

Core Value

Empowers agents to produce clean release commits and tags using Git workflows, incorporating tools like `just check` and `uv version` for streamlined development and version bumping, including minor and dev-only bumps.

Ideal Agent Persona

Ideal for Git-based AI Agents needing automated release management and version control.

Capabilities Granted for crimson-release

Automating release commit generation
Bumping version numbers for new releases
Validating repository status before pushing changes

! Prerequisites & Limits

  • Requires Git repository access
  • Needs `just` and `uv` tools installed
  • Limited to Git-based version control

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is crimson-release?

Ideal for Git-based AI Agents needing automated release management and version control. Run the Crimson release checklist (just check, uv version bump, uv lock), then create a conventional-commit release commit, tag it, and push. Default bump is minor (use dev bump when needed).

How do I install crimson-release?

Run the command: npx killer-skills add banteg/crimson/crimson-release. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for crimson-release?

Key use cases include: Automating release commit generation, Bumping version numbers for new releases, Validating repository status before pushing changes.

Which IDEs are compatible with crimson-release?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for crimson-release?

Requires Git repository access. Needs `just` and `uv` tools installed. Limited to Git-based version control.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add banteg/crimson/crimson-release. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use crimson-release immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

crimson-release

Install crimson-release, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Crimson Release

Goal

Produce a clean release commit + tag for this repo by running the checklist below in order.

Workflow

Pre-flight

  • Ensure the working tree is clean: git status --porcelain prints nothing.
  • Ensure the branch is correct (usually master).
  • Ask for confirmation before any of: git commit, git tag, git push.

0) Checks

Run: just check

1) Bump version (default: minor)

Run: uv version --bump minor

If you need a dev-only bump instead (e.g., 0.1.0.dev29 -> 0.1.0.dev30), run: uv version --bump dev

Capture the resulting version string (use uv version if needed).

2) Refresh lockfile

Run: uv lock

3) Commit

  • Verify the diff is expected: git diff --stat.
  • Stage: git add -A.
  • Commit using conventional commits (example): git commit -m "chore(release): bump version to <version>".

4) Tag

  • Prefer an annotated tag.
  • Derive the tag from the version (common pattern): v<version>.
  • If tag format is unclear, ask before creating it.

Example:

bash
1git tag -a "v<version>" -m "v<version>"

5) Push

  • Push branch and tag.
  • Prefer: git push --follow-tags.
  • If the remote/tag needs to be explicit, push both separately.

Sanity checks

  • Ensure only expected files changed (typically pyproject.toml and uv.lock).
  • Stop and ask if new failures appear or unexpected files change.

Related Skills

Looking for an alternative to crimson-release or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer