'upgrade' 검색 결과

Provides prompts for assessing and planning .NET upgrades across multiple projects. Helps identify compatibility issues, order migration work, propose code and build pipeline changes, and prepare testing checklists, review guidance, and release documentation.

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

• Assessing project structure and dependency compatibility
• Planning an incremental upgrade with rollback checkpoints
• Reviewing deprecated APIs and NuGet package replacements

Audit dependency files across eight language ecosystems for built-in vulnerability patterns, license conflicts, and indirect dependency risks. Generate a prioritized upgrade plan with testing and rollback notes, and pair results with live audit tools for current vulnerability coverage.

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

• Auditing third-party packages before a release
• Checking dependencies against built-in CVE patterns
• Reviewing license conflicts across dependency chains

Audit and upgrade NemoClaw dependencies, including Hermes and base images. Trace upstream changes to affected code, implement required migrations, and verify tests, distributed artifacts, and the versions actually selected for use.

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

• Assess the impact of a dependency upgrade
• Plan migrations for a Hermes upgrade
• Verify base images and selected artifacts

Guide OpenRig CLI and background service upgrades while protecting active sessions and local file changes. The skill provides staged checks, verified database backups, selective plugin refreshes, and migration helpers, with evidence checked after each change.

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

• Upgrading OpenRig while preserving active sessions
• Backing up and checking the database before an upgrade
• Refreshing managed plugins while preserving local edits

Review smart contract projects against Trail of Bits development guidelines. Examines architecture, upgrade mechanisms, implementation, dependencies, and tests, then provides system documentation, identifies gaps, and recommends improvements in priority order with code references.

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

• Review smart contract architecture
• Check upgrade and proxy designs
• Identify gaps in specifications and documentation

Update Remotion and its related packages while keeping their versions aligned. The workflow checks project dependencies, updates installed Remotion skills and lockfiles, and reviews changes using the project's existing package management conventions.

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

• Update Remotion and related packages together
• Align Remotion versions across workspaces
• Adjust auxiliary dependencies during an upgrade

Upgrade the chat app’s fast or good model slot across Rust backend code and the frontend. Updates model definitions, selection logic, generated types, and display names, then checks compilation and consistency.

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

• Upgrade the default chat model
• Replace the smart mode model
• Align backend definitions with frontend model labels

Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".

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

Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code. WHEN: upgrade Consumption to Flex Consumption, upgrade Azure Functions plan, change hosting plan, function app SKU, migrate App Service to Container Apps, modernize legacy Azure Java SDKs (com.microsoft.azure to com.azure), migrate Azure Cache for Redis (ACR/ACRE) to Azure Managed Redis (AMR).

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

Upgrade Apify SDK, apify-client, and Crawlee versions safely. Use when migrating between SDK versions, handling breaking changes, or updating from Apify SDK v2 to v3 (Crawlee split). Trigger with "upgrade apify", "apify migration", "apify breaking changes", "update apify SDK", "crawlee upgrade", "apify v2 to v3".

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

Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code. WHEN: upgrade Consumption to Flex Consumption, upgrade Azure Functions plan, change hosting plan, function app SKU, migrate App Service to Container Apps, modernize legacy Azure Java SDKs (com.microsoft.azure to com.azure), migrate Azure Cache for Redis (ACR/ACRE) to Azure Managed Redis (AMR).

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

Create the release notes and upgrade guide for a mariadb-operator release. Given the release PR whose body lists every PR included in the release, it gathers each PR, groups the changes by relevance, and produces `docs/releases/RELEASE_<version>_HEADER.md.gotmpl` and `docs/releases/UPGRADE_<version>.md` in the format the previous releases use, then opens a PR targeting `release-<version>`. If no release PR is provided it asks for the new version and infers the changes from git history since the last tag. Use whenever the user wants release notes, an upgrade/update guide, or docs for a new mariadb-operator version — "create the release notes for 26.10.0", "write the upgrade guide", "document this release", "prepare the release PR docs" — even if they don't mention a release PR.

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

In-app paywall and upgrade screen optimization covering feature gate design, usage limit UX, trial expiration flows, upgrade trigger timing, save offer strategy, and ethical monetization patterns.

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

Migrate, modernize, and upgrade codebases to AWS. Run analysis on repos for tech debt, security vulnerabilities, and modernization opportunities. Transforms .NET Framework to .NET 8/10, mainframe COBOL to Java, VMware VMs to EC2, SQL Server to Aurora, and upgrades Java/Python/Node.js versions and AWS SDKs. Use when the user says "migrate .NET to AWS", "upgrade Java to 17/21", "modernize COBOL", "modernize mainframe", "move VMware to EC2", "convert SQL Server to Aurora", "upgrade Python version", "migrate AWS SDK", "transform this codebase", "analyze for issues", "find tech debt", "what tech debt", "security vulnerabilities", "CVEs", "what's wrong with my code", "assess my repos", "where do I start", "find what's outdated", "analyze my repos", "AWS Transform - continuous modernization", "continuous modernization" or "continuous-modernization". Don't use for infrastructure provisioning, CI/CD pipelines, or general coding tasks.

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

