- Blog To DocsConvert ClickHouse blog content into docs pages. Use when porting a feature announcement, tutorial, or deep-dive from the blog into the docs site. Covers content extraction, asset handling, structural transformation, and voice conversion.ClickHouse/clickhouse-docs211
- Clickstack Otel CollectorUse when a user wants to wire an OpenTelemetry collector into a Managed ClickStack service on ClickHouse Cloud, either by deploying a new local collector (Docker run or Docker Compose) or by configuring their own existing collector, then send rich synthetic telemetry and verify it is visible in ClickStack.ClickHouse/clickhouse-docs211
- Docs DraftingVoice, style, and content rules for writing ClickHouse docs. Use when drafting new pages, rewriting sections, or applying editorial polish. Covers identity, voice, pacing, sentence habits, anti-patterns, AI-ism removal, prose tightening, editorial instinct, linking, keywords, content integrity, and marketing site alignment.ClickHouse/clickhouse-docs211
- Docs Pr ReviewReview a docs PR from someone else. Triage issues by severity, draft comments with rationale, and focus on what matters. Use when reviewing a PR, not when checking your own work (use docs-pre-ship-review for that).ClickHouse/clickhouse-docs211
- Docs Pre Ship ReviewReview a ClickHouse docs page before shipping. Runs the self-review checklist, Vale linting, and PR review rubric. Use when doing a final check, running Vale, or when asked "is this ready to ship."ClickHouse/clickhouse-docs211
- Component Css Modules MigrationMigrate a click-ui component from styled-components to CSS Modules with byte-for-byte visual regression coverage. Use whenever a component still uses styled-components and is on the CSS Modules migration list.ClickHouse/click-ui135
- Cpp Header TemplateGenerate C++ header files following Google Style Guide. Use when creating new header files or asking for a header template.ClickHouse/pg_stat_ch123
- Cpp Naming CheckCheck C++ naming conventions against Google Style Guide. Use when checking if names follow conventions or when renaming identifiers.ClickHouse/pg_stat_ch123
- Cpp ReviewReview C++ code against Google C++ Style Guide. Use when reviewing C++ code, pull requests, or when asked to check code style compliance.ClickHouse/pg_stat_ch123
- Create New ReleaseCreate and push a new semver release tag. Asks for release type (patch/minor/major), validates commit exists on remote, bumps version, and pushes the tag.ClickHouse/pg_stat_ch123
- Google Cpp StyleGoogle C++ Style Guide rules for writing clean, maintainable C++ code. Use when writing C++, reviewing code, discussing naming conventions, formatting, class design, or any C++ best practices. Covers headers, scoping, classes, functions, naming, comments, and formatting.ClickHouse/pg_stat_ch123
- ReviewReview a Pull Request for correctness, safety, performance, and compliance. Use when the user wants to review a PR or diff.ClickHouse/clickhouse-cs96
- ReviewReview a Pull Request for correctness, safety, performance, and compliance. Use when the user wants to review a PR or diff.ClickHouse/clickhouse-cs96
- Nerve DevelopmentNerve backend (Python) and frontend (React/TS) development and code contribution. Use when writing Python code for Nerve, fixing bugs, adding features, reviewing Nerve PRs, building the frontend, running tests, or working with the Nerve codebase. Triggers on "nerve code", "nerve PR", "fix nerve", "nerve feature", "nerve test", "build nerve UI", "nerve migration".ClickHouse/nerve90
- Nerve Workspace ConfigChange your own configuration — skills, cron jobs, sources, and settings that live in the workspace. Covers both routes: a pull request when the workspace is a shared config repo (and the only route when this instance is locked), or a direct edit when the workspace is purely local. Use when asked to add/edit/remove a cron job, create or change a skill, adjust settings, or "change your config". Triggers on "add a cron", "change your schedule", "edit your config", "update settings", "propose a conClickHouse/nerve90
- ShareShare a Claude Code session to pastila.nl and return a viewer link. Shares the current session by default, or a session specified as a transcript path, a session id, or a project. Use when the user asks to share, publish, or get a link to this conversation or to a session/transcript.ClickHouse/pastila85
- ReviewReview a pull request, branch, or diff for the ClickHouse Entity Framework Core provider. Use when the user asks to review a PR, branch, commit range, or working tree diff for correctness, safety, performance, tests, documentation, and project compliance.ClickHouse/ClickHouse.EntityFrameworkCore23
- Clickhouse Best PracticesMUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 31 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.clickhouse/clickhouse-claude-code-plugin7
- Clickhouse Best PracticesMUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 31 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.ClickHouse/clickhouse-claude-code-plugin7
- SetupGuides users through setting up the ClickHouse MCP server connection bundled with this plugin. Use when the user first installs the plugin or has trouble connecting to ClickHouse.ClickHouse/clickhouse-claude-code-plugin7
- SetupGuides users through setting up the ClickHouse MCP server connection bundled with this plugin. Use when the user first installs the plugin or has trouble connecting to ClickHouse.clickhouse/clickhouse-claude-code-plugin7
- Debug Reference TestsDebug ClickHouse reference test failures (the tests/clickhouse-reference-{ast,format,explain,round-trip} suites). Use when one or more of those reference cases fail and you need to see what this library produced vs. the committed expected output. Maps a failing case to the right diff:* npm script and walks through isolating, diffing, and fixing the cause in the grammar/formatter/explain code.ClickHouse/clickhouse-js-parser6
- Clickhouse DiagnosticAnalyse a ClickHouse support-diagnostic bundle (clickhouse_backup_*.tar.gz or its extracted folder: system.* JSONL dumps, dashboard.html, host_info.json, logs/, configuration/) and produce an evidence-backed health summary — parts and merges, replication and Keeper, disk, memory/CPU, queries, inserts, mutations/TTL, host tunables — with recommended actions and follow-up prompts. Also explains how to run clickhouse-diagnostic (grants, modes, windows, query analysis, gov mode) and what to re-colleClickHouse/clickhouse-diagnostics2
- Chdb DatastoreUse when the user has tabular data (pandas DataFrame, parquet, csv, Arrow, json) and wants to filter, group, aggregate, join, or speed up slow pandas. Provides chDB DataStore — same pandas API, ClickHouse engine underneath. Also handles reading from S3, MySQL, PostgreSQL, MongoDB, ClickHouse Cloud, Iceberg, Delta Lake as DataFrames and joining across sources. TRIGGER when: user mentions DataFrame, parquet, csv, "fast pandas", "speed up pandas", or cross-source DataFrame joins; user imports `chdbClickHouse/mintlify-docs-dev1
- Chdb SqlUse when the user wants to run SQL — especially analytical SQL — on local files (parquet/csv/json), URLs, S3 paths, or remote databases (Postgres, MySQL, MongoDB, ClickHouse Cloud, Iceberg, Delta Lake) without setting up a server. Provides chDB — embedded ClickHouse SQL in Python with 1000+ functions, Session for stateful multi-step pipelines, parametrized queries, and cross-source joins via `s3()`, `mysql()`, `postgresql()`, `iceberg()`, `deltaLake()`, `remoteSecure()` table functions. TRIGGER ClickHouse/mintlify-docs-dev1
- Clickhouse Architecture AdvisorMUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs. Complements clickhouse-best-practices with decision frameworks and explicit provenance labels.ClickHouse/mintlify-docs-dev1
- Clickhouse Best PracticesMUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 31 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.ClickHouse/mintlify-docs-dev1
- Clickhouse Js Node CodingWrite idiomatic application code with the ClickHouse Node.js client (`@clickhouse/client`). Use this skill whenever a user is *building* against the Node.js client — configuring the client, pinging, inserting rows in JSON or raw formats, selecting and parsing results, binding query parameters, managing sessions and temporary tables, working with data types or customizing JSON parsing. Do NOT use for browser/Web client code.ClickHouse/mintlify-docs-dev1
- Clickhouse Js Node TroubleshootingTroubleshoot and resolve common issues with the ClickHouse Node.js client (@clickhouse/client). Use this skill whenever a user reports errors, unexpected behavior, or configuration questions involving the Node.js client specifically — including socket hang-up errors, Keep-Alive problems, stream handling issues, data type mismatches, read-only user restrictions, proxy/TLS setup problems, or long-running query timeouts. Trigger even when the user hasn't precisely named the issue; vague symptoms liClickHouse/mintlify-docs-dev1
- Clickhouse Managed Postgres RcaMUST USE when investigating performance issues on a ClickHouse-managed Postgres instance. Provides an evidence-based RCA workflow that scrapes the Prometheus endpoint for system signal, pulls per-digest evidence from the Slow Query Patterns API, and recommends (does not apply) a fix.ClickHouse/mintlify-docs-dev1
- Clickhousectl Cloud DeployUse when a user wants to deploy ClickHouse to the cloud, go to production, use ClickHouse Cloud, host a managed ClickHouse service, or migrate from a local ClickHouse setup to ClickHouse Cloud.ClickHouse/mintlify-docs-dev1
- Clickhousectl Local DevUse when a user wants to build an application with ClickHouse, set up a local ClickHouse development environment, install ClickHouse, create a local server, create tables, or start developing with ClickHouse. Covers the full flow from zero to a working local ClickHouse setup.ClickHouse/mintlify-docs-dev1
- Migrate Docusaurus To MintlifyUse when migrating ClickHouse docs pages from Docusaurus (clickhouse-docs) to Mintlify format in this repo, or when wiring up the migration script. Covers frontmatter rewrites, body transforms, component mapping, link normalization, and redirect generation. Slugs are canonical and must never be rewritten.ClickHouse/mintlify-docs-dev1
- Clickhouse Best PracticesMUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 31 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.ClickHouse/clickhouse-grok-plugin
- SetupGuides users through setting up the ClickHouse MCP server connection bundled with this plugin. Use when the user first installs the plugin or has trouble connecting to ClickHouse.ClickHouse/clickhouse-grok-plugin