alembic
Manage Alembic Database Migrations
Database schema changes are risky when teams lack repeatable migration patterns. This skill gives Claude, Codex, and Claude Code practical Alembic guidance for SQLAlchemy projects.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "alembic" from https://skillstore.io/skills/bossjones-alembic.md and its manifest at https://skillstore.io/api/skills/bossjones-alembic/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "alembic". I added an email column to the users model. What should I do next?
Expected outcome:
The skill would outline an autogenerate command, review steps for the generated migration, an upgrade command, and checks for downgrade behavior.
Using "alembic". My SQLite migration cannot alter a table directly.
Expected outcome:
The skill would recommend Alembic batch mode and explain when render_as_batch should be enabled for SQLite migrations.
Using "alembic". I need to check if the database is at the latest revision.
Expected outcome:
The skill would describe comparing current database heads with Alembic script heads and when to use that check in deployment workflows.
Security Audit
SafeThe static findings are false positives caused by Markdown code fences containing Alembic commands, Python migration snippets, and normal database configuration examples. No prompt injection, data exfiltration intent, or executable marketplace behavior was found in the reviewed skill content.
Risk Factors
⚙️ External commands (33)
🔑 Env variables (5)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/bossjones-alembic/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/bossjones-alembic?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/bossjones-alembic?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bossjones-alembic/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/bossjones-alembic.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
bossjones. (2026). alembic security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/bossjones-alembic/audits/10BibTeX citation
@techreport{bossjones-bossjones-alembic-2026,
author = {bossjones},
title = {alembic security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/bossjones-alembic/audits/10},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "alembic security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
- name: "bossjones"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/bossjones-alembic/audits/10"
identifiers:
- type: other
value: "skillstore:bossjones-alembic:audit:10"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Create model-driven migrations
Generate Alembic revisions from SQLAlchemy model changes and review the resulting schema operations.
Prepare safe database releases
Plan upgrade, downgrade, and status commands before applying schema changes across environments.
Maintain migration configuration
Configure async engines, metadata discovery, object filters, and SQLite batch mode for reliable autogeneration.
Try These Prompts
Help me create an Alembic migration for my SQLAlchemy model changes. Show the commands to generate, inspect, and apply it safely.
Review this Alembic migration plan for safety. Identify risky operations, missing downgrade steps, and changes that need manual edits.
Guide me through configuring Alembic env.py for async SQLAlchemy. Include metadata setup, async engine configuration, and autogenerate options.
Help me design a safe Alembic migration strategy for a production schema change with data backfill, rollback planning, and deployment checks.
Best Practices
- Review autogenerated migrations before applying them to shared or production databases.
- Test both upgrade and downgrade paths in a disposable database before release.
- Keep schema migrations and data migrations small enough to review and roll back.
Avoid
- Do not downgrade or reset a production database without backups and an approved rollback plan.
- Do not commit database credentials in alembic.ini or migration files.
- Do not trust autogenerate output without checking constraints, indexes, data changes, and defaults.