agentleFS
Sign inStart free
gerard-labsgerard-labs/superpowers-api-platform/skills/doctrine-migrations/SKILL.md

doctrine-migrations

Skill2 starsChanged 6 months agoMITView on GitHub

Manage Doctrine schema evolution — `doctrine:migrations:diff` to generate from entity diff, `doctrine:migrations:migrate` to apply, custom up()/down() for data migrations, zero-downtime expand/contract patterns (add nullable column → backfill → set NOT NULL → drop), separate console commands for heavy data migrations, naming conventions per Symfony. Trigger when adding a column, renaming, splitting a table, or planning a UUID v7 retrofit.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Verify lifecycle behavior with targeted tests.

    line 23
  2. Distinctive:

    Keep owning/inverse sides coherent.

    line 26
  3. Distinctive:

    Avoid destructive migration jumps in one release.

    line 27
  4. Distinctive:

    Use this file for execution posture and risk controls.

    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

Doctrine Migrations (Symfony)

Use when

  • Designing entity relations or schema evolution.
  • Improving Doctrine correctness/performance.

Default workflow

  1. Model ownership/cardinality and transactional boundaries.
  2. Apply mapping/schema changes with migration safety.
  3. Tune fetch/query behavior for hot paths.
  4. Verify lifecycle behavior with targeted tests.

Guardrails

  • Keep owning/inverse sides coherent.
  • Avoid destructive migration jumps in one release.
  • Eliminate accidental N+1 and over-fetching.

Progressive disclosure

  • Use this file for execution posture and risk controls.
  • Open references when deep implementation details are needed.

Output contract

  • Entity/migration changes.
  • Integrity and performance decisions.
  • Validation outcomes and rollback notes.

References

  • reference.md
  • docs/complexity-tiers.md

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