agentleFS
Sign inStart free
rpraharajrpraharaj/ai-sdlc/skills/data-change/SKILL.md

data-change

Skill0 starsChanged 16 days agoMITView on GitHub

Plan and apply a schema, API, or data migration using expand-then-contract. Use when adding or changing columns, indexes, events, protobuf or OpenAPI shapes, or backfills. Do not expand and contract in the same change.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Write the plan from references/data-change-plan.md.

    line 41

≈ “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

Data change

Change stored or published shape without breaking current readers. For a multi-slice plan, plan-data-migration orders the slices; this skill applies one step.

Is this the right skill?

SignalDo this instead
Ordered expand/dual-write/contract planplan-data-migration first
Examples onlywrite-api-examples
No migrator in the repo and they need onestop — do not invent a framework

Required inputs

  • Current and desired shape (or the current plan-data-migration slice)
  • AGENTS.md

Human decisions (do not invent)

  • Running a destructive migration against shared/prod
  • Combining expand and contract (forbidden)

Procedure

  1. Detect how this repo migrates from existing folders. Do not add a new migrator.
  2. Classify: expand | backfill | contract. Default to expand. Rename/drop is three later changes, not one.
  3. Write the plan from references/data-change-plan.md. Destructive contract with expand is a fail. Unbounded backfill without batches is a fail.
  4. Apply only the current step. Match existing migration naming. Load engineering-bar. Prove with this repo’s tests plus the verification check in the plan.

Output

  • Path: reply plan + migration files
  • Template: references/data-change-plan.md

Quality bar

  • Step is one of expand / backfill / contract
  • Expand and contract are not in the same change
  • Rollback sentence exists
  • Commands run are recorded

Done

  1. Plan + step executed
  2. Files added
  3. What a later change must do

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