Guided setup and upgrade-check experience for Lattice projects -- scans the repository, detects existing configuration and outdated conventions, suggests refiners and available upgrades in priority order, and creates or reconciles the .lattice/ config. Bridges the gap between installing skills and getting first value, and between upgrading Lattice and adopting its newest conventions. Use when the user says 'lattice init', 'set up lattice', 'initialize lattice', 'get started with lattice', 'configure lattice for this project', 'check for lattice upgrades', or 'upgrade lattice conventions'.

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

Decision and migration guide for Prisma ORM MongoDB projects on v6, which have no upgrade path to v7. Use when a MongoDB project asks about upgrading Prisma, when "upgrade to prisma 7" comes up in a project with provider = "mongodb", or when evaluating a move to Prisma 8. Triggers on "upgrade prisma mongodb", "prisma 7 mongodb", "mongodb prisma migration", "prisma 8 mongodb".

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

Upgrade gstack to the latest version. Detects global vs vendored install, runs the upgrade, and shows what's new. Use when asked to "upgrade gstack", "update gstack", or "get latest version".

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

Upgrade Prisma Next in your app. Bumps every `@prisma-next/*` dependency from the version pinned in the lockfile to the requested target (or npm `latest`), applies any required code-translation steps from the per-transition upgrade instructions, validates with the project's own typecheck + tests, and commits each minor step on its own. Use when the user asks to "upgrade Prisma Next", "bump Prisma Next", "move to Prisma Next X.Y", or asks an agent to deal with an `@prisma-next/*` minor bump in their app.

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

Upgrade Prisma Next in your extension. Bumps every `@prisma-next/*` dependency to the requested target (or npm `latest`), runs the per-transition upgrade instructions for the extension SPI (middleware lifecycle, codec / migration-tools / framework-components churn, seed-migration on-disk shape), verifies the pins are correctly exact via `prisma-next-check-pins`, runs the extension's own typecheck and tests, and commits each minor step on its own. Use when the user asks to "upgrade Prisma Next" in an extension package, or to update an extension's `@prisma-next/*` deps to a new minor.

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

Guide users through `pulp upgrade` — discover new CLI releases, interpret migration notes for the hop they're performing, and apply breaking-change fixes (CMake macro renames, API surface changes, config file moves). Handles "upgrade pulp", "what's new", "migrate my project", "show breaking changes", and the `/upgrade` slash command. Pairs with the embedded migration index shipped in the CLI binary.

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

Use when planning, implementing, or reviewing frontend dependency upgrades, package migrations, lockfile changes, major framework version bumps, CVE remediation, peer dependency conflicts, ESM/CJS shifts, build-tool compatibility, or CI verification matrices; Chinese triggers include dependency upgrades, version upgrades, lockfile, peer dependency, CVE fixes, major version migrations.

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

Safe systematic dependency upgrade with vulnerability scanning and rollback capability. Detects project ecosystem, audits outdated and vulnerable packages, presents a prioritized upgrade plan, and executes upgrades one at a time with test verification after each. Use when updating dependencies, fixing vulnerability alerts, or performing periodic dependency maintenance.

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

Use when a subscriber admin is installing, upgrading, or rolling back a managed package (1GP or 2GP) sourced from AppExchange or a private install URL — covers pre-install evaluation, sandbox dry runs, license and dependency checks, the install/upgrade audit trail, post-install configuration the package's InstallHandler cannot perform, and uninstall fallback. NOT for building managed packages as an ISV (use devops/managed-package-development), unlocked-package development (use devops/unlocked-package-development), or AppExchange listing setup. Trigger keywords: InstalledPackage, installedPackages, securityType, activateRSS, sf package install, sf package installed list, PackageLicense, UserPackageLicense, AllowedLicenses, UsedLicenses, push upgrade, PackageSubscriber, namespace prefix, 04t, certified managed package limits.

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

Reconcile baseline-versioned files that the `create-baseline upgrade` CLI staged for LLM-assisted semantic merge. Use when the CLI prints "Open Claude Code and run /upgrade-project to reconcile". Reads the stage manifest at `.claude/state/upgrade/<ts>/manifest.json`, reasons through each pending file's three-way delta in main context, writes a reconciled LOCAL, then deletes the stage when every file lands. Supports `--dry-run` (preview the reconciled diff without writing) and a structured "needs-user-input" fallback when the conflict cannot be disambiguated automatically.

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