“change”的搜索结果

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.

中文简介正在准备中。当前显示原文说明。

从Git提交历史生成面向用户的更新日志或发行说明，按新功能、改进、修复等类别整理，将开发者用语改写为易懂的表述，并过滤内部代码整理和测试。

• 编写新版本发行说明
• 汇总每周或每月产品更新
• 编写应用商店更新说明

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

Review changes since the last npm release through parallel change analysis, hands-on quality checks, and an overall release assessment. Receive a readiness verdict, blocking issues, version recommendations, and a draft changelog with compatibility concerns.

中文简介正在准备中。当前显示英语简介。

• Assess readiness before an npm release
• Check breaking changes and migration needs
• Review version bump recommendations

Prepare Apache Airflow provider releases by classifying pending changes, inspecting pull request diffs for compatibility risks, and applying version bumps and changelog entries. Use existing breeze tooling to regenerate release documentation and consult the release manager on uncertain decisions.

中文简介正在准备中。当前显示英语简介。

• Prepare documentation for a regular provider release cycle
• Classify changes for a selected set of providers
• Review breaking changes and choose version bumps

Add a new exchange integration to CCXT using TypeScript and established exchange templates. Follow guidance for unified methods, data conversion, authentication, sandbox settings, recorded API test data, documentation, and checks across generated language implementations.

中文简介正在准备中。当前显示英语简介。

• Add an exchange that CCXT does not yet support
• Convert exchange responses into CCXT's common data format
• Record real API responses for regression tests

Build workflows that generate changelogs and release notes from commits, pull requests, and releases. Use Keep a Changelog formatting, standardize commit messages with Conventional Commits, and manage version numbers through Semantic Versioning rules.

中文简介正在准备中。当前显示英语简介。

• Automating changelog generation from commits and pull requests
• Standardizing team commit messages
• Setting up GitHub or GitLab release notes

Prepare a structured request for a system or process change, covering business reasons, affected users, risks, implementation steps, stakeholder communications, required approvals, and a rollback plan that explains how to reverse the change.

中文简介正在准备中。当前显示英语简介。

• Prepare a system change request for approval
• Document deployment risks and rollback steps
• Plan stakeholder communications for a rollout

Turn Git history into release notes and recommend the next version based on commit types and breaking changes. Check commit formatting, filter changes by package, and generate Markdown or JSON for automated release workflows.

中文简介正在准备中。当前显示英语简介。

• Prepare release notes before publishing a version
• Determine the next version from commit history
• Check commit message formats before merging

Turn Git commits and sprint records into internal and player-facing game changelogs. Group related features, fixes, and balance changes, retain technical references for the team, and describe player-visible changes in clear language.

中文简介正在准备中。当前显示英语简介。

• Preparing a changelog for a game version
• Summarizing changes completed during a sprint
• Writing an internal record with commit references

Review Handsontable code changes for architecture, code quality, performance, accessibility, and test coverage. Findings include severity, confidence, and file locations, helping developers assess whether changes follow project rules and demonstrate the intended behavior.

中文简介正在准备中。当前显示英语简介。

• Review a Handsontable branch or pull request
• Check architecture before or during core changes
• Review keyboard access and performance concerns

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

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

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

Prepare a software release by analyzing code changes, writing English and Chinese release notes, updating versions with changeset, and creating commits and a release pull request for review before automated publishing.

中文简介正在准备中。当前显示英语简介。

• Preparing a patch release after bug fixes
• Writing English and Chinese release notes
• Creating a release pull request for a protected main branch

Turn a list of changes, commits, or PRs into clean release notes / a changelog entry. Use when asked to write release notes, a changelog, or a version announcement from raw changes. Produces a Keep-a-Changelog-style entry grouped by type (Added/Changed/Fixed/etc.), written for users — surfacing breaking changes and upgrade notes up top. To go straight from a raw git log use changelog-generator instead.

中文简介正在准备中。当前显示原文说明。

Create or update a structured change log for a product or platform. Use when someone asks to "create a change log", "log this change", "what changed", "update the change log", "release notes", or "changelog". Reads project memory (CLAUDE.local.md Recent Changes) and meeting notes to build chronological change records. Supports init (backfill from memory), update (append new entries), and release (summarize for a version).

中文简介正在准备中。当前显示原文说明。

Maintain a changelog following Keep a Changelog format. Covers entry categorization (Added, Changed, Deprecated, Removed, Fixed, Security), version section management, and unreleased tracking. Use when starting a new project that needs a changelog, adding entries after completing features or fixes, preparing a release by promoting Unreleased entries to a versioned section, or converting a free-form changelog to Keep a Changelog format.

中文简介正在准备中。当前显示原文说明。

Analyzes git commit history and generates professional changelogs with semantic versioning, conventional commit support, and multiple output formats (Keep a Changelog, Conventional, GitHub). Use when editing CHANGELOG.md, CHANGELOG.txt, or HISTORY.md files, preparing release notes, creating releases, bumping versions, updating changelog, documenting changes, writing release notes, tracking changes, version bump, tag release, or when user mentions "changelog", "release notes", "version history", "release", "semantic versioning", or "conventional commits".

中文简介正在准备中。当前显示原文说明。

組織変革管理の専門コンサルタントスキル。システム導入、組織変革、DXプロジェクトにおける変革管理を支援。 ADKAR、Kotter 8-Stepフレームワークに基づき、ステークホルダー影響度分析、コミュニケーション計画、抵抗管理戦略を提供。 Use when managing organizational change, system implementations, digital transformation projects, or improving user adoption rates. Triggers: "change management", "organizational change", "system implementation", "user adoption", "change strategy", "stakeholder engagement".

中文简介正在准备中。当前显示原文说明。

从Git历史重新生成OpenClaw发布用的更新日志，按用户影响归纳变更，保留Issue、PR引用与贡献者署名，并核查遗漏、已撤销变更及已发布说明。

• 在stable版发布前编写更新日志
• 整理相对上次beta基准的变更
• 核查贡献者署名与PR引用