Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
migrations - Skill - OpenSmartRoute
Skillv1.0.0
migrations
Migrations. Alembic 1. Migrations must be static and revertable. If your migrations depend on dynamically generated data, then make sure the only thing that is dynamic is the data itself, not its stru
Instruction file imported from twbrandon7/rag-mcp-server (.github/instructions/migrations.instructions.md). Copyright stays with the author.
Migrations. Alembic
Migrations must be static and revertable.
If your migrations depend on dynamically generated data, then
make sure the only thing that is dynamic is the data itself, not its structure.
Generate migrations with descriptive names & slugs. Slug is required and should explain the changes.
Set human-readable file template for new migrations. We use *date*_*slug*.py pattern, e.g. 2022-08-24_post_content_idx.py
{
"ocm": "1",
"id": "twbrandon7-rag-mcp-server-migrations-instructions",
"kind": "skill",
"name": "migrations",
"description": "Migrations. Alembic 1. Migrations must be static and revertable. If your migrations depend on dynamically generated data, then make sure the only thing that is dynamic is the data itself, not its structure. 2. Generate migrations with descriptive names & slugs. Slug is required and should explain the changes. 3. Set human-readable file template for new migrations. We use `*date*_*slug*.py` pattern, e.g. `2022-08-24_post_content_idx.py` ``` # alembic.ini file_template = %%(year)d-%%(month).2d-%%(day).2d_%%(slug)s ```",
"publisher": "twbrandon7",
"version": "1.0.0",
"capabilities": {
"domains": [
"math"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Migrations. Alembic 1. Migrations must be static and revertable. If your migrations depend on dynamically generated data, then make sure the only thing that is dynamic is the data itself, not its structure. 2. Generate migrations with descriptive names & slugs. Slug is required and should explain the changes. 3. Set human-readable file template for new migrations. We use `*date*_*slug*.py` pattern, e.g. `2022-08-24_post_content_idx.py` ``` # alembic.ini file_template = %%(year)d-%%(month).2d-%%(day).2d_%%(slug)s ```"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/twbrandon7/rag-mcp-server",
"path": ".github/instructions/migrations.instructions.md",
"ref": "843450e048f62ce93a17ac7718dc4f759f30216d",
"url": "https://github.com/twbrandon7/rag-mcp-server/blob/843450e048f62ce93a17ac7718dc4f759f30216d/.github/instructions/migrations.instructions.md",
"key": "twbrandon7/rag-mcp-server/.github/instructions/migrations.instructions.md"
},
"applies_to": "backend/alembic/versions/**"
},
"instructions": "## Migrations. Alembic\n1. Migrations must be static and revertable.\nIf your migrations depend on dynamically generated data, then \nmake sure the only thing that is dynamic is the data itself, not its structure.\n2. Generate migrations with descriptive names & slugs. Slug is required and should explain the changes.\n3. Set human-readable file template for new migrations. We use `*date*_*slug*.py` pattern, e.g. `2022-08-24_post_content_idx.py`\n```\n# alembic.ini\nfile_template = %%(year)d-%%(month).2d-%%(day).2d_%%(slug)s\n```",
"cost": {
"context_tokens": 131
}
}
Fetch it by URL: GET /api/v1/registry/twbrandon7-rag-mcp-server-migrations-instructions/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
