'change' 검색 결과

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 참조 표기 확인

REA의 Git 이력을 특정 버전으로 고정해 변경 이력과 릴리스 노트를 정리합니다. 기여자 감사 표기를 검증하고 Release Please의 공개 본문과 일치하는지 확인합니다.

• Git 이력으로 릴리스 노트 작성
• 사용자에게 미치는 변경 영향 정리
• 기여자 감사 표기와 이슈 링크 확인

코드, 데이터, API 변경 전에 실제 의존 관계로 영향 범위와 검증·복구 절차를 정리합니다. 구현 후 차이와 계획을 대조해 누락과 범위 이탈을 확인합니다.

• API 변경의 영향 범위 확인
• 데이터베이스 이전과 복구 계획 점검
• 인증 변경의 모듈 간 영향 확인

Prepare code changes for sharing by merging the base branch, running tests, and reviewing the diff. Update VERSION and CHANGELOG, then commit, push, and create a pull request, a proposal to merge the changes.

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

• Create a pull request for completed work
• Test and review changes before pushing
• Merge the base branch before sharing changes

Manage OpenSpec releases by auditing merged changes and release records, checking release pull requests, and verifying publication. Support stable and beta releases, resume from the current GitHub state, and finish with polished release notes.

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

• Checking release readiness and missing change records
• Preparing a pull request for missing release records
• Resuming a release after human approval

Archive several OpenSpec changes together after reviewing their documents and task progress. The skill checks code to resolve overlapping specification updates, syncs the selected updates, and reports which changes were archived, skipped, or failed.

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

• Archive several completed changes together
• Resolve overlapping specification updates
• Review unfinished work before archiving

Assess whether a code change is small enough to review using line-count guidance. For larger changes, examine the actual differences, dependencies, and calling code to suggest reviewable stages and the smallest coherent first step.

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

• Check the size of a change before requesting review
• Assess the scope of a complex logic change
• Plan reviewable stages for a large change