Menu
Discover Alembic project structure, targets, files, metadata, dependency relationships, and Recipe graph context.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | alembic-structure |
| description | Discover Alembic project structure, targets, files, metadata, dependency relationships, and Recipe graph context. |
Use this skill when the user asks about module structure, targets, dependencies, call relationships, or how Recipes relate to each other.
| Tool | Use |
|---|---|
alembic_structure(operation: "targets") | List modules, targets, language stats, and inferred roles |
alembic_structure(operation: "files") | List files for a target |
alembic_structure(operation: "metadata") | Read target metadata, dependencies, package info, and graph edges |
alembic_call_context | Query callers, callees, or impact radius for a function or method |
Recommended flow:
alembic_structure(operation: "targets").alembic_structure(operation: "files", targetName: "...").alembic_structure(operation: "metadata", targetName: "...") when dependency context matters.| Tool | Use |
|---|---|
alembic_graph(operation: "query") | Get relations for one Recipe node |
alembic_graph(operation: "impact") | Analyze downstream impact of changing a Recipe |
alembic_graph(operation: "path") | Find a relationship path between two Recipes |
alembic_graph(operation: "stats") | Summarize graph health |
Use graph context when Recipe changes might affect other standards.
Some generated dependency maps may live under the Alembic knowledge root. In standard mode that root is usually Alembic/ in the project; in Ghost mode it is external to the project. Prefer MCP tools over hardcoded paths.
alembic-recipes: Recipe content as project standards.alembic-create: Submit candidates after structure analysis.alembic-guard: Check affected files against standards.Submit new Alembic knowledge candidates from Codex. Covers `alembic_submit_knowledge`, required V3 fields, batch rules, and review boundaries.
Generate Alembic Wiki documentation through `alembic_wiki` using plan, article writing, and finalize.
Check code against Alembic Recipe standards with `alembic_guard`. Trigger for audits, lint-like review, diff checks, compliance checks, and "does this follow our conventions?" questions.
Use Alembic Recipes as the project's curated source of truth for conventions, code patterns, facts, and Guard standards. Trigger when answering questions about project standards or when implementation should follow local knowledge.
Use Alembic from Codex. Start here for status, initialization, project priming, Guard checks, bootstrap/rescan jobs, Dashboard handoff, and permission boundaries.
Use when: generating source-derived chain maps and long-chain execution plans, validating long-chain workflow behavior node by node, reviewing benchmark coverage, applying optional domain overlays, or repairing Alembic cold-start/rescan/bootstrap/delivery/skill-generation flows with explicit evidence and write boundaries.