altinity
- 35 skills
- 0 followers
- 8 hours ago last updated
- ▌ Testflows · altinity bundleRetrieve and analyze TestFlows logs with tfs, then inspect ClickHouse _instances server error logs. Use when analyzing TestFlows test failures, reading test.log/raw.log, running tfs show/transform/report/document, debugging a local regression.py run, or looking at clickhouse-server.err.log under _instances.
- ▌ Compose Env · altinity bundleBring up a clickhouse-regression docker-compose cluster from a suite env folder without running regression.py, then open an interactive clickhouse client. Use when the user wants to start or stop a local test cluster, docker compose up inside cas_env/iceberg_env/s3_env or any *_env folder, or run manual SQL against those nodes.
- ▌ Export Part · altinityRun export_part tests in the s3 test suite. Use when the user wants to run export part tests, test ALTER TABLE EXPORT PART functionality, or test exporting MergeTree parts to S3.
- ▌ Cicd Trigger · altinityTrigger GitHub Actions workflows for ClickHouse regression tests. Use when the user wants to run CI/CD tests, trigger regression workflows, or check running workflow status.
- ▌ Usability Audit · altinityPerform a usability audit of a feature, PR, or test suite from the user/operator's point of view and produce a clean list of issues they may face in normal flow, failure modes, cancellation, retries, concurrent admin actions, diagnostics, and at scale. Use when the user asks for a usability audit, user-journey trace, operator experience review, or wants a report of issues an operator may hit when using a feature. Also use proactively after completing a feature or PR audit to append an operational readiness section.
- ▌ CI Job Forensics · altinityExtract facts from a CI job - fetch logs (including previous attempts), read huge artifacts without downloading them, identify the runner hardware, bisect a regression on branch runs, and interpret broken_tests.yaml matching.
- ▌ Export Partition · altinityRun export partition tests in the s3 test suite. Use when the user wants to run export partition tests, test ALTER TABLE EXPORT PARTITION ID functionality, or test exporting MergeTree partitions to S3.
- ▌ Technical Writing · altinityUse when writing or revising any prose a person will read — chat replies to the user, docs, READMEs, wiki pages, CLI --help text, error and log messages, commit bodies, PR descriptions, release notes, code comments. Also use when text reads as stiff, hedged, padded, corporate, or breezy, or when an error message leaves the reader with nothing to do. Portable voice-and-tone rules adapted from the Microsoft Writing Style Guide; carries no Microsoft-specific terminology or UI conventions.
- ▌ Pr CI Failure Triage · altinityVerify a Pull Request's CI before approving it - QA verification, PR verification, CI triage, "check the CI of PR
- ▌ Github Issue Template · altinityWrite well-formatted GitHub issues for the Altinity ClickHouse repository following team conventions. Covers bug reports for regressions, upstream bugs, and flaky test tracking.
- ▌ Release Branch Monitor · altinity bundleMonitor MasterCI failures on a release branch (e.g. antalya-26.1) by cross-referencing the last N CI run reports. Use when the user asks to "check failing tests on branch X", "monitor a release branch", "see which tests are flaky on antalya-XX.X before release", or wants to know which failures are consistent vs flaky vs isolated across recent MasterCI runs.
- ▌ Distributed Systems Audit · altinityPerform a static, distributed-systems-focused audit of a PR or feature. Use when reviewing changes to replication, cluster coordination, RPC/network paths, consensus- or Keeper-style dependencies, multi-node protocols, distributed state, retries/timeouts, or any logic whose correctness depends on behavior across nodes under partial failure.
- ▌
- ▌
- ▌ Regression Test Database Investigation · altinity bundleInvestigate one Altinity regression-suite (TestFlows) failure - "investigate this test", "why is this scenario failing". Handles scenario paths starting with a slash (`/swarms/...`, `/lightweight delete/...`, `/ldap/authentication`) - anything recorded in `gh-data.clickhouse_regression_results`. Reaches a verdict - regression, pre-existing flaky, infrastructure, cascade, or unknown - using the CI database, the ClickHouse source when the error comes from the server, and this repository's own history. Works without the database password.
- ▌ Altinity Profiler Clickhouse · altinity bundleProfile a ClickHouse cluster via MCP and emit a per-cluster "analyst" Skill the user can save in claude.ai. Activate when the user asks to "profile this ClickHouse", "generate an analyst skill", "build a schema guide", "map the data in this cluster", or regenerate an existing cluster-analyst Skill after schema changes. Works against any ClickHouse with read-only SELECT/SHOW/DESCRIBE access via an `execute_query` MCP tool (e.g. the Altinity MCP server). Outputs a 5-file markdown bundle plus a README.
- ▌ Altinity Expert Clickhouse Logs · altinity bundleAnalyze ClickHouse system log table health including TTL configuration, disk usage, freshness, and cleanup. Use for system log issues and TTL configuration.
- ▌ Altinity Expert Clickhouse Kafka · altinity bundleDiagnose ClickHouse Kafka engine health, consumer status, thread pool capacity, consumption issues, and Kafka rack-awareness problems. Use for Kafka lag, consumer errors, thread starvation, or unexpected cross-AZ Kafka traffic and cost.
- ▌ Altinity Expert Clickhouse Caches · altinity bundleAnalyze ClickHouse cache systems including mark cache, uncompressed cache, and query cache. Use for cache hit ratio issues and cache tuning.
- ▌ Altinity Expert Clickhouse Grants · altinity bundleDiagnose and resolve ClickHouse grant and authentication errors, especially after upgrades. Use when queries fail with ACCESS_DENIED/NOT_ENOUGH_PRIVILEGES, AUTHENTICATION_FAILED/WRONG_PASSWORD/REQUIRED_PASSWORD, or ON CLUSTER privilege errors; when system.* or INFORMATION_SCHEMA access is denied; or when grant behavior changes after version upgrades.
- ▌ Altinity Expert Clickhouse Memory · altinity bundleDiagnose ClickHouse RAM usage, OOM errors, memory pressure, and allocation patterns. Use for memory-related issues and out-of-memory errors.
- ▌ Altinity Expert Clickhouse Merges · altinity bundleDiagnose ClickHouse merge performance, part backlog, and 'too many parts' errors. Use for merge issues and part management problems.
- ▌ Altinity Expert Clickhouse Schema · altinity bundleAnalyze ClickHouse table structure, partitioning, ORDER BY keys, materialized views, and identify schema design anti-patterns. Use for table design issues and optimization.
- ▌ Altinity Expert Clickhouse Metrics · altinity bundleReal-time monitoring of ClickHouse metrics, events, and asynchronous metrics. Use for load average, connections, queue monitoring, and resource saturation.
- ▌ Altinity Expert Clickhouse Storage · altinity bundleDiagnose ClickHouse disk usage, compression efficiency, part sizes, and storage bottlenecks. Use for disk space issues and slow IO.
- ▌ Altinity Expert Clickhouse Overview · altinity bundleRuns a fast ClickHouse server health snapshot and routes to specialist skills. Use as the entry point for general health checks or when the problem area is not yet known.
- ▌ Altinity Expert Clickhouse Part Log · altinity bundleDiagnose ClickHouse issues by analyzing system.part_log (part creation, merges, mutations, downloads, removals, moves). Use for too many parts / micro-batch inserts, merge backlog or slow merges, mutation storms (ALTER DELETE/UPDATE), unusual replication DownloadPart churn, unexpected RemovePart spikes, or ZooKeeper/Keeper znode growth correlated with part activity.
- ▌ Altinity Expert Clickhouse Security · altinity bundleRead-only ClickHouse security audit expert for live or exported systems. Use when assessing ClickHouse security posture, reviewing users, roles, grants, settings profiles, row policies, table functions, external sources, table engines, executable UDFs, audit logs, named collections, password hash hygiene, SQL SECURITY DEFINER, impersonation, TLS/network exposure, Keeper/interserver security, encryption at rest, backups, the HTTP interface surface, cluster security, or version-specific ClickHouse security behavior. Diagnoses from SQL/system tables, supplied configuration files, query logs, access metadata, and ClickHouse/Altinity documentation.
- ▌ Altinity Expert Clickhouse Ingestion · altinity bundleDiagnose ClickHouse INSERT performance, batch sizing, part creation patterns, and ingestion bottlenecks. Use for slow inserts and data pipeline issues.
- ▌ Altinity Expert Clickhouse Mutations · altinity bundleTrack and diagnose ClickHouse ALTER UPDATE, ALTER DELETE, and other mutation operations. Use for stuck mutations and mutation performance issues.
- ▌ Altinity Expert Clickhouse Reporting · altinity bundleDiagnose ClickHouse SELECT query performance, analyze query patterns, identify slow queries, and find optimization opportunities. Use for query latency and timeout issues.
- ▌ Altinity Expert Clickhouse Connection · altinityEstablishes the ClickHouse connection mode, cluster macro, and default log timeframe for diagnostics. Use first, before any other altinity-expert-clickhouse skill, to verify connectivity and set shared analysis rules.
- ▌ Altinity Expert Clickhouse Replication · altinity bundleDiagnose ClickHouse replication health, Keeper connectivity, replica lag, and queue issues. Use for replication lag and read-only replica problems.
- ▌ Altinity Expert Clickhouse Dictionaries · altinity bundleAnalyze ClickHouse external dictionaries including configuration, memory usage, reload status, and performance. Use for dictionary issues and load failures.
- ▌ Altinity Expert Clickhouse Index Analysis · altinity bundleAnalyze whether ClickHouse indexes (PRIMARY KEY, ORDER BY, skipping indexes, projections) are being used effectively for actual query patterns. Use when investigating index effectiveness, ORDER BY key design, query-to-index alignment, or when queries scan more data than expected.