القائمة
Use Alembic from Codex. Start here for status, initialization, project priming, Guard checks, bootstrap/rescan jobs, Dashboard handoff, and permission boundaries.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | alembic |
| description | Use Alembic from Codex. Start here for status, initialization, project priming, Guard checks, bootstrap/rescan jobs, Dashboard handoff, and permission boundaries. |
Use this skill when the user asks Codex to work with project conventions, local knowledge, Guard checks, bootstrap/rescan workflows, or Alembic itself.
Call alembic_codex_status before assuming Alembic is initialized. This status check is local and must not start the daemon.
If status reports runtime or environment problems, call alembic_codex_diagnostics and surface the suggested fix. Diagnostics also runs without starting the daemon.
If the workspace is not initialized and the user wants Alembic knowledge for this project, call alembic_codex_init. The default profile is Ghost mode, so Alembic data is stored in the external workspace data root and Codex does not write IDE configuration into the project.
For non-trivial coding tasks:
alembic_task with operation: "prime" and include the user's task.alembic_search, alembic_knowledge, or alembic_structure when more project context is needed.alembic_guard after meaningful edits, especially before summarizing completion.alembic_submit_knowledge; do not write Recipe files directly.Use alembic_codex_bootstrap for internal bootstrap jobs and alembic_codex_rescan for internal rescan jobs. These tools start or connect to the daemon, enqueue work, and return a recoverable job id.
Use alembic_codex_job to check job status later. Job lookup is local and should not start the daemon.
Use alembic_codex_dashboard when the user needs review, candidates, or progress visualization. Return the Dashboard URL instead of opening a browser yourself.
Default Codex mode is agent tier. It may search knowledge, prime tasks, run Guard, start daemon jobs, and submit candidates.
Do not publish, deprecate, delete, or directly edit Recipes from the default tier. Admin tools only appear when both ALEMBIC_MCP_TIER=admin and ALEMBIC_CODEX_ENABLE_ADMIN=1 are set.
Do not edit .cursor, .vscode/mcp.json, AGENTS.md, or project Alembic data unless the user explicitly asks for a standard, project-written setup.
Plugin uninstall never removes user data. Use alembic_codex_cleanup for explicit cleanup. The default call is a dry run; confirm=true only removes daemon runtime state, logs, locks, and job files.
alembic-recipes: Recipe lookup and application.alembic-create: Candidate submission rules.alembic-guard: Compliance checks.alembic-structure: Project targets, files, metadata, graph, and call context.alembic-devdocs: Wiki planning, article writing, and finalize.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.
Discover Alembic project structure, targets, files, metadata, dependency relationships, and Recipe graph context.
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.