bezael

Plan before executing. Use when task touches 3+ files, requires new folder structure, involves DB or API changes, or has step dependencies. Waits for approval before writing code.

Structured debugging workflow — diagnose before proposing fixes. Use when user says /debug, reports a bug, an error, or unexpected behavior. Forms hypotheses before touching code.

Compact the current conversation into a handoff document for a fresh agent to continue the work.

Manage persistent memory across sessions. Subcommands: save [topic] captures session learnings, recall [question] retrieves relevant context before acting, clean removes stale entries.

Review code with real engineering criteria — logic bugs, security vulnerabilities, and technical debt. Use when user says /review @file or /review to review current PR changes.

Audit AI-generated apps for security, performance, and maintainability issues. Use when user says /vibe-audit or "I generated this with AI and want to know how bad it is".

Generate a semantic commit message by reading the real staged diff. Use when the user says /commit, "make a commit", or "commit the changes". Never invents — reads the actual diff.

Create a Pull Request with description, test plan, and checklist. Use when the user says /pr, "create PR", or "open pull request". Reads real branch commits and diff.

Query a production PostgreSQL database safely and read-only from Hermes. Enforces a dedicated read-only role, rejects any write/DDL/stacked-statement payload before it reaches the database, caps row counts and execution time, and never lets a connection string or password enter the agent's context or logs. Use whenever Hermes needs to answer a question against a live production Postgres database (debugging, support triage, reporting, ad-hoc analytics) without risking a write, a runaway scan that saturates the connection pool, or a leaked credential.

Connect a new MCP (Model Context Protocol) server to a running Hermes Agent instance safely — add the right entry under `mcp_servers:` in `~/.hermes/config.yaml`, scope its environment variables correctly, and verify both that the server's tools actually load and that Hermes's credential-filtering is doing what the docs claim. Use when the user has an MCP server (official, community, or self-built) and needs it working inside Hermes, is migrating an `mcp.json`-style config from Claude Desktop/Cursor into Hermes, or is debugging why an MCP server's tools aren't showing up or a tool call is failing with what looks like an auth error.

Reviews a new or modified FastAPI endpoint against production practices in four areas — Pydantic request/response validation, HTTP error handling, dependency injection, and OpenAPI documentation. Use when a user adds or changes a route (`@app.get`, `@router.post`, etc.) and asks for a review, a second opinion, or "is this endpoint ready to merge", or before approving a PR that touches a FastAPI `routers/`, `api/`, or `endpoints/` folder. Not for Flask/Django views — trigger only on `fastapi`/`APIRouter`/`Depends` imports.

Delega una tarea de refactor puntual entre Hermes Agent y Cursor usando un protocolo de archivos compartidos (task/result), sin depender de MCP ni ACP. Sirve como fallback ligero cuando no tienes un bridge en tiempo real instalado, o como primer paso antes de instalar uno.

Delega desde Hermes una tarea de código puntual y acotada a Codex CLI (codex exec) sin cambiar el runtime completo de Hermes, y trae el resultado de vuelta para verificarlo e integrarlo a la memoria de Hermes.

Deploy Hermes Agent to Azure — either Azure Container Apps (ACA) or an Azure Linux VM — with persistent state volumes, secrets pulled from Key Vault instead of baked into the image, and the agent's isolated sandbox configured correctly for whichever target you pick. Use when a user wants to run Hermes on Azure specifically (not a generic VPS, not AWS/GCP) and asks about hosting, persistence, secrets, or sandboxing on ACA or an Azure VM.

Revisa la configuración de una instancia EC2 o Lightsail antes de desplegar Hermes Agent con el sandbox Docker — tipo de instancia adecuado para correr el daemon Docker más contenedores de sandbox, reglas de grupos de seguridad (security groups) y costo mensual estimado usando la AWS Pricing API real. Úsala cuando el usuario vaya a desplegar Hermes en AWS y pregunte cosas como "qué instancia EC2 necesito para Hermes", "esta instancia le va a alcanzar al sandbox Docker", "revisa mis security groups antes de desplegar" o "cuánto me va a costar esto al mes".

Propuesta de arquitectura para exponer el estado y las acciones de Hermes Agent (mensajes en streaming, tool calls, plan/todos) a un frontend custom vía AG-UI (Agent-User Interaction Protocol), el protocolo abierto de CopilotKit para conectar agentes a interfaces React/Angular. Úsala cuando quieras construir una UI propia (chat, dashboard, panel de control) sobre una instancia de Hermes en vez de un cliente de mensajería, cuando necesites que esa UI pueda declarar herramientas invocables por el agente y recibir el resultado de vuelta, o cuando quieras entender qué eventos internos de Hermes corresponden a qué eventos de AG-UI antes de escribir el adapter tú mismo.

Create a Spec-Driven Development specification (spec.md + plan.md + tasks.md with TDD) BEFORE writing any code, following the Dominicode SDD methodology by Bezael Pérez. Use this skill whenever the user wants to scaffold, plan, design, or specify a new feature, product, MVP, module, or project — including phrases like "create a spec", "spec this out", "write the spec for", "plan this feature", "I want to build X", "help me design X", "structure this project", "scaffold a new feature", "let's start a new project", or any request that would normally lead to coding a non-trivial feature. ALWAYS trigger this skill before generating implementation code for a new feature or product, even if the user did not explicitly ask for a spec — jumping straight to code without a spec is exactly what this methodology prevents. Produces a 6-section spec (Visión, Usuarios, Funcionalidades, Flujos, Arquitectura, NFRs) plus a technical plan and a TDD-ordered task list.

Review code with real engineering criteria — logic bugs, security vulnerabilities, and technical debt. Use when user says /review @file or /review to review current PR changes.

Create a Spec-Driven Development specification (spec.md + plan.md + tasks.md with TDD) BEFORE writing any code, following the Dominicode SDD adaptation by Bezael Pérez. Use this skill whenever the user wants to scaffold, plan, design, or specify a new feature, product, MVP, module, or project — including phrases like "create a spec", "spec this out", "write the spec for", "plan this feature", "I want to build X", "help me design X", "structure this project", "scaffold a new feature", "let's start a new project", or any request that would normally lead to coding a non-trivial feature. ALWAYS trigger this skill before generating implementation code for a new feature or product, even if the user did not explicitly ask for a spec — jumping straight to code without a spec is exactly what this methodology prevents. Produces a 6-section spec (Vision, Users, Features, Flows, Architecture, NFRs) plus a technical plan and a TDD-ordered task list.