'release-notes' 검색 결과

Generate Hugging Face Hub (huggingface_hub) release notes from cached PR JSON files. Use when asked to draft release notes from PR files.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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/下一发布时刻

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Draft user-facing Minutes release notes for a version from the commit range, recent GitHub releases, and the repository release checks. Use when the user asks to write, generate, prepare, revise, or review release notes or a changelog for a Minutes version.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate categorized release notes from any source (GitHub, Linear, Jira, or manual input) with optional publishing

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create the release notes and upgrade guide for a mariadb-operator release. Given the release PR whose body lists every PR included in the release, it gathers each PR, groups the changes by relevance, and produces `docs/releases/RELEASE_<version>_HEADER.md.gotmpl` and `docs/releases/UPGRADE_<version>.md` in the format the previous releases use, then opens a PR targeting `release-<version>`. If no release PR is provided it asks for the new version and infers the changes from git history since the last tag. Use whenever the user wants release notes, an upgrade/update guide, or docs for a new mariadb-operator version — "create the release notes for 26.10.0", "write the upgrade guide", "document this release", "prepare the release PR docs" — even if they don't mention a release PR.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Генерирует release notes / CHANGELOG между двумя тегами или от последнего тега. Используй, когда просят release notes, changelog или список изменений релиза.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Automatically generate user-facing release notes from git commits, pull requests, changelogs, and code changes. Use when preparing software releases, creating version announcements, documenting what changed between versions, or communicating updates to users. Analyzes commit messages, PR descriptions, and code diffs to produce categorized markdown release notes organized by New Features, Improvements, Bug Fixes, and Breaking Changes. Focuses on user-visible changes while filtering out internal/technical details. Triggers when users ask to generate release notes, create changelog, write version announcement, or summarize changes for a release.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Internal — for Boundless team members only. Generate release notes for a new Boundless version. Fetches PR details, explores code changes, and produces prover-facing documentation with config examples, migration guides, and worked examples. Use when the user wants to write release notes, changelog entries, or upgrade guides.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate release notes and changelogs from git commits, feature lists, or project updates. Use when a user asks to generate a changelog, create release notes, summarize recent changes, draft a CHANGELOG entry, or prepare release documentation from git history.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Writes the App Store "What's New in This Version" text for an app update from the repository's commit history: finds the range since the last shipped version, separates changes users can notice from internal work, drafts plain-text notes within Apple's 4,000-character limit and review guidelines, and returns a trace from every sentence back to its commits. Use when someone asks to "write release notes for the App Store", "generate What's New from git", "summarize changes since the last tag for the store listing", or needs the same notes cut to Google Play's 500 characters.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Draft release notes from changes and PRs. Use when a mid-level developer needs a structured changelog.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the stakeholder asks for release notes or a changelog - group done/released work into Added, Changed, Deprecated, Removed, Fixed and Security, in outcome language, with task references

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

generate release notes for changes since a given tag

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write a short release note people finish reading. Picks the few changes a user will notice from the pull requests since the last release, names each by what the reader can now do, keeps to a length budget, writes every language from the intent instead of translating, and traces every line to a PR. Use when cutting a release, or filling a GitHub Release body, a store "what's new", a package changelog or an in-app what's new screen. Triggers - "write the release notes", "release notes for 0.4.0", "what's new", "changelog for this release", "notes de version".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

发布说明编写时使用。适用于 Changelog / 迁移指南 / 影响说明。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Draft a changelog for the next release by summarizing git commits since the last tag. Use only when the user asks to draft release notes, write a changelog entry, or prepare the next version's notes — never trigger automatically.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use after a release succeeds, when maintainers need to sync apps/pythinker-code/CHANGELOG.md into docs/release-notes/changelog.md, then open a PR on a dedicated branch.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn raw Lumen release content (a dump of the LedgerHQ/lumen GitHub Releases page) into one minimalist Slack announcement, drafted to #lumen-releases. Use whenever the user pastes one or more `@ledgerhq/lumen-*` package releases, a chunk of the Releases page, or asks to "announce", "format", "post", or "write release notes / a Slack message" for new Lumen versions. Trigger it even when the user just drops the raw release text with no instructions, or says things like "new Lumen release", "format these lumen versions for Slack", or "lumen changelog for the channel".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate ship-ready release notes from specs and tickets. Use this skill when: - A release is being prepared and you need user-facing release notes - You need internal (engineering) release notes for a deployment - You want to generate release notes from completed specs or tickets

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate structured release notes from git history and closed issues within Claude Code session

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turns a list of merged changes, closed work items or commit messages the user provides into DRAFT release notes under the version heading and date the user supplies, grouped as features, fixes and other, in the organisation's tone from the style guide or prior notes given, with every entry traced to its source item, breaking changes and required actions flagged first, and internal-only items held back for the release owner to confirm. Use when the user asks to "write the release notes for this version", "turn these merged pull requests into a changelog", "summarise what shipped this sprint for customers", "draft the what's new for this release" or "group these closed tickets into release notes". Do not use for an announcement email or intranet post about a launch, use announcement-drafter instead; for a change ticket, use change-request-pack; for a how-to article about one fix, use knowledge-article-drafter. Drafts for human review; never approves, authorises or signs off.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prepares a change request pack (description and justification, scope, schedule, implementation plan, risk as stated, rollback, test evidence as provided, communications, approvals route) from an engineer's notes, ticket or pull request description, with UNKNOWN for anything not provided and a question list for the engineer. Never rates risk or marks a change tested or approved. Use when the user asks to "write the change request for this", "fill in the change ticket from my notes", "prepare the CAB submission" or "turn this pull request into an RFC". Do not use for the step-by-step procedure with commands and rollback, use runbook-drafter instead; for release notes describing what shipped, use release-notes-writer. Drafts for human review; never approves, authorises or signs off.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.