القائمة
Create an Alembic database migration following project conventions (idempotent, single-head). Use when adding columns, tables, or modifying the database schema.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Interact with the MCP Context Forge Gateway REST API — register gateways, create servers, invoke tools, manage teams, configure OAuth, and perform admin operations. Use when asked to register an MCP server, call a gateway endpoint, create a team, invoke a tool, set up a virtual server, test API connectivity, check gateway health, manage tokens, configure header passthrough, or perform any gateway API operation. Also trigger when the user mentions curl examples, API payloads, or gateway configuration.
Author gateway plugins for MCP Context Forge — native Python plugins or external MCP plugins. Use when asked to create a new plugin, add a hook, build a filter/guard/validator, write a content transformer, implement rate limiting or PII detection, or add any pre/post processing to the gateway pipeline. Also use when the user mentions plugin configuration, hook types, or policy enforcement.
Scaffold and create new MCP servers for MCP Context Forge. Use when asked to create a new MCP server, add a tool server, scaffold a Python or Go MCP server, build an MCP integration, or register an external service with the gateway. Also use when the user mentions adding new tools, creating a server for a specific API, or building a FastMCP service.
Run the full pre-commit quality gate — format, lint, static analysis. Use before committing changes.
| name | alembic-migration |
| description | Create an Alembic database migration following project conventions (idempotent, single-head). Use when adding columns, tables, or modifying the database schema. |
| disable-model-invocation | true |
Create an Alembic migration for: $ARGUMENTS
down_revision MUST point to the actual current head (verified below)down_revision from older migrationsVerify current head (this is the value for down_revision):
cd mcpgateway && alembic heads
Generate the migration:
cd mcpgateway && alembic revision --autogenerate -m "$ARGUMENTS"
Edit the generated file to make it idempotent:
def upgrade() -> None:
inspector = sa.inspect(op.get_bind())
if "my_table" not in inspector.get_table_names():
return
columns = [col["name"] for col in inspector.get_columns("my_table")]
if "new_column" in columns:
return
op.add_column("my_table", sa.Column("new_column", sa.String(), nullable=True))
Verify single head after creation:
cd mcpgateway && alembic heads
Must show exactly ONE head. If multiple, fix down_revision.
Run tests to confirm:
make test