agentleFS
Sign inStart free
swestfall21swestfall21/claude-skills/migration-refactor-safety/SKILL.md

migration-refactor-safety

Skill0 starsChanged 4 months agoMITView on GitHub

Enforce safe execution for migrations, refactors, and major system changes. Use when changing data flows, services, interfaces, or platform structure.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not complete a migration or refactor until the change is safe to roll out, safe to roll back, and observable in production.

    line 8
  2. Distinctive:

    Prefer staged rollout over big-bang changes.

    line 19
  3. Distinctive:

    Add or preserve observability for the transition.

    line 21
  4. Distinctive:

    Keep the rollback path simple and rehearsed.

    line 22
  5. Distinctive:

    Do not treat a migration as done just because the code is deployed.

    line 26
  6. Distinctive:

    Do not remove the old path without an explicit rollback plan.

    line 27
  7. Distinctive:

    Do not rely on intuition when the change affects data or traffic patterns.

    line 28
  8. Distinctive:

    Do not leave the team without visibility into the rollout.

    line 29
  9. Distinctive:

    Use this skill to make migrations and refactors disciplined rather than risky.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Migration and refactor safety

Do not complete a migration or refactor until the change is safe to roll out, safe to roll back, and observable in production.

Before starting

  • Understand the old and new paths clearly.
  • Identify the compatibility requirements and the rollback strategy.
  • Define what success looks like during the transition.
  • Decide what will be monitored during rollout.

During execution

  • Prefer staged rollout over big-bang changes.
  • Preserve compatibility where it matters.
  • Add or preserve observability for the transition.
  • Keep the rollback path simple and rehearsed.

Non-negotiables

  • Do not treat a migration as done just because the code is deployed.
  • Do not remove the old path without an explicit rollback plan.
  • Do not rely on intuition when the change affects data or traffic patterns.
  • Do not leave the team without visibility into the rollout.

Use this skill to make migrations and refactors disciplined rather than risky.

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.

Check your setup, free