メニュー
Workflow for ClickHouse schema changes — adding columns, tables, or modifying the OTEL analytics schema. Use when making changes to ClickHouse tables in the otel database.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Step-by-step workflow for adding a new sub-agent or tool to the Pulse AI system. Use when creating a new ADK agent, tool, or extending the AI pipeline in pulse_ai/.
Cross-cutting workflow for adding a new alert metric spanning DB, backend, cron, frontend, and AI agent. Only invoke explicitly when adding a new metric type.
Step-by-step workflow for adding a new REST API endpoint to pulse-server. Use when creating a new backend endpoint, route, resource, or API in backend/server/.
Step-by-step workflow for adding a new reusable component to pulse-ui. Use when creating a shared component in pulse-ui/src/components/ (not a full screen/page).
Step-by-step workflow for adding a new screen/page to pulse-ui. Use when creating a new UI screen, page, dashboard view, or route in pulse-ui/.
Workflow for building and deploying Pulse services locally via Docker. Use when building Docker images, starting/stopping services, or managing the local development environment.
| name | clickhouse-migration |
| description | Workflow for ClickHouse schema changes — adding columns, tables, or modifying the OTEL analytics schema. Use when making changes to ClickHouse tables in the otel database. |
| disable-model-invocation | true |
- [ ] Step 1: Update the schema file
- [ ] Step 2: Create migration script
- [ ] Step 3: Update init script
- [ ] Step 4: Update affected queries in backend
- [ ] Step 5: Update AI agent schema registry
- [ ] Step 6: Apply and verify
Edit backend/db/prod/clickhouse/*.sql to reflect the final desired state. This file is used for fresh installs.
When you add or rename tables, materialized columns, or row-policy targets, update .cursor/ docs to match (at minimum
agents/data-analyst.md, rules/clickhouse-sql.mdc, rules/pulse-architecture.mdc, commands/query-clickhouse.md) or
run /audit-cursor-config to catch drift.
Create deploy/db/migration-clickhouse-<description>.sql:
-- Adding a new column
ALTER TABLE otel.otel_traces ADD COLUMN IF NOT EXISTS new_column String DEFAULT '';
-- Adding a new table
CREATE TABLE IF NOT EXISTS otel.my_new_table (
Timestamp DateTime64(9) CODEC(Delta, ZSTD(1)),
TraceId String CODEC(ZSTD(1)),
-- ... columns ...
) ENGINE = MergeTree()
PARTITION BY toDate(Timestamp)
ORDER BY (TraceId, Timestamp)
SETTINGS index_granularity = 8192;
If adding a new table, update deploy/scripts/init-clickhouse.sh to include it.
Search for affected queries in:
backend/server/src/main/java/.../service/ — ClickhouseMetricService and relatedbackend/server/src/main/java/.../dao/ — any DAO querying the changed tableNote: The AI agent currently has a flat structure (pulse_ai/agent.py) with no registries. If the change affects
queryable tables/columns, update the root agent's instruction in pulse_ai/agent.py to reflect the new schema, or
update registry files at the pulse_ai/ root when they are added.
# Apply to running ClickHouse
docker exec -i pulse-clickhouse clickhouse-client < deploy/db/migration-clickhouse-<desc>.sql
# Verify
docker exec pulse-clickhouse clickhouse-client --query "DESCRIBE otel.otel_traces"