agentleFS
GlamgarOnDiscordGlamgarOnDiscord/claude-saas-blueprint/.claude/skills/migrate/SKILL.md

migrate

Skill2 starsChanged 6 months agoMITView on GitHub

Gère les migrations : DB, dépendances majeures, changement de lib, ou mise à jour de framework.

65 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use incident, sdd and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 4 projects that use this

  • liatrio-labsSkill

    sdd

    Execute the Liatrio Spec-Driven Development (SDD) workflow when explicitly invoked by the user. NOTE: this skill is NOT intended to be dynamically loaded or automatically triggered; it should only ever be explicitly called by the user.

    Also in 4 projects that use this

  • BerryKuipersSkill

    scaffold

    Detect project stack, apply architecture patterns, wire quality gates, and scaffold features. Use when bootstrapping a project, adding a vertical slice, wiring CI/CD, adding Docker compose, or setting up quality gates.

    Also in 4 projects that use this

  • agenticnotetakingSkill

    upgrade

    Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".

    Also in 3 projects that use this

  • genomewalkerSkill

    checkpoint

    Save a checkpoint of task status, decisions, active files, and next steps

    Also in 5 projects that use this

  • JohnJBorenSkill

    ci-cd

    CI/CD pipeline design, GitHub Actions, testing automation, and deployment strategies

    Also in 3 projects that use this

The file

Files
SKILL.md

Modes

/migrate db [description] — Migration de base de données

Avant de commencer :

# 1. Backup local obligatoire
python scripts/supabase_migrate.py --diff   # voir l'état actuel
git stash || git commit -m "chore: pre-migration checkpoint"

Création et application :

python scripts/supabase_migrate.py --new [description]   # crée le fichier migration
# Éditer le fichier créé dans supabase/migrations/
python scripts/supabase_migrate.py --env local           # appliquer en dev d'abord

Checklist post-migration :

  1. Toute nouvelle table → vérifier ENABLE ROW LEVEL SECURITY + politiques RLS
  2. python scripts/supabase_rls_check.py — doit retourner 0 tables sans RLS
  3. Mettre à jour core/entities/ et core/ports/ si les types changent
  4. Régénérer les types TypeScript : pnpm supabase gen types
  5. Tests blast radius : pnpm test -- --grep [feature]

Rollback :

python scripts/supabase_migrate.py --new rollback-[description]
# Écrire le SQL inverse dans le nouveau fichier
python scripts/supabase_migrate.py --env local

Règle stricte : jamais modifier une migration déjà appliquée — toujours créer une nouvelle.


/migrate dep [package] [version] — Mise à jour de dépendance majeure

  1. Lire changelog/release notes officiel (WebSearch) — breaking changes uniquement
  2. Grep les imports du package dans tout le projet
  3. Appliquer les changements fichier par fichier
  4. tsc --noEmit + tests après chaque fichier
  5. Si la migration est complexe → /deep-update (veille changelog approfondie)
  6. Documenter dans decisions.md si changement architecturel

/migrate lib [ancienne] → [nouvelle] — Changement de librairie

  1. Rechercher le guide de migration officiel (WebSearch)
  2. Mapper les API ancienne → nouvelle (tableau de correspondance)
  3. EnterPlanMode — plan fichier par fichier avant de toucher quoi que ce soit
  4. Remplacer fichier par fichier, tests verts entre chaque
  5. pnpm remove [ancienne] seulement quand 0 import restant (Grep)
  6. Tests complets + tsc --noEmit

/migrate framework [version] — Mise à jour de framework

  1. Lire le guide de migration officiel (WebSearch) — ne pas supposer les breaking changes
  2. Créer une branch dédiée : git checkout -b migrate/[framework]-[version]
  3. Suivre le guide étape par étape — une étape = un commit
  4. tsc --noEmit + build + tests après chaque étape
  5. Si Next.js : vérifier App Router codemods disponibles (npx @next/codemod)
  6. Créer un ADR documentant les décisions de migration

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.