release — build-system release, community, build-system, ide skills, linter, linting

v1.0.0

이 스킬 정보

자동화된 릴리스 및 변경 로그 관리 기능이 필요한 버전 관리 에이전트에 적합합니다. Cut and publish a release. Does CHANGELOG prep, version bumps, PR creation, CI, tagging, and publishing.

# Core Topics

langston-barrett langston-barrett
[0]
[1]
Updated: 3/15/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for teams, 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
Review Score
7/11
Quality Score
31
Canonical Locale
en
Detected Body Locale
en

자동화된 릴리스 및 변경 로그 관리 기능이 필요한 버전 관리 에이전트에 적합합니다. Cut and publish a release. Does CHANGELOG prep, version bumps, PR creation, CI, tagging, and publishing.

이 스킬을 사용하는 이유

에이전트에 빌드 및 린팅 프로세스의 자동화를 가능하게 하며, CHANGELOG 및 깃 히스토리를 분석하여 릴리스를 준비하고 버전 범프 유형을 결정하며, 깃 및 파이썬 스크립트(`scripts/release.py`와 같은)를 활용합니다.

최적의 용도

자동화된 릴리스 및 변경 로그 관리 기능이 필요한 버전 관리 에이전트에 적합합니다.

실행 가능한 사용 사례 for release

CHANGELOG 분석을 사용하여 자동으로 릴리스를 준비합니다
깃 히스토리를 기반으로 버전 범프 유형을 결정합니다
깃 로그를 기반으로 누락된 CHANGELOG 항목을 제안합니다

! 보안 및 제한 사항

  • 깃 저장소 액세스가 필요합니다
  • 스크립트 실행을 위해 파이썬 환경이 필요합니다
  • 릴리스 준비는 CHANGELOG 및 깃 히스토리 분석만 가능합니다

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - 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 release?

자동화된 릴리스 및 변경 로그 관리 기능이 필요한 버전 관리 에이전트에 적합합니다. Cut and publish a release. Does CHANGELOG prep, version bumps, PR creation, CI, tagging, and publishing.

How do I install release?

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

What are the use cases for release?

Key use cases include: CHANGELOG 분석을 사용하여 자동으로 릴리스를 준비합니다, 깃 히스토리를 기반으로 버전 범프 유형을 결정합니다, 깃 로그를 기반으로 누락된 CHANGELOG 항목을 제안합니다.

Which IDEs are compatible with 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 release?

깃 저장소 액세스가 필요합니다. 스크립트 실행을 위해 파이썬 환경이 필요합니다. 릴리스 준비는 CHANGELOG 및 깃 히스토리 분석만 가능합니다.

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 langston-barrett/lun. 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 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

release

Install 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

Release

Overview

  1. Analyze CHANGELOG and git history to prepare release
  2. Suggest missing CHANGELOG entries from git log
  3. Determine version bump type (major/minor/patch)
  4. Run scripts/release.py with the determined bump type

Step 0: Check out main

sh
1git checkout main && git pull

Step 1: Ensure CHANGELOG Has ## next Section

If no ## next section exists, create one at the top of the changelog (after the header):

markdown
1## next 2 3- [entries go here]

Step 2: Analyze CHANGELOG for Missing Entries

Before releasing, review git history for commits since the last release that aren't in CHANGELOG.

bash
1# Show commits since last tag 2git log $(git describe --tags --abbrev=0)..HEAD --oneline

For each important change not already mentioned in CHANGELOG under ## next:

  1. Summarize the change in user-facing terms
  2. Ask the user: "Add to CHANGELOG: [summary]? (y/n)"
  3. If confirmed, add the entry under ## next in CHANGELOG.md

Step 3: Determine Version Bump Type

Analyze the ## next section of CHANGELOG.md to determine the appropriate bump:

MAJOR (breaking changes):

  • "BREAKING" keyword in any entry
  • Removed features or APIs
  • Changed behavior that breaks existing usage

MINOR (new features):

  • "Add" keyword starting an entry
  • New commands, flags, or configuration options
  • New capabilities that don't break existing usage

PATCH (bug fixes):

  • "Fix" keyword starting an entry
  • Performance improvements
  • Documentation updates
  • Internal refactoring without user-facing changes

Apply the highest applicable bump type. Present the suggestion to the user: "Based on CHANGELOG entries, suggesting [type] bump. Proceed? (y/n/major/minor/patch)"

Step 5: Run the Release Script

Execute the release script with the determined bump type:

bash
1python3 .claude/skills/release/scripts/release.py [major|minor|patch]

The script handles:

  1. Checkout main, pull, create release branch
  2. Update version in Cargo.toml
  3. Update CHANGELOG.md (replace ## next with version header and link)
  4. Run cargo clippy -- --all-targets --deny warnings and cargo test
  5. Commit changes with message vX.Y.Z
  6. Create PR with title vX.Y.Z
  7. Open PR in browser
  8. Wait for user to press ENTER
  9. Wait for all CI checks to pass
  10. Merge PR
  11. Checkout main, pull
  12. Create and push annotated tag vX.Y.Z
  13. Wait for tag CI to complete
  14. Publish draft GitHub release

Example Session

User: cut a release

Claude:
1. Checks git log for interesting commits
2. "Add to CHANGELOG: Add support for YAML configs? (y/n)"
3. User: "y"
4. Claude adds entry to CHANGELOG
5. "Based on CHANGELOG (new 'Add' entry), suggesting minor bump. Proceed?"
6. User: "y"
7. Claude runs: python3 .claude/skills/release/scripts/release.py minor

관련 스킬

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

모두 보기

openclaw-release-maintainer

Logo of openclaw
openclaw

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

333.8k
0
인공지능

widget-generator

Logo of f
f

prompts.chat 피드 시스템을 위한 사용자 지정 가능한 위젯 플러그인을 생성합니다

149.6k
0
인공지능

flags

Logo of vercel
vercel

리액트 프레임워크

138.4k
0
브라우저

pr-review

Logo of pytorch
pytorch

파이썬에서 텐서와 동적 신경망 구현 및 강력한 GPU 가속 지원

98.6k
0
개발자