「changelog」の検索結果

Use when the user asks to "keep the launch momentum going after launch week", "plan a changelog / release-notes cadence as GTM", or "is this update worth a relaunch"; produces a T+1→T+30 momentum plan — a launch-moment calendar (milestone / shipped-loop / badge moments only), announcement-tier routing (major = full-channel, medium = targeted, minor = changelog-only), a relaunch legitimacy call, spike-to-owned handoff briefs, and the next Tier-1 moment with launch-stacking spacing. Not for the 30-day content-reuse map or paid amplification execution — use content-amplifier; not for planning the next launch end to end — use launch-tier-planner. 抗第二周断崖/changelog-as-GTM/relaunch/下一发布时刻

日本語の概要は準備中です。原文の説明を表示しています。

Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.

日本語の概要は準備中です。原文の説明を表示しています。

Generate structured changelogs from git history. Use when user asks "what changed recently", "generate a changelog", "summarize commits" or user wants to understand recent development activity.

日本語の概要は準備中です。原文の説明を表示しています。

AI repo versioning and changelogs via release-please — never edit CHANGELOG.md or pyproject version by hand. Use when the user asks about releases, version bumps, changelogs, or preparing a release.

日本語の概要は準備中です。原文の説明を表示しています。

Generates and maintains changelogs following Keep a Changelog format. Use when updating release notes, finishing tasks, or tagging versions. For version bumps, see semantic-versioning.

日本語の概要は準備中です。原文の説明を表示しています。

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

日本語の概要は準備中です。原文の説明を表示しています。

Generate comprehensive changelogs from Git history, commit messages, pull requests, and issue tracking for release documentation. Use when preparing releases, documenting changes, creating release notes, categorizing commits, generating version summaries, maintaining project history, or automating changelog updates.

日本語の概要は準備中です。原文の説明を表示しています。

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

日本語の概要は準備中です。原文の説明を表示しています。

Generate user-facing or internal release notes and changelogs. Load when the user prepares a release, tags a version, or wants to summarize recent progress. Also triggers on "write a changelog", "prepare release notes", "what's new in this version", "summarize my commits", or "create a release summary". Auto-triggered by library-skill after major repo changes (new skills added, skills renamed, structure changes). Applicable to any project, including this skill library itself.

日本語の概要は準備中です。原文の説明を表示しています。

Generate a single unified changelog from git history that works for everyone in the company (managers and non-tech colleagues as well as developers). Outputs Slack mrkdwn so it can be pasted straight into Slack. Defaults to Slovak (English only on explicit request) and to comparing the release branch (main) against develop to show unreleased changes; also supports date ranges like "today", "yesterday", "last week", or an explicit git range. User-invoked only via /changelog.

日本語の概要は準備中です。原文の説明を表示しています。

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

日本語の概要は準備中です。原文の説明を表示しています。

Generates CHANGELOG.md files following Keep a Changelog format. Creates version history documentation.

日本語の概要は準備中です。原文の説明を表示しています。

Show recent Claude Code changes personalized to user's setup. Trigger when user asks about changelog, "what's new", "cc changelog", "claude code updates", "recent changes", or wants to know what changed in Claude Code.

日本語の概要は準備中です。原文の説明を表示しています。

OpenClawのリリース情報を確認し、Discord向けの告知文を作成します。版ごとの更新手順や利用者に試してほしい点を整理し、投稿にも対応します。

• beta版の告知文を作りたいとき
• stable版の更新方法を案内したいとき
• 利用者向けのテスト項目の整理

GitHubのIssue分類やPRの確認、CI失敗の調査、変更履歴を含むリリース準備、セキュリティ警告の確認を、gh CLIで進める運用スキル。

• Issueの分類と重複確認
• PRのレビュー状況とマージ可否確認
• CIワークフローの失敗調査

Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.

日本語の概要は準備中です。原文の説明を表示しています。

Write the Discord announcement for a stable Paperclip release from the release changelog. Use when a release issue needs a copy-pasteable dotta-voice Discord post or refreshed discord_announcement document.

日本語の概要は準備中です。原文の説明を表示しています。

Generate the stable Paperclip release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.

日本語の概要は準備中です。原文の説明を表示しています。

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

日本語の概要は準備中です。原文の説明を表示しています。

Write the changelog entry for a new minor or major Storybook release. Use when preparing a CHANGELOG.md entry for a X.Y.0 version.

日本語の概要は準備中です。原文の説明を表示しています。

Coordinates the three artifacts that ship a new Appwrite feature announcement: docs updates under src/content/docs/, an announcement blog post under blog/announcing-<slug>/, and a changelog entry under src/content/changelog/entries/. Use when the user asks to announce, launch, or ship a feature, product, SDK, runtime, integration, or plugin.

日本語の概要は準備中です。原文の説明を表示しています。

Author the committed release-notes file for a Prisma 8 release (stable or `8.0.0-rc.N`) by enumerating the merged PRs since the previous release `v*` tag (stable or `-rc.N`), resolving opaque `TML-NNNN:` titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking changes first — into `docs/releases/v<version>.md` plus a mirrored `CHANGELOG.md` entry. Use when cutting a release, when the `publish-npm-version` skill reaches its "draft the release notes" step, when asked to "draft the release notes", "write the changelog for this release", "author docs/releases/v<x>.md", or "summarize what shipped since the last release".

日本語の概要は準備中です。原文の説明を表示しています。

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

日本語の概要は準備中です。原文の説明を表示しています。

Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.

日本語の概要は準備中です。原文の説明を表示しています。