Plan and carry out a controlled migration of an Algolia JavaScript client from v4 to v5. Inventory package versions and API usage, update method calls and waits against the installed types and official migration guidance, run compatibility checks, and document remaining gaps and rollback steps.
Migrate an Algolia JavaScript client integration from v4 to v5 with inventory, compatibility tests, and rollback. Use when removing initIndex, updating client methods, or reconciling mixed major versions. Trigger with "upgrade Algolia v5", "remove initIndex", or "Algolia SDK migration".
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
This skill follows the official v5 migration contract and the repository's pinned dependency graph. It treats import, method, parameter, response, wait, and test changes as one controlled migration.
Use Read, Glob, and Grep to inspect local code, configuration names, tests, and dependency versions. Use WebFetch only for current official Algolia documentation. Use Write or Edit only after identifying the target files, constraints, and verification plan.
initIndex; methods live on the client and receive indexName.Do not change key privilege during an SDK upgrade. Use existing least-privilege test credentials only for safe verification targets.
initIndex, client wrappers, methods, waits, mocks, and runtime targets.Do not combine the SDK upgrade with relevance, index schema, credential, or broad architectural changes unless separately scoped and tested.
Return the usage inventory, official mapping, dependency diff, migrated boundaries, test evidence, remaining v4 patterns, compatibility notes, and rollback.
| Condition | Response |
|---|---|
initIndex remains | Locate the call or generated artifact and migrate it. |
| Method signature differs | Follow installed v5 types and current official reference. |
| Mock passes but live test fails | Correct the application adapter contract. |
| Rollback changes lockfile only | Revert source and lockfile as one unit. |
Use this compact input and expected handoff to calibrate scope and evidence quality.
Input:
from=algoliasearch-4; to=pinned-5; initIndex-calls=9; wrappers=2
Expected handoff:
initIndex=0; typecheck=pass; integration=pass; disposable-write-cleaned=yes
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.
Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.
Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.
Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.
Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.
Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.