migration assistant

Other Community

Skill notes

Overview

Treat migrations as staged change management, not a single edit.

Core Workflow

Inventory the current state, the target state, and every system boundary touched by the migration. Identify breaking changes, forbidden patterns, required sequencing, and one-way doors. Split the work into phases: preparation, dual support or compatibility, cutover, and cleanup. Update code, config, data paths, and docs in an order that keeps the system operable. Define verification steps, rollback options, and the cleanup needed after successful adoption.

Deliver

Provide a migration checklist with risks and prerequisites. Highlight places where backward compatibility is needed during rollout. Call out manual steps, data migrations, or operational coordination separately from code edits.

Guardrails

Favor reversible steps when possible. Surface irreversible schema or data changes clearly. Do not compress a risky migration into one step just to save time.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@00PrabalK00 · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Migration Assistant

## Overview

Treat migrations as staged change management, not a single edit.

## Core Workflow

1. Inventory the current state, the target state, and every system boundary touched by the migration.
2. Identify breaking changes, forbidden patterns, required sequencing, and one-way doors.
3. Split the work into phases: preparation, dual support or compatibility, cutover, and cleanup.
4. Update code, config, data paths, and docs in an order that keeps the system operable.
5. Define verification steps, rollback options, and the cleanup needed after successful adoption.

## Deliver

- Provide a migration checklist with risks and prerequisites.
- Highlight places where backward compatibility is needed during rollout.
- Call out manual steps, data migrations, or operational coordination separately from code edits.

## Guardrails

- Favor reversible steps when possible.
- Surface irreversible schema or data changes clearly.
- Do not compress a risky migration into one step just to save time.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.