Results for “pandas-migration”

Manage Migration entities — pending, in-progress, and applied transitions between upstream source versions. Use when an upstream source bumps version (processkit, a host installer, or a community package), when a user wants to draft a migration plan, when an agent needs to reason about pending migrations, or when working through an in-progress migration.

Migrate Claude Code configuration, skills, agents, and MCP servers to Codex project and global files.

Guides embedding model migration in Qdrant without downtime, covering alias swap, side-by-side, and hybrid search strategies.

Extends pandas for geospatial vector data analysis, including reading/writing shapefiles, GeoJSON, GeoPackage, and PostGIS, performing spatial joins, geometric operations, coordinate transformations, and creating static or interactive maps.

Audit, plan, implement, or review Model Context Protocol version and SDK migrations. Use for MCP 2026-07-28, stateless Streamable HTTP, server/discover, removal of initialize or Mcp-Session-Id, MCP Tasks extension changes, full JSON Schema 2020-12 tool schemas, OAuth issuer hardening, deprecated roots/sampling/logging, or cross-version client/server compatibility.

Package an in-progress task on this cluster so a Claude agent on another cluster (MMM Young, CX3, HX1, Isambard) can pick it up, or resume a task handed off to this cluster. Use when the user says hand off / migrate / continue this on <cluster>, or asks you to pick up an existing handoff.

Audits a project's agent configuration files, establishes a source-of-truth skills directory, normalizes naming, and generates bridge files to make the workspace consistent across Claude Code, Codex, Grok, and generic Agents.

Agent profile for lead framework, dependency, database, SDK, and architecture migrations with sequencing and rollback. Use when Codex needs a specialist agent perspective for planning, implementation, review, debugging, validation, or handoff in this domain.