'changes' 검색 결과

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 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

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

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

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 financial models after earnings, new company guidance, or changes in assumptions. Revise forecasts, recalculate valuation and price targets, and summarize significant changes with their reasons and implications for the investment view.

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

• Updating a financial model after quarterly earnings
• Revising forecasts after changes in company guidance
• Reflecting interest rate and currency changes in valuation

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

Save a page's SEO settings and compare them with later versions to detect changes after updates or deployments. Review differences in titles, headings, indexing controls, structured data, and available performance metrics, with severity levels and stored comparison history.

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

• Compare SEO settings before and after deployment
• Check for unintended title or heading changes
• Investigate page changes after a traffic drop

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

Write a single-line commit message for Ant Design by reading staged changes, the changes selected for the next commit. It summarizes the full commit intent and follows the style of recent repository commits.

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

• Write a message for staged changes
• Match the style of recent commits
• Summarize changes across multiple files in one line

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

Review local code changes with git diff and update the matching pages under docs/. Keep commands, settings, examples, and navigation aligned with current behavior so readers can understand the changes without reading the code.

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

• Documenting uncommitted feature changes
• Updating setup instructions after a refactor
• Replacing outdated commands and configuration examples

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

Archive several OpenSpec changes together after reviewing their documents, task completion, and specification conflicts. The agent checks actual code to decide which specification updates to apply, asks for confirmation, and reports successes, skipped changes, and failures.

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

• Archiving several completed changes together
• Reviewing incomplete documents and tasks before archiving
• Resolving overlapping specifications using implementation evidence

Check Google Cloud IAM allow policy changes against the last 90 days of access logs. The skill identifies access that could be lost and applies changes only after a successful simulation and user approval.

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

• Checking access impact before removing a role
• Reviewing allow policy changes across resource scopes
• Applying policy changes after simulation and approval

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

Review Apache Pinot changes for compatibility with existing configurations and consumers. Covers public APIs, extension interfaces, serialized data formats, and REST responses, helping focus code review on changes that may affect existing users.

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

• Reviewing changes to configuration fields
• Checking compatibility after extension interface changes
• Reviewing enum and schema type changes

Review Apache Pinot changes for concurrency and state safety, including locks, shared callbacks, lifecycle changes, and distributed metadata. Use it to examine how changes affect shared state when multiple operations run at the same time.

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

• Reviewing changes to locks and atomic operations
• Checking shared callback registration changes
• Reviewing Helix state transitions and ZK node changes

Archive several OpenSpec changes together after reviewing their documents, task completion, and specification conflicts. The agent checks actual code to decide which specification updates to apply, asks for confirmation, and reports successes, skipped changes, and failures.

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

• Archiving several completed changes together
• Reviewing incomplete documents and tasks before archiving
• Resolving overlapping specifications using implementation evidence

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".

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

지정한 커밋이나 브랜치를 기준으로 코드 변경을 검토합니다. 문서화된 개발 규칙 준수와 요구 사항 구현을 별도로 확인하고 두 관점의 지적 사항을 나누어 보고합니다.

• 브랜치나 PR의 변경 검토
• 지정 커밋이나 태그 이후 변경 확인
• 문서화된 개발 규칙과 대조

Compare a Git diff with its stated purpose to flag potentially unrelated files, added dependencies, API renames, and configuration changes. Receive recommendations to keep, split, or justify changes, with a proposed grouping for follow-up work.

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

• Check scope before opening a pull request
• Find unexpected changes in a bug fix
• Review whether staged changes are too broad

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