'change' 검색 결과

Collect pull requests between Ant Design versions and turn user-facing changes into Chinese and English changelog drafts. Filter internal changes, highlight release priorities, add contributor links, and update both changelog files after preview confirmation and format checks.

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

• Collecting changes between a release tag and a target branch
• Preparing Chinese and English release notes together
• Filtering internal changes and highlighting release priorities

Prepare user-facing changelog entries for source code changes. The skill determines whether an entry is needed, classifies the change, writes a clear title, and uses the project CLI to create a JSON file tied to the pull request.

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

• Add a changelog entry for a bug fix
• Classify a new feature or behavior change
• Explain a breaking change and its replacement

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

Parse git history and produce or update a CHANGELOG.md following the Keep a Changelog convention. Supports Conventional Commits, basic prefix conventions, and unstructured commit messages. Intelligently categorizes changes, detects breaking changes, links to PRs/issues, and handles both initial generation and incremental updates. **Triggers — use this skill when:** - User asks to "generate", "create", "update", or "write" a changelog - User mentions "CHANGELOG", "changelog", "release notes" - User says "document changes", "what changed since last release" - User wants to "prepare a release" and needs a changelog entry - User asks to "clean up" or "reformat" an existing changelog **Covers:** Any git-based project. Handles Conventional Commits (feat/fix/chore), Angular convention, basic prefixes (Add/Fix/Remove), and freeform commit messages. Outputs Keep a Changelog format with optional Common Changelog enhancements.

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

Prepare a CHANGELOG.md entry for a Storybook minor or major release. Collect changes from prereleases, filter out changes already backported to patch releases, select significant highlights, and combine them with the full change list.

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

• Prepare a changelog for a Storybook minor release
• Summarize major release highlights
• Consolidate changes from prereleases

Read recent releases from CHANGELOG.md and display their version numbers, dates, and complete change sections. Choose how many entries to show, or view the full history while preserving the document’s formatting.

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

• Reviewing the five most recent releases
• Checking changes across ten releases
• Reading the complete release history

Plan organizational changes such as tool migrations, restructures, and strategy shifts using ADKAR, a five-stage model for adopting change. Structure communication, training, and follow-up while addressing employee concerns, resistance, and fatigue from overlapping changes.

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

• Plan communication and training for a tool migration
• Prepare reorganization announcements and employee FAQs
• Explain a strategy shift and its impact on teams

Create changelog files for significant changes in a pull request, a proposed code change. Describe effects users will notice and organize entries by PR number and change type, such as features or fixes.

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

• Writing changelog entries for a pull request
• Separating new features from bug fixes
• Explaining changes in user-facing language

Prepare user-facing changelogs for stable Paperclip releases from commits, change records, and merged pull requests. Group related changes, identify breaking changes, and explain upgrade actions using the beta version selected for release.

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

• Preparing changelogs for stable releases
• Documenting breaking changes and upgrade steps
• Summarizing changes since the previous stable release

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

Generate commit messages from git diffs, staged changes, or written descriptions. Explain the reason and problem behind each change using Conventional Commits, a structured message format, and suggest separate messages for unrelated changes.

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

• Writing a commit message from staged changes
• Recording why a bug fix was needed
• Splitting unrelated changes into separate commit messages

Review FastGPT pull requests or local branch changes by examining actual code differences. Explain behavior changes and affected areas, identify unrelated changes, and report concrete concerns about code quality, consistency with nearby implementations, and missing test coverage.

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

• Understanding the behavior changes in a FastGPT pull request
• Comparing a local branch with upstream/main
• Identifying unrelated changes or excessive refactoring

Turn a selected range of commits or merged pull requests into release notes grouped by change type. Describe user-visible effects, link to supporting changes, and highlight breaking changes so readers can assess an upgrade.

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

• Write release notes covering changes since the last tag
• Summarize pull requests merged during a selected period
• Highlight breaking changes before an upgrade

Prepare Bifrost releases by turning Git history into release summaries and module changelogs. Coordinate version updates across dependent modules, document database migration risks, and include closed issues and outside contributor credits.

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

• Preparing changelogs for a Bifrost release
• Coordinating version updates across dependent modules
• Documenting database migration rollback limits

Follow a release workflow for game changes, from screenshots and changelog entries through testing, commits, and live deployment. Verify the published version, measure transfer sizes, and report evidence while applying approval rules for large uploads.

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

• Releasing game features or fixes with screenshots
• Adding a versioned changelog entry with images
• Testing changes after integrating the latest main

Compare current code with the latest published npm releases to identify unpublished changes. Read actual code differences, explain their impact across shared components and agent environments, and recommend version updates for each release layer.

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

• Reviewing unpublished changes before a release
• Drafting release notes from actual code changes
• Choosing version updates for each release layer

Update a project's changelog using GitHub releases, git history, and code differences. Select changes that matter to users, match the existing format, and write concise entries for the requested release.

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

• Add the latest missing release entry
• Align changelog text with GitHub Releases
• Summarize changes between release tags

Create English and Chinese changelogs for PuerTS releases on Unity or Unreal. Review platform-specific Git commits, investigate unclear changes, and summarize their impact on users using each platform’s required format.

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

• Preparing a Unity release changelog
• Preparing an Unreal release changelog
• Updating English and Chinese changelogs together

Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed since last release", this is the skill to use. Do NOT manually edit CHANGELOG.md without this skill — it ensures proper formatting, user-perspective writing, and website changelog sync. For full release workflows (Release PR review, tests, draft assets, publication, announcements), use /release instead.

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

Update the Unreleased section of CHANGELOG.md based on current changes. No-op if CHANGELOG.md does not exist. Use when the user asks to "update changelog", "add to changelog", "update the changelog", "changelog entry", "add changelog entry", or "log this change".

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

Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".

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

Use when enabling, configuring, or monitoring Change Data Capture (CDC) entity selection, channel enrichment, and delivery usage limits from an admin perspective. Covers the PlatformEventChannel and PlatformEventChannelMember metadata, the standard ChangeEvents channel, custom __chn data channels, enrichedFields, filterExpression, destructive deselection, and PlatformEventUsageMetric / EventBusSubscriber monitoring. Trigger keywords: change data capture, CDC, entity selection, change event, platform event channel, channel member, enrichment, event delivery allocation. NOT for writing an Apex change-event trigger — use apex/change-data-capture-apex. NOT for subscribing an external system over Pub/Sub or CometD — use integration/change-data-capture-integration.

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

Turn Git commits, records of code changes, into clear release notes for users. The skill groups updates by type, rewrites technical descriptions in plain language, and filters out internal work such as refactoring and tests.

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

• Preparing release notes for a new version
• Summarizing weekly or monthly product updates
• Writing app store update descriptions

Revise an existing OpenSpec change plan and reconcile related planning documents. Incorporate new decisions, identify contradictions or gaps, and apply proposed document edits after confirmation, while leaving implementation code untouched.

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

• Incorporating new decisions into an existing change plan
• Checking planning documents for contradictions
• Reconciling related documents after an edit