'release-notes' 검색 결과

Turn Git commits and pull request details into release notes in three formats: a changelog section, a release PR description, and a user announcement. Group changes, explain user impact, and flag database migrations.

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

• Prepare a changelog for a release
• Draft a release pull request description
• Explain updates to users in plain language

Draft public Tamanu release notes for a given version. Use when the user wants release notes for a Tamanu release (e.g. "draft release notes for v2.45"). Pulls work from the specs and code that landed in that version's release/X.Y branch, plus the matching issues in the trackers (Linear's Tamanu team and Workhorse's Tamanu workspace), reconciles them, and writes docs/release-notes/vX-YY.md in the canonical v2.44 format for project managers and system administrators, plus a styled HTML rendering at .workhorse/design/designs/vX-YY-release-notes.html. Not for developer changelogs or QA test scoping (use scope-tamanu-release-tests for the latter).

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

HeroUI Pro React の新リリースを公式サイトから調査し、 指定されたリリースノートドキュメントを追記更新するスキル。 「できるようになったこと・作れるようになったもの」を主軸に、 自然な日本語でユーザーストーリーとして記述する。 Trigger: HeroUI Pro リリースノート更新, heroui-pro release notes, heroui-pro更新, /dev:heroui-pro-release-notes

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

Draft Prisma 8 release notes from merged PRs since the previous published release. Select user-facing changes, put breaking changes first, link migration guidance and PR evidence, and mirror the notes in CHANGELOG.md.

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

• Draft notes for a stable or RC release
• Summarize changes since the previous published release
• Explain breaking changes with migration guidance

Edit patch release notes for GitHub Enterprise Server, correcting typos and style while preserving approved technical facts. Keep repeated notes consistent across versions and update known issue source comments so future releases inherit the same edits.

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

• Proofread approved patch release notes
• Keep repeated notes consistent across versions
• Update source comments for known issues

Independently review release note drafts against scanned change data. Check factual accuracy, missing items, tone, links, and clear coverage of breaking changes and security updates, then return a verdict with recommended revisions.

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

• Checking release notes against scanned changes
• Reviewing breaking change and security notices
• Finding missing links and acknowledgments

Draft user-facing release notes from a verified release range. Use for release-note or changelog requests and /release-notes; writing notes alone does not imply publishing a release.

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

Draft or refresh the human-written release notes for a version in `docs/releases/`. Codex equivalent of the Claude /release-notes command.

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

Create or update product-update / release-notes content for a given OpenMetadata/Collate patch version across getcollate, openmetadata-site, and docs-om. Sources getcollate's changelog from openmetadata-collate + OpenMetadata + ai-platform; openmetadata-site's from OpenMetadata only; docs-om reuses openmetadata-site's already-written content, reformatted into its Mintlify snippet structure. Filters to customer-facing changes only, runs each target's own doc-review checklist, verifies every link live, and requires explicit approval before any commit.

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

최근 코드와 기능 변경을 바탕으로 문서와 실제 동작의 차이를 찾아 관련 자료와 예시만 수정하고, 사용자에게 미치는 영향을 담은 릴리스 노트를 작성합니다.

• 새 기능에 맞춰 문서를 갱신합니다
• 릴리스 전에 문서를 점검합니다
• 오래된 기본값과 조작 설명을 수정합니다

Create a single HTML page that organizes release highlights, additions, fixes, breaking changes, known issues, and upgrade guidance. Missing information is explicitly labeled, helping readers distinguish supplied details from information that was not provided.

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

• Preparing release notes for a version update
• Sharing additions and fixes on one page
• Documenting breaking changes and upgrade steps

Organize open pull requests before a release, classify what to merge or defer, and track decisions in a resumable document. Guide review, merging, follow-up fixes, and closing requests already covered by other changes.

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

• Sort a backlog of pull requests before a release
• Prioritize bug fixes for the next version
• Resume interrupted reviews from a progress document

Draft release notes from commits, pull requests, and file changes since the latest release tag. Update the Unreleased section of CHANGELOG.md with a thematic narrative while preserving previous releases and leaving versions and tags unchanged.

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

• Keeping release notes current during development
• Summarizing changes before a pull request
• Preparing a changelog draft before release

Prepare the next Prisma 8 release by updating workspace versions, assembling upgrade guides, and drafting release notes. Open release and documentation pull requests for maintainer review; merging the release request triggers automated publication.

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

• Preparing the next Prisma 8 release candidate
• Updating versions across workspace packages
• Assembling upgrade guides and release notes

Turn development tickets, product requirements, or internal changelogs into release notes users can understand. Organize updates into features, improvements, and fixes, explain their benefits, and highlight changes that require users to take action.

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

• Creating release notes from development tickets
• Turning internal changelogs into user announcements
• Explaining updates that require user action

Prepare an OpenSEO release by updating the version, selecting user-visible changes from commits, and writing concise release notes. Review agents check the draft against the code before a pull request is opened for the release.

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

• Prepare an OpenSEO release pull request
• Summarize changes since the previous release
• Update the version and release notes together

Draft a NemoClaw release announcement from verified GitHub tags and shipped pull requests. Produce a local Markdown draft with an opening narrative, categorized changes, visible pull request links, and thanks to external contributors.

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

• Drafting an announcement after a release tag is created
• Explaining shipped changes and their impact on users
• Preparing acknowledgments for external contributors

Draft release notes from merged pull requests for releases that have already shipped. The skill filters internal changes, groups user-facing updates, matches the existing changelog style, and opens a pull request for human review.

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

• Draft release notes for a published tag
• Keep a changelog current through scheduled checks
• Catch up on several undocumented releases

Create a short WeChat group announcement and a tall PNG poster from Chinese release notes. The skill summarizes features and fixes, verifies credited contributors through GitHub, and includes their actual profile images.

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

• Preparing a WeChat group release announcement
• Turning release notes into a mobile-friendly poster
• Crediting contributors with verified GitHub profile images

Turn scan data into a categorized release notes draft covering features, fixes, breaking changes, and security. Get clean Markdown suitable for a CHANGELOG or GitHub release, with a review disclaimer and human approval required before publication.

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

• Draft release notes from scan results
• Organize features, fixes, breaking changes, and security updates
• Prepare Markdown for a CHANGELOG or GitHub release

Turn a structured change list into a categorized release notes draft for users. Follow the project's writing style, highlight breaking changes and security items, and include upgrade guidance where evident, leaving publication to human review.

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

• Drafting release notes from a structured change list
• Organizing features and bug fixes for users
• Highlighting breaking changes and security updates

Turns changelog-scan results into a readable, categorized release notes draft. Places breaking changes and security items at the top and ends with a human review note, providing a proposal for review.

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

• Turning scan results into a release notes draft
• Organizing release updates by category
• Highlighting breaking changes and security items

Draft or refresh Omnigent release notes for a specific version and commit range. Review merged pull requests, verify user-facing highlights and contributor credits, and deliver unpublished notes alongside a complete changelog preview.

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

• Draft release notes before a version tag exists
• Refresh a reviewed draft while preserving editorial changes
• Review breaking changes and upgrade guidance

Turns Git commits and pull request details into release notes for CHANGELOG.md, a release pull request, and Slack. It categorizes changes, explains user impact in plain language, and flags database migrations that need attention.

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

• Preparing release notes since the last release
• Summarizing changes across a specified version range
• Drafting a release pull request body