Claude Skills by thedixitjain

| ClickHouse incident response — triage, diagnose, and remediate server issues using system tables, kill stuck queries, and execute recovery procedures. Use when ClickHouse is slow, unresponsive, OOM-killed, out of disk, backing up merges, or producing errors in production and you need an on-call playbook. Trigger with \"clickhouse incident\", \"clickhouse outage\", \"clickhouse down\", \"clickhouse emergency\", \"clickhouse on-call\", \"clickhouse broken\".

ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.

ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.

| Execute ClickHouse schema migrations — ALTER TABLE operations, data migration between engines, versioned migration runners, and zero-downtime schema changes. Use when modifying ClickHouse schemas, migrating data between tables, or implementing versioned migration workflows. Trigger with \"clickhouse migration\", \"clickhouse ALTER TABLE\", \"clickhouse schema change\", \"migrate clickhouse\", \"clickhouse add column\", or \"clickhouse schema migration\".

| Optimize ClickHouse query performance with indexing, projections, settings tuning, and query analysis using system tables. Use when queries are slow, investigating performance bottlenecks, or tuning ClickHouse server settings. Trigger with \"clickhouse performance\", \"optimize clickhouse query\", \"clickhouse slow query\", \"clickhouse indexing\", \"clickhouse tuning\", \"clickhouse projections\".

| Configure ClickHouse query concurrency, memory quotas, and connection limits. Use when hitting \"too many simultaneous queries\", managing concurrent users, or tuning server-side resource limits so an app never starves the cluster. Trigger with \"clickhouse rate limit\", \"clickhouse concurrency\", \"clickhouse quota\", \"too many simultaneous queries\", \"clickhouse connection limit\".

| Production reference architecture for ClickHouse-backed applications — project layout, data flow, multi-tenant patterns, and operational topology. Use when designing a new ClickHouse system, reviewing an existing analytics architecture, or establishing standards for ClickHouse integrations. Trigger with \"clickhouse architecture\", \"clickhouse project structure\", \"clickhouse design\", \"clickhouse multi-tenant\", \"clickhouse reference\".

| Production-ready patterns for @clickhouse/client — streaming inserts, typed queries, error handling, and connection management. Use when building robust ClickHouse integrations, implementing streaming inserts or low-memory streaming reads, or establishing team coding standards. Trigger with \"clickhouse SDK patterns\", \"clickhouse client patterns\", \"clickhouse best practices\", \"clickhouse streaming insert\".

| Use when upgrading ClickHouse server versions or the @clickhouse/client SDK, handling breaking changes between versions, or migrating from older client libraries — covers version checks, changelog review, staged upgrade, post-upgrade validation, and rollback. Trigger with phrases like \"upgrade clickhouse\", \"clickhouse version upgrade\", \"update clickhouse client\", \"clickhouse breaking changes\", \"new clickhouse version\".

'Diagnose and fix ClickUp API v2 errors by HTTP status and error code. Use when encountering ClickUp API errors, debugging failed requests, or troubleshooting OAUTH_* error codes, 401s, 429s, and 500s. Trigger: \"clickup error\", \"fix clickup\", \"clickup not working\", \"clickup 401\", \"clickup 429\", \"OAUTH error\", \"debug clickup API\". '

'Collect ClickUp API diagnostic information for troubleshooting and support. Use when encountering persistent issues, preparing support tickets, or collecting API connectivity and rate limit diagnostics. Trigger: \"clickup debug\", \"clickup diagnostics\", \"clickup support bundle\", \"collect clickup logs\", \"clickup health check\". '

'Execute ClickUp API incident response: triage, diagnosis, mitigation, and postmortem for API failures and integration outages. Trigger: \"clickup incident\", \"clickup outage\", \"clickup down\", \"clickup on-call\", \"clickup emergency\", \"clickup API broken\". '

'Migrate to ClickUp from other project management tools (Jira, Asana, Trello) or migrate data between ClickUp workspaces using API v2. Trigger: \"migrate to clickup\", \"clickup migration\", \"jira to clickup\", \"asana to clickup\", \"trello to clickup\", \"clickup data migration\", \"move tasks to clickup\", \"clickup import\". '

