'change' 검색 결과

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

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

Record migration instructions for Prisma 8 breaking changes alongside the pull request. Prepare separate guidance for application users and extension authors, with optional code transformation scripts and checks that reproduce the required changes.

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

• Documenting migration steps for a breaking change
• Preparing separate app and extension upgrade guidance
• Testing migration scripts against pre-change code

Prepare a library release on GitHub by reviewing code changes, proposing a version number, drafting a changelog, and opening a release pull request. Version and changelog reviews let you confirm the details before proceeding.

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

• Choosing the next version from public API changes
• Drafting a changelog for library users
• Preparing a release branch and pull request

Create concise commit messages from a code diff, a file list, or a description of changes. The skill selects one emoji that matches the change’s purpose, follows gitmoji conventions, and explains the choice without running Git commands.

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

• Writing a commit message from a code diff
• Choosing an emoji that matches a change
• Matching the style of existing commit messages

Split a large pull request into smaller, reviewable changes. Plan branch dependencies, extract related code, verify each part, and track review changes while preserving the intent of the original work.

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

• Split a large pull request into reviewable parts
• Separate refactoring from behavior changes
• Plan dependent pull requests

Prepare employee communications for organizational changes, tool rollouts, and policy updates. Create announcements, audience-specific FAQs, manager talking points, and a communication calendar, while checking tone, channel choices, and sequencing against the change's impact.

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

• Preparing an internal reorganization announcement
• Planning communications for a new tool rollout
• Writing audience-specific FAQs for policy changes

Keep Kilo-specific changes small in files shared with upstream OpenCode. The skill guides where to place custom logic and tests, how to mark changes, and how to check annotations while preserving behavior.

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

• Add Kilo-specific features to shared upstream code
• Move additive logic into Kilo-owned files
• Clean up outdated or overly broad change markers

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

Guide a Verdaccio change through a pull request, from branch preparation and checks to changelog entries, labels, CI results, and review responses. Track separate pull requests when the fix also belongs on other release lines.

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

• Preparing and opening a pull request
• Investigating failed CI checks after a push
• Addressing review comments and updating the PR

Implement Verdaccio fixes, features, or refactoring after checking whether existing settings or plugins already solve the problem. Place changes in the responsible component, reuse helpers, add tests and release notes, and validate affected packages.

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

• Implementing a bug fix with a regression test
• Checking existing settings before adding a feature
• Refactoring code within a defined change

Scans merged pull requests and commits since a chosen reference, using titles, labels, milestones, and messages to categorize changes. Produces a release notes draft, highlights breaking changes and security items, and records the scan window.

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

• Collecting changes since the previous release tag
• Sorting updates into features, fixes, and other categories
• Identifying breaking changes and security items

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

Review merged pull requests and significant commits within a release window, then organize features, fixes, breaking changes, and security signals into structured source material for drafting release notes.

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

• Collecting changes since the last release
• Checking breaking changes and security signals
• Preparing source material for release notes

Scan merges and commits since the previous release to collect user-facing changes for a changelog. Produce structured entries and a summary, with explicit lists of breaking changes and security signals.

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

• Collecting changes since the previous release
• Organizing user-facing updates
• Listing breaking changes and security signals

Review release notes stored in changeset files before a release. Check that entries describe user-facing changes, group related updates, remove unnecessary implementation details, and commit the resulting edits.

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

• Reviewing changeset files before a release
• Grouping related changes into one release note
• Rewriting technical notes for users

Standardize Chinese Git commit messages and changelogs using Conventional Commits, a structured message format. The skill provides writing rules and configuration examples for message checks, interactive commit entry, and automatic changelog generation.

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

• Standardizing Chinese commit messages across a team
• Checking commit formats with commitlint and husky
• Generating changelogs with Chinese section headings

Compare code structure across two commits, tags, or directories to identify security-relevant changes. Produces a report on new attack paths, privilege boundaries, complexity, and how widely a change could affect other functions.

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

• Compare code structure before a release
• Investigate new attack paths after code changes
• Track untrusted data flows across a refactor

Track multiple Claude sessions working on one project, check that changes reached main with screenshots and changelog entries, verify the live site, and identify finished sessions, interrupted work, and questions awaiting the user.

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

• Reviewing progress across parallel Claude sessions
• Checking merged changes, changelog images, and the live site
• Archiving finished sessions after preserving screenshots

Evaluate staged Git changes before committing using an LLM, a language model acting as a reviewer. Receive correctness, completeness, and safety scores, plus issues by severity, to decide whether to fix, commit, or stop.

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

• Evaluate significant changes before committing
• Review changes in unfamiliar code
• Check changes to security-sensitive code

Convert a git log, commit list, or release notes into a polished, user-facing changelog. Use when writing release notes, generating a CHANGELOG.md entry, or documenting what changed in a version. Produces a structured changelog section with version header, categorised changes, and migration notes. For an already-curated change list use changelog-writer instead.

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

Assists with managing versioning and changelogs in JavaScript/TypeScript monorepos using Changesets. Use when automating semantic versioning, generating changelogs from PRs, coordinating multi-package releases, or publishing to npm. Trigger words: changesets, versioning, changelog, npm publish, monorepo release, semver.

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

Generate a markdown report documenting codebase changes from the current session -- files added, modified, deleted, and a summary of what was done. Use when asked to "document changes", "generate change report", "save changes report", "what did I change", "session report", "summarize my changes", or "write a changes report".

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

Generate a markdown report documenting codebase changes from the current session — files added, modified, deleted, and a summary of what was done. Use when asked to "document changes", "generate change report", "save changes report", "what did I change", "session report", "summarize my changes", or "write a changes report".

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