algolia-upgrade-migration
Upgrade algoliasearch from v4 to v5 with breaking change detection and codemod. Use when upgrading SDK versions, detecting deprecations, or migrating initIndex patterns. "update algolia SDK", "algolia v4 to v5". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill algolia-upgrade-migration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Algolia Upgrade & Migration (v4 to v5) ## Overview Guide for upgrading `algoliasearch` from v4 to v5. The v5 release is a major rewrite: `initIndex()` is removed, all methods move to the client, and the import style changes. ## Prerequisites - Current `algoliasearch` v4 installed - Git for version control (work in a branch) - Test suite passing on current version ## Breaking Changes Summary | v4
What does the algolia-upgrade-migration skill do?
Upgrade algoliasearch from v4 to v5 with breaking change detection and codemod. Use when upgrading SDK versions, detecting deprecations, or migrating initIndex patterns. "update algolia SDK", "algolia v4 to v5". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill algolia-upgrade-migration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
