ai-homebase

Use for Gitea, GitOps, registry, and every non-trivial implementation task that should be delegated to Codex instead of being coded inline.

Use for non-trivial implementation work. Delegate the coding or large-repo analysis to Codex CLI, then record usage before handing back results.

Browse in-cluster Gitea repos, issues, pull requests, commits, chart values, GitOps definitions, and sandbox image sources for read-only design context with the `__REVIEWER_GITEA_USERNAME__` Gitea user shared with auditor.

Review in-cluster Gitea repos and pull requests by reading files, inspecting diffs, checking comments, posting review feedback, and approving with the `__REVIEWER_GITEA_USERNAME__` Gitea user shared with architect; merge only with explicit instruction.

Use this to turn recent Qdrant memories and changed Nextcloud docs into clean Memgraph links, Qdrant graph-link annotations, and an updated grooming checkpoint.

Use when routing work to a standing specialist or reviewing a specialist return.

Use when operating Nextcloud as the shared coordination layer for desk state, calendars, todos, tables, sharing, or coordination status.

Use for heartbeat-driven monitoring, readiness checks, coordination-status checks, or budget sentinel alerts.

Use this to query or change Memgraph by adding canonical entities and relationships, linking Qdrant memories, and keeping graph structure consistent.

Use this to answer "what do we know about this?" with a Memgraph-first context map and link relevant Qdrant memories as graph evidence.

Use this to find and cite Nextcloud documents that support knowledge-graph curation, schema decisions, or Qdrant memory references.

Use when meaningful coordination work is complete and you need to decide what belongs in Qdrant or whether to refresh the shared coordination status marker.

Use when returning a plan or design deliverable to main, especially when the response needs a structured handoff and durable artifact references.

Use when defining a recurring worker workflow that needs a complete worker package, safety boundaries, and review guidance.

Use when creating or updating durable project planning artifacts in Nextcloud, including specs, decisions, and planning trackers.

Use when classifying a review request or returning a completed review packet to main.

Use when producing a review verdict that needs clear evidence, risk level, and a compact decision-ready result.

Use when reading or writing durable review artifacts in Nextcloud, including review packets, evidence, and findings.

Use when reading governing specs from Nextcloud or writing durable implementation notes after non-obvious implementation work.

Use when setting up, inspecting, or changing messaging channel bindings for the user or a dedicated specialist channel.

Use when deciding whether recurring work should become a worker, or when requesting, activating, updating, or retiring a worker.

Use before or during delegation when OpenClaw/Codex spend or budget pressure may affect staffing decisions.

Use when classifying a monitoring result, deciding whether to escalate, or preparing a Watchdog Alert.

Use when recording or updating durable monitoring state in Nextcloud, including incidents, baselines, and escalation trails.

Template skill for worker procedures. Use when defining a worker-local recurring workflow, output template, or escalation recipe that should not live in the always-loaded worker contract.