'Optimize ClickUp API v2 performance with caching, pagination, connection pooling, and request batching patterns. Trigger: \"clickup performance\", \"optimize clickup\", \"clickup latency\", \"clickup caching\", \"clickup slow\", \"clickup batch requests\", \"clickup pagination\". '

'Production architecture for ClickUp API v2 integrations with layered design, custom fields, time tracking, goals, and two-way sync patterns. Trigger: \"clickup architecture\", \"clickup design\", \"clickup project structure\", \"clickup custom fields\", \"clickup time tracking\", \"clickup goals API\". '

'Production-ready ClickUp API v2 client patterns with typed wrappers, error handling, caching, and multi-tenant support. Trigger: \"clickup client wrapper\", \"clickup SDK patterns\", \"clickup best practices\", \"clickup typescript client\", \"clickup API wrapper\", \"production clickup code\". '

'Migrate between ClickUp API versions (v2 to v3) and handle breaking changes. Use when upgrading API versions, adapting to endpoint changes, or migrating between ClickUp plan tiers. Trigger: \"upgrade clickup API\", \"clickup v2 to v3\", \"clickup breaking changes\", \"clickup API migration\", \"clickup deprecation\". '

Plan client onboarding. Use when: kickoff agenda, discovery questionnaire, account setup checklist, 30-60-90 day plan.

Commit the session to durable vault memory and prepare a clean resume point

CloudFormation template optimization, nested stacks, drift detection, and production-ready patterns. Use when writing or reviewing CF templates.

Detects architectural clusters and coupling boundaries via community detection on the code graph. Use when identifying module groupings or refactoring targets.

Technology-agnostic prompt generator that creates customizable AI prompts for scanning codebases and identifying high-quality code exemplars. Supports multiple programming languages (.NET, Java, JavaScript, TypeScript, React, Angular, Python) with configurable analysis depth, categorization methods, and documentation formats to establish coding standards and maintain consistency across development teams.

'Execute automatically formats and validates code files using Prettier and other formatting tools. Use when users mention \"format my code\", \"fix formatting\", \"apply code style\", \"check formatting\", \"make code consistent\", or \"clean up code formatting\". Handles JavaScript, TypeScript, JSON, CSS, Markdown, and many other file types. Trigger with relevant phrases based on skill purpose. '

Scans the codebase for dead code, tech debt, outdated dependencies, and code quality issues. Delegates to the Centinela (QA) agent.

Systematic code maturity assessment using Trail of Bits' 9-category framework. Analyzes codebase for arithmetic safety, auditing practices, access controls, complexity, decentralization, documentation, MEV risks, low-level code, and testing. Produces professional scorecard with evidence-based ratings and actionable recommendations.

Rewrites unprofessional code comments into clear ones and performs non-semantic cleanup. Use to professionalize code without altering logic or behavior.

Applies KISS, YAGNI, and SOLID principles for clean code with reduced complexity. Use when refactoring or reviewing code for over-engineering.

Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions. Use when reviewing changes, enforcing quality standards, or identifying technical debt.

Use when working with code refactoring context restore

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti

Improves code quality across duplication, efficiency, and architectural fit. Use when code passes tests but quality is poor or before a major release.

Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.

Use after completing implementation steps and before merging — reviews against plan and HOTL contracts.

Standalone code review methodology for structured, severity-classified code assessment

Standalone code review methodology for structured, severity-classified code assessment

You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.

Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".

Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin, C#, .NET, Java, C, C++, Rust, Ruby, PHP, and Dart/Flutter. Analyzes PRs for complexity and risk, checks code quality for SOLID violations and code smells, generates review reports. Use when reviewing pull requests, analyzing code quality, identifying issues, generating review checklists.

Review completed implementation batches for spec compliance and code quality. Invoke after execution batches complete, before merging, or when a review gate is reached in the workflow.

Elite code review expert specializing in modern AI-powered code

Searches GitHub for existing implementations, libraries, or patterns. Use when finding code examples or prior art on a topic during a research session.

Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST.

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to \"simplify code\", \"clean up code\", \"refactor for clarity\", \"improve readability\", or review recently modified code for elegance. Focuses on project-specific best practices.