py2go
SolidMigrate Python projects to idiomatic Go end-to-end. Branches into 6 project-type playbooks (CLI, TUI, HTTP backend, data pipeline, async worker, library) with the right stack defaults (Gin, pgx, sqlc, slog, etc.) and pinned library versions. Default strategy: LLM module-by-module rewrite with golden-file parity tests; --strangler for live-traffic gradual cutover; --spec-first for OpenAPI/proto-driven regeneration. Use when porting a Python codebase to Go, when scaffolding a Go rewrite of a Python service, or when generating CLAUDE.md/MIGRATION.md for an AI-driven migration.
Install
Quality Score: 84/100
Skill Content
Details
- Author
- vanducng
- Repository
- vanducng/skills
- Created
- 4 months ago
- Last Updated
- today
- Language
- HTML
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
transform-my-repo
Feasibility analysis and migration strategy for architecture transformations: language ports (PHP to Python, Rust to Go), framework migrations (Vue or React SPA to Next.js), major version upgrades, monolith to microservices and back, database migrations, cloud/container/ serverless re-hosting, sync to event-driven, REST to GraphQL/gRPC, UI platform shifts, standalone to SaaS, and vanilla to framework. Produces an evidence-based GO/PARTIAL/NO-GO verdict with a worth-it test against the do-nothing baseline (dependency census verified in the target ecosystem, semantic gap analysis, per-module difficulty heatmap), then a migration roadmap with behavioral parity gates and rollback points. Allowed to recommend NOT migrating. Use when the user asks to migrate, port, rewrite, re-platform, upgrade a major version, split or merge services, switch databases or API paradigms, asks whether a migration is worth it, or mentions transform-my-repo or /transform-my-repo.
migration-playbook
Structured playbook for safely executing migrations: upgrading a major dependency version, framework migrations (e.g. React 17→18, Next.js 12→14, Vue 2→3), API deprecations, replacing one library with another, large-scale refactors touching many call sites, and database schema changes. Use this skill whenever the word "migrate", "upgrade", "deprecate", or "replace" applies to something with more than a handful of affected sites — even if it looks straightforward. Migrations that skip the inventory step consistently produce incidents from the sites nobody knew existed.
go-migrator
Writes zero-downtime, reversible, batched data migrations tested with testcontainers. Use for backfills, data transforms, column splits, and schema-level data moves.