agentleFS
PradnyeshpPradnyeshp/Claude-Skills/.claude/skills/migrate/SKILL.md

migrate

Skill2 starsChanged 4 months agoMITView on GitHub

Apply a sweeping, mechanical change consistently across the whole codebase — rename an API, swap a library or pattern, update a deprecated call — then verify nothing broke. Use when the user says "migrate all", "rename X everywhere", "replace every use of", "codemod", "update all callers", or "switch the project from X to Y".

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 6 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

  • MicrosoftSkill

    init

    Also in 8 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

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Map the blast radius first: Use grep/glob to find every occurrence — source, tests, config, docs, and string references.

    line 19
  2. Distinctive:

    Never do a blind global find-and-replace.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 51 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Scope of the change

!git status --short 2>/dev/null && echo "(commit or stash first — a migration touches many files)"

Instructions

Apply the migration described in $ARGUMENTS across the codebase. If the change isn't specific (the old → new mapping, or which symbol/pattern), ask before editing anything — a vague migration corrupts files at scale.

Method

  1. Map the blast radius first. Use grep/glob to find every occurrence — source, tests, config, docs, and string references. Report the count and the distinct usage shapes before changing anything. Watch for partial-word false positives (getUser inside getUserId).
  2. Confirm the transformation rule. State the exact old → new mapping and any cases that should be left alone (comments, generated files, vendored code, unrelated same-named symbols in another module).
  3. Apply consistently. Edit every real call site, plus imports/exports, type signatures, tests, and docs that reference it. Don't leave a half-migrated codebase. For large mechanical renames, prefer a scripted codemod (sed/ast-grep/language codemod tool) and show the command, but review its diff.
  4. Handle the long tail: re-exports, dynamic references (string keys, reflection, config files), and anything the search couldn't see. Call out spots you couldn't safely automate so the user can check them.
  5. Verify. Build/typecheck and run the test suite. Report what passed. If the project has a linter, run it to catch leftover unused imports.

Rules

  1. Insist on a clean working tree (or recent commit) before starting — migrations are large and hard to undo by hand. Stop and say so if it's dirty.
  2. Never do a blind global find-and-replace; verify each match class is a real target. Show the diff stat (git diff --stat) when done.
  3. Preserve behavior unless the migration explicitly changes it — flag any spot where the new API has different semantics (e.g. different default, throws instead of returns null).
  4. End with: files changed, occurrences migrated, verification result, and any sites left for manual review.

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.