make-migration
Skill4 starsChanged 2 months agoMITView on GitHub
Use when the database schema needs to change in a Symfony project using Doctrine.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cli-conventionsSkill
- componentsSkill
- configurationSkill
- discoverSkill
- make-ciSkill
- make-commandSkill
- make-controllerSkill
- make-crudSkill
- make-decoratorSkill
- make-entitySkill
- make-formSkill
- make-listenerSkill
- make-registration-formSkill
- make-reset-passwordSkill
- make-security-customSkill
- make-security-form-loginSkill
- make-testSkill
- make-twig-extensionSkill
- make-userSkill
- make-voterSkill
- make-webhookSkill
- servicesSkill
- templatesSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 22
Every schema change goes through a migration.
≈ “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.
Files
Schema changes
symfony console make:migration
symfony console doctrine:migrations:migratemake:migration takes no arguments and asks nothing — it diffs the mapping against the
database and writes the migration. Requires
doctrine/doctrine-migrations-bundle.
The rule
Every schema change goes through a migration. Not doctrine:schema:update, not hand-written
SQL against the database. The migration is the only artefact that can be reviewed, replayed
on another environment, and rolled back.
Reading what was generated
Open the file before running it. The diff is derived from the mapping, so a renamed property
appears as a dropped column plus a new one — which loses data. Rewrite those cases by hand
inside the generated up() method.
--formatted makes the SQL readable when you intend to edit it.
Test and production
doctrine:migrations:migrate runs the same way everywhere. For the test database, run it
with --env=test, and prefer it over recreating the schema so tests exercise the migrations
that production will run.
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
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.