release-notes — for Claude Code release-notes, helmlog, community, for Claude Code, ide skills, $LAST_TAG, Release, RELEASES.md, summarizing, commits

v1.0.0
GitHub

이 스킬 정보

자동화된 릴리즈 노트 작성과 Git 명령 통합이 필요한 버전 관리 에이전트에게 적합합니다. 현지화된 요약: Draft a curated RELEASES.md entry from commits since the last stage/ tag # Release Notes: Draft Entry Draft a new RELEASES.md entry summarizing commits on main since the latest stage/ tag. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

기능

Release Notes: Draft Entry
Draft a new RELEASES.md entry summarizing commits on main since the latest
stage/ tag. Run this skill before promoting main to stage.
Find the Commit Range
Run git tag -l 'stage/ ' --sort=-creatordate head -1 to find the latest

# 핵심 주제

for Claude Code $LAST_TAG Release RELEASES.md summarizing commits
weaties weaties
[1]
[1]
업데이트: 3/14/2026

Skill Overview

Start with fit, limitations, and setup before diving into the repository.

자동화된 릴리즈 노트 작성과 Git 명령 통합이 필요한 버전 관리 에이전트에게 적합합니다. 현지화된 요약: Draft a curated RELEASES.md entry from commits since the last stage/ tag # Release Notes: Draft Entry Draft a new RELEASES.md entry summarizing commits on main since the latest stage/ tag. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

이 스킬을 사용하는 이유

에이전트가 Git과 CLI 명령을 사용하여 커밋을 요약하고 아이디어 기록 전용 커밋을 필터링할 수 있는 기능을 제공하여 Git 태그와 커밋 범위를 지원하는 릴리즈 노트 작성 경험을 제공합니다.

최적의 용도

자동화된 릴리즈 노트 작성과 Git 명령 통합이 필요한 버전 관리 에이전트에게 적합합니다.

↓ 실행 가능한 사용 사례 for release-notes

라즈베리파이 로그 애플리케이션의 릴리즈 노트 자동화
릴리즈 노트에서 아이디어 기록 전용 커밋 필터링
최신 스테이지 태그 이후의 메인 커밋을 요약한 RELEASES.md 항목 생성

! 보안 및 제한 사항

  • Git 설치 및 구성이 필요
  • Git 기반 버전 관리 시스템만 해당
  • Git 연산에 CLI 명령에 의존

About The Source

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Labs 데모

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 및 설치 단계

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

? 자주 묻는 질문

release-notes은 무엇인가요?

자동화된 릴리즈 노트 작성과 Git 명령 통합이 필요한 버전 관리 에이전트에게 적합합니다. 현지화된 요약: Draft a curated RELEASES.md entry from commits since the last stage/ tag # Release Notes: Draft Entry Draft a new RELEASES.md entry summarizing commits on main since the latest stage/ tag. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

release-notes은 어떻게 설치하나요?

다음 명령을 실행하세요: npx killer-skills add weaties/helmlog/release-notes. Cursor, Windsurf, VS Code, Claude Code와 19개 이상의 다른 IDE에서 동작합니다.

release-notes은 어디에 쓰이나요?

주요 활용 사례는 다음과 같습니다: 라즈베리파이 로그 애플리케이션의 릴리즈 노트 자동화, 릴리즈 노트에서 아이디어 기록 전용 커밋 필터링, 최신 스테이지 태그 이후의 메인 커밋을 요약한 RELEASES.md 항목 생성.

release-notes 와 호환되는 IDE는 무엇인가요?

이 스킬은 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 와 호환됩니다. 통합 설치에는 Killer-Skills CLI를 사용하세요.

release-notes에 제한 사항이 있나요?

Git 설치 및 구성이 필요. Git 기반 버전 관리 시스템만 해당. Git 연산에 CLI 명령에 의존.

↓ 이 스킬 설치 방법

  1. 1. 터미널 열기

    프로젝트 디렉터리에서 터미널 또는 명령줄을 여세요.

  2. 2. 설치 명령 실행

    npx killer-skills add weaties/helmlog/release-notes 를 실행하세요. CLI가 IDE 또는 에이전트를 자동으로 감지하고 스킬을 설정합니다.

  3. 3. 스킬 사용 시작

    스킬이 이제 활성화되었습니다. 현재 프로젝트에서 release-notes을 바로 사용할 수 있습니다.

! Source Notes

This page is still useful for installation and source reference. Before using it, compare the fit, limitations, and upstream repository notes above.

Upstream Repository Material

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Upstream Source

release-notes

Install release-notes, an AI agent skill for AI agent workflows and automation. Explore features, use cases, limitations, and setup guidance.

SKILL.md
Readonly
Upstream Repository Material
The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.
Upstream Source

Release Notes: Draft Entry

Draft a new RELEASES.md entry summarizing commits on main since the latest stage/* tag. Run this skill before promoting main to stage.

1. Find the Commit Range

Run git tag -l 'stage/*' --sort=-creatordate | head -1 to find the latest stage tag. If no stage tags exist, use the initial commit as the base.

Save the tag as $LAST_TAG and collect the commit range:

bash
1git log --oneline "$LAST_TAG"..HEAD

2. Filter Out Ideation-Log-Only Commits

For each commit in the range, check which files it touches:

bash
1git diff-tree --no-commit-id --name-only -r <sha>
  • Exclude entirely: Commits where every changed file is docs/ideation-log.md
  • Include (code changes only): Commits that touch docs/ideation-log.md AND other files — describe only the non-ideation changes

If no non-ideation commits remain after filtering, tell the user:

All commits since the last stage tag only touch the ideation log — nothing to document. The promote workflow will allow this through automatically.

And stop here.

3. Analyze Changes and Group by Theme

For each included commit, examine:

  • The commit message and any PR title (from (#NNN) references)
  • The files changed and the nature of the diff

Group changes into logical themes (e.g., "Performance analysis", "Synthesizer improvements", "Deploy & infrastructure", "Bug fixes"). Use your judgment — aim for 2–5 groups. A single-commit release can have just one group.

4. Draft the RELEASES.md Entry

Read RELEASES.md to match the existing format. Draft a new entry following this pattern:

markdown
1## Title — Description (YYYY-MM-DD)
2
3Optional 1–2 sentence summary of the release.
4
5### Theme group
6- **Feature name** (#issue) — one-line description
7- **Feature name** (#issue) — one-line description with enough context to
8  understand the change without reading the code

Rules:

  • Use today's date (YYYY-MM-DD format)
  • Bold feature names, reference issue/PR numbers as (#NNN)
  • One bullet per logical change — merge related commits into a single bullet
  • Use sub-bullets only when a change needs a brief clarification
  • Do NOT mention ideation log updates anywhere in the entry

5. Insert into RELEASES.md

Prepend the new entry immediately after the # Release Notes heading (line 1), with a blank line separating it from the next entry. Do not modify existing entries.

6. Present for Review

Show the user the drafted entry and ask them to review and edit before committing. Do NOT commit automatically — the user will commit when satisfied.

관련 스킬

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

모두 보기

openclaw-release-maintainer

Logo of openclaw
openclaw

현지화된 요약: 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 333.8k
⑂ 0
인공지능

widget-generator

Logo of f
f

현지화된 요약: Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat . It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf

★ 149.6k
⑂ 0
인공지능

flags

Logo of vercel
vercel

현지화된 요약: The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 138.4k
⑂ 0
브라우저

pr-review

Logo of pytorch
pytorch

현지화된 요약: Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review . It covers autograd, deep-learning, gpu workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 98.6k
⑂ 0
개발자