القائمة
Guard checks code against project Recipe standards via MCP tool alembic_guard (auto-routes by code/files params). Use when the user wants to audit, lint, or verify code compliance.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | alembic-guard |
| description | Guard checks code against project Recipe standards via MCP tool alembic_guard (auto-routes by code/files params). Use when the user wants to audit, lint, or verify code compliance. |
Use this skill when: The user wants to check whether code meets project standards (规范 / Audit / Guard / Lint).
Guard is a scoped Recipe-adherence check. It is not repo lint, security audit, general code review, or a whole-diff fallback.
alembic_guardSingle code check (code param):
{ "code": "URLSession.shared.dataTask(with: url) { ... }", "language": "objc", "filePath": "Sources/Network/OldAPI.m" }
Multi-file audit (files[] param):
{ "files": [{ "path": "Sources/Network/APIClient.m" }, { "path": "Sources/Network/RequestManager.m" }], "scope": "project" }
Returns violations with { ruleId, severity, message, line, pattern }. Batch results auto-recorded to ViolationsStore.
Guard uses Recipe content as the standard — no separate config:
constraints.guards[].pattern → regex patterns for automated detectionalembic_guard with code → present violations + fix suggestionsalembic_structure(operation=files) → get file listalembic_guard with file paths → summarize by severityalembic_bootstrap → full project scan including Guard auditSubmit knowledge to Alembic. Covers single/batch MCP submission, V3 field requirements, quality validation, and lifecycle. Use when user says "submit knowledge / add to KB / create recipe" or agent needs to persist code patterns, rules, or facts.
Generate and browse project Wiki documentation through the Alembic resident daemon's wiki HTTP API (generate → status → files). Use when user says "generate wiki/docs", "write documentation", or agent needs structured project documentation produced from the knowledge base.
Provides this project's Recipe-based context to the agent. Recipes are the project's standard knowledge (code patterns + usage guides + structured relations). Use when answering about project standards, Guard, conventions, or when suggesting code. Supports in-context lookup, terminal search (alembic search), and on-demand semantic search via MCP tool alembic_search (mode=context).
Discover project structure (targets, files, dependency graph) and browse the knowledge graph (relations between Recipes). Use when the user asks about module structure, project targets, dependency relationships, or knowledge graph navigation.