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

# Core Topics

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

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/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
8/11
Quality Score
30
Canonical Locale
en
Detected Body Locale
en

バージョン管理エージェントが自動化されたリリースノートの作成と 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 コマンドに依存

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.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team workflows, approvals, and repeatable execution, move into workflow collections.
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-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.

How do I install release-notes?

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

What are the use cases for release-notes?

Key use cases include: ラズベリーパイログアプリケーションのリリースノートの自動化, リリースノートからアイデア記録のみのコミットをフィルタリング, 最新のステージタグ以降のメインコミットを要約した RELEASES.md エントリの生成.

Which IDEs are compatible with release-notes?

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

Git のインストールと設定が必要. Git ベースのバージョン管理システムのみ. Git 操作には CLI コマンドに依存.

↓ 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 weaties/helmlog. 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-notes 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-notes

Install release-notes, 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 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
AI

nextjs-turbopack

[ 注目 ]
Logo of affaan-m
affaan-m

ローカライズされた概要: Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack. It covers ai-agents, anthropic, claude workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 169.5k
⑂ 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
AI

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
ブラウザ