菜单
Test Chronos Docker stack data flow across container states. Run to verify Core, Query Service, and MCP connectivity, health endpoints, event creation/query, and end-to-end data flow. Triggers on "test data flow", "check data flow", "chronos health", "test chronos stack", "verify containers".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Build and use a durable "voice file" — your thinking patterns, communication style, domain expertise, contrarian takes, and strategic frameworks — backed by AllSource Prime instead of a static markdown blob. Runs a structured interview that records each answer as an embedded `voice` node, then BEFORE writing anything user-facing (LinkedIn post, ADR, code review, proposal, email) recalls the relevant voice slice and writes in that voice. The viral "voice file" idea, but live, queryable, portable across MCP agents, and team-shareable. Use when the user says "build my voice file", "set up my voice", "/voice", "write this in my voice", "make this sound like me", "capture how I think/write", or asks for user-facing writing once a voice file exists. Triggers PROACTIVELY: recall the voice slice before drafting any first-person user-facing text. voice = identity layer; mammoth = the memory engine underneath.
Durable cross-session memory via AllSource Prime. Recall what was learned in past sessions — decisions, task history, code context — and record salient new facts as you work, so the user never re-explains the project twice. Use at the START of a session to orient (recall prior context before answering non-trivial questions), and DURING work to record decisions, gotchas, and outcomes worth remembering. Triggers on "what did we decide about X", "remember this", "why did we do Y", "recall", "have we discussed", "load context", or any question that depends on prior-session knowledge. Also use PROACTIVELY: recall before answering architecture/decision/history questions; record after a non-obvious decision is made. mammoth = the memory layer; caveman makes few token, mammoth never forget token.
Release a new version of the AllSource Chronos monorepo. Bumps versions across all services (Rust, Go, Elixir), runs full CI to green, creates a single squashed commit with an annotated immutable tag. Use when the user says "release", "new version", "bump version", "tag a release", "cut a release", or "make a release". Argument is the version number (e.g., "0.10.4") or "patch"/"minor"/"major" for auto-increment.
Check the status of all AllSource services on Fly.io. Shows running state, health checks, deployed versions, recent crashes/errors, and staleness vs latest git tag. Triggers on "fly status", "check fly", "deployment status", "are services running", "check production", "fly report", "fly health".
Create an AllSource account and API key for chronis sync. Registers on the hosted Core, creates an API key, and configures .chronis/config.toml in the current project. Triggers on "onboard allsource", "setup sync", "get api key", "connect to allsource", "cn sync setup".
Test Chronos MCP server with embedded Core backend (CORE_MODE=embedded). Verifies Rustler NIF prerequisites, event ingest/query through embedded backend, schema operations, stats/health, and data persistence across restarts. Triggers on "test embedded data flow", "test embedded", "embedded health", "test embedded backend", "verify embedded", "test nif".
| name | chronos-data-flow |
| description | Test Chronos Docker stack data flow across container states. Run to verify Core, Query Service, and MCP connectivity, health endpoints, event creation/query, and end-to-end data flow. Triggers on "test data flow", "check data flow", "chronos health", "test chronos stack", "verify containers". |
| category | testing |
| color | green |
| displayName | Chronos Data Flow Test |
Tests the full data flow through the Chronos Docker stack across multiple container states.
Run the data flow test script:
bash tooling/data-flow-test/test-data-flow.sh
Analyze the output and report:
If specific sections were requested, use the appropriate flag:
--state — container state only--core — Core tests only--query — Query Service tests only--mcp — MCP tests only--flow — end-to-end data flow only--json — append for machine-readable outputThe script tests these data flow paths:
| Test Area | What's Checked |
|---|---|
| Container State | Port reachability for Core (3280), Query Service (3283), MCP (3904), PostgreSQL (3284) |
| Core Health | /health, /api/v1/stats, /api/v1/events/query, /api/v1/projections, /api/v1/schemas, /api/v1/snapshots, /api/v1/topology |
| Query Service Health | /api/health, /api/health/live, /api/health/ready |
| Query Service Proxy | /api/tenant, /api/tenant/usage, /api/events, /api/events/streams, /api/events/types, /api/openapi |
| MCP | /health |
| E2E Write Path | Create event via Query Service (or Core fallback) |
| E2E Read Path | Read event back from Core, read via Query Service, verify in streams/types lists |
| Query DSL | Execute DSL query for the test entity |
backend: degraded. Event proxy calls will fail./api/v1/ paths instead of /api/ paths.Override default ports if your Docker mapping differs:
CORE_PORT=3280 QUERY_PORT=3283 MCP_PORT=3904 bash tooling/data-flow-test/test-data-flow.sh
To bring the stack up/down for testing:
# Start
docker compose -f ~/Projects/alphaSigmaPro/wallet/docker/docker-compose.chronos.yml up -d
# Stop
docker compose -f ~/Projects/alphaSigmaPro/wallet/docker/docker-compose.chronos.yml down