菜单
Run read-only SQL against the {{ProductName}} PostgreSQL database to investigate or verify data during diagnosis. Use when asked to query the database directly or check actual data behind an issue. Preloaded by the rca-investigator agent.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Add a domain entity, aggregate, or value object to the .NET API — rich mutable class with private ctor + static factory (UUIDv7), invariants that throw, tenant_id, identity equality; records for value objects. Use when modeling new domain state under apps/api/{{ProjectName}}.Domain.
Add a Minimal API endpoint (a feature/use case) to the .NET API — feature folder, IEndpoint self-registration, contract validation, Kommand dispatch, Result→ProblemDetails. Use when adding or changing an HTTP endpoint under apps/api/{{ProjectName}}.Api.
Author a CQRS command or query in the {{ProductName}} backend using the Kommand library, the three-scope validation model, and the Result<T> failure pattern. Use whenever creating or modifying a command/query/handler/validator in apps/api/{{ProjectName}}.Application, or wiring its endpoint in {{ProjectName}}.Api.
Choose and wire AI features in the .NET backend — LLM calls, agentic tool-calling/multi-step workflows, RAG/vector search, structured output, streaming. Use when adding or changing anything that talks to a model or orchestrates agents (your agentic pipeline). Tailored to our LLM provider + MAF + pgvector stack.
Scan .NET/C# code for performance anti-patterns (async, memory/strings, collections/LINQ, regex, serialization, I/O) with tiered severity, reporting findings without editing. Use when auditing hot paths, reviewing allocation-heavy code, or analyzing the API for optimization opportunities.
Add or change EF Core (Npgsql/PostgreSQL) persistence in the .NET backend — entities, EF configurations, repositories, queries, migrations. Use when adding a table/entity, a query, a repository, or a migration under apps/api.
| name | query-postgres |
| description | Run read-only SQL against the {{ProductName}} PostgreSQL database to investigate or verify data during diagnosis. Use when asked to query the database directly or check actual data behind an issue. Preloaded by the rca-investigator agent. |
| argument-hint | <environment> <sql-query> |
| allowed-tools | Read, Bash |
Run a read-only SQL query against your PostgreSQL connection to get actual data during an
investigation. Wraps psql for read-only queries against Postgres.
⚠ Connection details are PLACEHOLDERS. No database is provisioned yet. Fill these in once the Postgres instance exists; until then, treat this skill as the agreed shape and ask Dan for connection specifics. Secrets (host/user/password) come from env / a vault — never hardcode or commit them.
| Environment | Host | Database | Auth |
|---|---|---|---|
| prod | <PG_HOST_PROD> | <DB_PROD> | <user via env/vault — read-only role> |
| test | <PG_HOST_TEST> | <DB_TEST> | <user via env/vault> |
| local | localhost | <db> | local dev creds |
Default environment if unspecified: prod (read-only).
# Prefer a connection URI from an env var; use a READ-ONLY role for investigation.
psql "$PG_URL_<ENV>" -v ON_ERROR_STOP=1 -P pager=off -c "<SQL_QUERY>"
# e.g. PG_URL_PROD="postgresql://<readonly_user>@<host>:5432/<db>?sslmode=require"
SELECT/EXPLAIN. Anything destructive (DROP/TRUNCATE/unqualified DELETE/UPDATE)
is blocked/prompted by the protect-commands hook and is never part of an investigation.timestamptz; display AT TIME ZONE 'UTC'.SELECT id, name FROM tenants ORDER BY name;.)$0, default prod).psql with the read-only connection.