| name | alembic-structure |
| description | Discover Alembic project structure, targets, files, metadata, dependency relationships, and Recipe graph context. |
Alembic Structure
Use this skill when the user asks about module structure, targets, dependencies, call relationships, or how Recipes relate to each other.
Project Structure Tools
| 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:
- Call
alembic_structure(operation: "targets").
- Select a target based on the user request.
- Call
alembic_structure(operation: "files", targetName: "...").
- Call
alembic_structure(operation: "metadata", targetName: "...") when dependency context matters.
Knowledge Graph Tools
| 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.
Path Notes
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.
Related Skills
alembic-recipes: Recipe content as project standards.alembic-create: Submit candidates after structure analysis.alembic-guard: Check affected files against standards.
