Results for “dependency-update”

Provides structured prompts for analyzing, planning, and executing .NET framework upgrades, covering project assessment, dependency management, code modernization, CI/CD updates, testing, and documentation.

Upgrades outdated Maven dependency versions in AEM Cloud Service pom.xml files, handling both literal <version> and same-pom ${property} shapes.

Updates the dbskill collection from the official repository when the user requests an update, upgrade, or check for updates.

Bring an existing brand's setup up to date with the latest plugin version — detects gaps since the user last ran brand-setup and fills them interactively.

Upgrade Expo SDK versions and fix dependency issues with step-by-step guidance.

Update an existing implementation plan file with new or updated requirements for features, refactoring, package upgrades, design, architecture, or infrastructure.

Check minimum dependency versions for React 18.3.1 and React 19 compatibility, resolve peer dependency conflicts, and decide on upgrade strategies.

Upgrades or migrates an Android project from any legacy Google Play Billing Library version to the latest stable version, with automated discovery, planning, and verification.

Upgrade Expo SDK versions and fix dependency issues with step-by-step guidance.

Guidelines for upgrading Expo SDK versions and fixing dependency issues

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". Voice triggers (speech-to-text aliases): "upgrade the tools", "update the tools", "gee stack upgrade", "g stack upgrade".

Add or update features in existing application. Used for iterative development.

Ready-to-use prompts for comprehensive .NET framework upgrade analysis and execution

Fenxiang Update

Use this skill to monitor a deployed URL for regressions after deploys, merges, or dependency upgrades.

Demonstrates pinned dependency metadata.

Guide a structural migration or dependency upgrade with a step-by-step plan and verification

Use this skill when upgrading or migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL.

Upgrade gstack to the latest version.

Assesses and automates upgrades of Azure workloads between plans, tiers, or SKUs, and modernizes Azure SDK for Java dependencies in source code.

Applies the same change across multiple repositories in parallel using git worktrees, tests, and pull requests.

PUA Pro extensions: self-evolution notes, compaction state continuity, KPI-style summaries, flavor switching, and feedback tools.

Fix F821 undefined name errors for optional dependencies using TYPE_CHECKING

Analyzes dependencies between stories, code modules, tickets, or specs to compute an optimal implementation order with parallel batches, cycle detection, and critical path analysis.

Cut a Han release: update CHANGELOG.md with the changes since the last release, bump every plugin that changed, tag every plugin as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release whose notes attribute every merged pull request to its author, credit every closed issue to the person who opened it, the people who contributed to it, and the people who worked on the fix, and link back to the full changelog for that version. Han ships as a parent meta-plugin (`han`) plus child plugins (`han-core`, `han-github`, `han-reporting`, and any future `han-*` extension); the skill versions each plugin independently and tags each one independently, with the release attaching to the parent's tag. Use when releasing, cutting a release, shipping a new Han version, publishing release notes, or tagging a version. Reads each plugin's target version from its plugin.json; when a plugin has not been bumped past the latest tag yet, it proposes a semantic-versioning bump and conf