Loading...
Loading...
Found 11 Skills
Upgrade JavaScript dependencies using npm-check-updates, then run post-upgrade checks to ensure nothing is broken.
Update AG Grid, AG Charts and AG Studio dependencies to a newer version
Migrate a Grafana plugin to React 19 compatibility. Use when the user asks to update a plugin for React 19, prepare for React 19, fix React 19 compatibility, upgrade to React 19, migrate to React 19, bump grafanaDependency to 12.3.0, externalize jsx-runtime, or run react-detect. Triggers on phrases like "update plugin for React 19", "React 19 migration", "prepare for React 19", "plugin React 19 compat", "grafanaDependency 12.3.0", "JSX runtime externals", "react-detect", "SECRET_INTERNALS", "ReactCurrentOwner", or "ReactCurrentDispatcher".
Upgrade dependencies safely using pnpm catalog, checking for breaking changes, and testing upgrades. Use when updating packages, applying security patches, upgrading major versions, resolving dependency conflicts, or modernizing tech stack.
Upgrade Python dependencies using uv, then run post-upgrade checks to ensure nothing is broken.
Audit and optimize an existing Convex app: security, scale, upgrades, observability.
Review Python dependencies for known security advisories, stale version pins, and unsafe upgrade paths. Use when users ask for dependency security reviews, requirements or lockfile audits, upgrade planning, pre-release risk checks, or remediation prioritization for Python projects.
Keep JavaScript/TypeScript dependencies fresh with safety rails and monorepo support.
Use this skill when migrating a Taiga UI project to a new major version. Before starting, confirm with the user which major versions are involved (e.g. v4 → v5). Substitute the source version as CURRENT_MAJOR and the target version as NEXT_MAJOR throughout this workflow. Also invoke when running migration schematics, handling migration TODOs left after `ng update` or `nx migrate`, asked to fix TODOs, clean up migration notes, resolve deprecation warnings, or work with @taiga-ui/legacy package. Follow the complete migration workflow: gather context, prepare environment, run schematics, review changes, handle TODOs, and troubleshoot common issues. Resolve every actionable TODO only when the surrounding code proves the fix is safe; otherwise inspect more context or ask the user before changing behavior, templates, styles, or scripts.
Upgrade an existing EmDash project with upgrade-emdash, interpret .emdash/UPGRADE.md, apply required project changes, and verify the package, skill, and migration result. Use when asked to update or upgrade EmDash dependencies. Do not use for an unrelated schema change or a known database migration without a package upgrade.
Diagnoses the health of a project's PostHog SDK integrations — which SDKs are out of date and how to fix them. Use when a user asks about PostHog SDK versions, outdated SDKs, upgrade recommendations, "SDK health", "SDK doctor" (the former name), or when events or features seem off and it might be due to an old SDK.