Claude Skills by thedixitjain

Produce consistent, auditable release notes from Conventional Commits. Separates commit parsing, semantic-bump logic, and changelog rendering for automated releases with editorial control. Use when cutting a release, generating CHANGELOG.md from git history, computing the next semantic version from commits, automating release notes in CI, or planning a hotfix/rollback. Examples: 'generate the changelog for v1.4.0', 'what version bump do these commits require', 'we need an emergency hotfix pro...

'Generate changelog generator operations. Auto-activating skill for Technical Documentation. Triggers on: changelog generator, changelog generator Part of the Technical Documentation skill category. Use when working with changelog generator functionality. Trigger with phrases like \"changelog generator\", \"changelog generator\", \"changelog\". '

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Draft changelog PRs by collecting GitHub/Slack/Git changes, formatting with templates, running quality gates, and preparing a branch/PR. Use when generating weekly/monthly release notes or when the user asks to create a changelog from recent merges. Trigger with \"changelog weekly\", \"generate release notes\", \"draft changelog\", \"create changelog PR\".

Create release notes and product updates that developers actually read and care about. This skill covers changelog formatting, versioning communication, breaking change announcements, deprecation notices, and building anticipation for new features. Trigger phrases: \"changelog\",...

Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.

Use when planning, running, or learning from chaos engineering experiments. Triggers on \"chaos experiment\", \"fault injection\", \"gameday\", \"resilience test\", \"blast radius\", \"steady state\", \"abort criteria\", \"Chaos Toolkit\", \"Chaos Mesh\", \"Litmus\", \"Gremlin\", \"AWS FIS\", or any deliberate failure-injection question. Ships experiment designer, blast-radius calculator, and postmortem generator (all stdlib Python), 4 references on chaos principles + experiment design + atta...

Use when targeting Chemical Engineering Journal or deciding whether an applied chemical-engineering / functional-materials manuscript fits this venue. Encodes the journal's fit, the applied-advance-with-mechanism bar, performance and benchmarking rigor, house style, the applied-vs-fundamentals routing, official-submission re-check, and desk-reject heuristics.

Use Chrome DevTools MCP for frontend performance work such as slow page loads, LCP, CLS, INP, Lighthouse regressions, scripting hotspots, or layout thrash. Trigger when the user asks for page speed analysis, Core Web Vitals debugging, trace-based investigation, or before-and-after performance verification.

Use when choosing the solution route and delivering the algorithm section of a 《中国管理科学》 (Chinese Journal of Management Science) manuscript — exact vs heuristic vs learning-based, with pseudocode, property analysis, and baseline comparison. Covers solving the model; the experiments that showcase it belong to cjms-numerical-experiments.

\"Build different types of Claude-powered applications \\u2014 chatbots,\\ \\ RAG systems,\\nUse when working with architecture-variants patterns.\\nagents, content\\ \\ pipelines, and code generation tools.\\nTrigger with \\\"claude architecture\\\", \\\"\\ anthropic rag\\\", \\\"build with claude\\\",\\n\\\"claude agent pattern\\\", \\\"anthropic app\\ \\ design\\\".\\n\"

\"Diagnose and fix Anthropic API errors \\u2014 authentication, rate limits,\\n\\ Use when working with common-errors patterns.\\noverloaded, context length, and content\\ \\ policy issues.\\nTrigger with \\\"anthropic error\\\", \\\"claude 429\\\", \\\"claude overloaded\\\"\\ ,\\n\\\"anthropic not working\\\", \\\"debug claude api\\\".\\n\"

\"Collect debug evidence for Anthropic API issues \\u2014 request IDs,\\ \\ headers,\\nUse when working with debug-bundle patterns.\\nerror payloads, and reproduction\\ \\ steps for support tickets.\\nTrigger with \\\"anthropic debug\\\", \\\"claude support\\ \\ ticket\\\", \\\"anthropic request id\\\",\\n\\\"debug claude api call\\\".\\n\"

\"Respond to Anthropic API incidents \\u2014 outages, degraded performance,\\n\\ Use when working with incident-runbook patterns.\\nerror spikes, and rate limit issues\\ \\ in production.\\nTrigger with \\\"anthropic down\\\", \\\"claude outage\\\", \\\"anthropic\\ \\ incident\\\",\\n\\\"claude not responding\\\", \\\"anthropic 529\\\".\\n\"

\"Migrate from OpenAI/GPT to Anthropic/Claude \\u2014 API differences,\\n\\ Use when working with migration-deep-dive patterns.\\nprompt adaptation, SDK swap,\\ \\ and feature mapping.\\nTrigger with \\\"migrate to claude\\\", \\\"openai to anthropic\\\"\\ ,\\n\\\"switch from gpt to claude\\\", \\\"replace openai with anthropic\\\".\\n\"

\"Optimize Anthropic API latency \\u2014 streaming, prompt caching, model\\ \\ selection,\\nUse when working with performance-tuning patterns.\\nconnection reuse,\\ \\ and parallel requests.\\nTrigger with \\\"anthropic slow\\\", \\\"claude latency\\\", \\\"\\ speed up anthropic\\\",\\n\\\"anthropic performance\\\", \\\"claude response time\\\".\\n\"

\"Build Claude Code plugins \\u2014 skills, agents, MCP servers, hooks,\\ \\ and slash commands.\\nUse when working with reference-architecture patterns.\\n\\ The complete guide to extending Claude Code with the Anthropic plugin system.\\n\\ Trigger with \\\"claude code plugin\\\", \\\"build a skill\\\", \\\"create mcp server\\\",\\n\\ \\\"anthropic plugin architecture\\\", \\\"claude code hooks\\\".\\n\"

'Upgrade Anthropic SDK versions and migrate between Claude model generations. Use when working with upgrade-migration patterns. Trigger with \"upgrade anthropic sdk\", \"migrate claude model\", \"anthropic breaking changes\", \"new claude model\". '

'Diagnose and fix Clari API errors including auth failures, export issues, and data mismatches. Use when Clari API calls fail, exports return empty data, or forecast numbers do not match the UI. Trigger with phrases like \"clari error\", \"clari not working\", \"clari api failure\", \"fix clari\", \"debug clari\". '

'Optimize Clari API usage and integration costs. Use when reducing API call volume, optimizing export frequency, or evaluating Clari license utilization. Trigger with phrases like \"clari cost\", \"clari api usage\", \"reduce clari calls\", \"clari optimization\". '

'Collect Clari API diagnostic info for support cases. Use when preparing a support ticket, collecting API response samples, or documenting integration issues. Trigger with phrases like \"clari debug\", \"clari support bundle\", \"collect clari diagnostics\", \"clari troubleshoot\". '

'Optimize Clari API performance with caching, batch exports, and data pipeline efficiency. Use when exports take too long, optimizing data warehouse load times, or reducing API calls in multi-forecast environments. Trigger with phrases like \"clari performance\", \"clari slow export\", \"optimize clari pipeline\", \"clari caching\". '

'Reference architecture for Clari revenue intelligence integrations. Use when designing a forecast data platform, planning Clari integration architecture, or establishing team patterns for revenue analytics. Trigger with phrases like \"clari architecture\", \"clari data platform\", \"clari integration design\", \"clari best practices\". '

'Handle Clari API version changes and export schema migrations. Use when Clari updates their API, export format changes, or migrating from v3 to v4 API. Trigger with phrases like \"upgrade clari\", \"clari api migration\", \"clari schema change\", \"clari v4 migration\". '

Personal coach that teaches users to become Claude power users. Use this skill the FIRST time a user asks to \"learn Claude\", \"be a power user\", \"coach me\", \"teach me Claude tricks\", \"what can Claude do\", \"make me better at prompting\", or any variation. After activation, also use it on EVERY subsequent turn to detect missed optimization opportunities (vague prompts, ignored capabilities, manual work Claude could automate) and surface a single power-user tip. Trigger generously — mo...

Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops; use night-market-operations.

Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions \"CLAUDE.md maintenance\" or \"project memory optimization\".

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.

'Deep-debug complex Clay enrichment failures, provider degradation, and data flow issues. Use when standard troubleshooting fails, investigating intermittent enrichment failures, or preparing detailed evidence for Clay support escalation. Trigger with phrases like \"clay hard bug\", \"clay mystery error\", \"clay impossible to debug\", \"difficult clay issue\", \"clay deep debug\". '

'Choose and implement Clay integration architecture for different scales and use cases. Use when designing new Clay integrations, comparing direct vs queue-based vs event-driven, or planning architecture for Clay-powered data operations. Trigger with phrases like \"clay architecture\", \"clay blueprint\", \"how to structure clay\", \"clay integration design\", \"clay event-driven\". '

'Diagnose and fix the most common Clay errors and integration issues. Use when encountering Clay errors, debugging failed enrichments, or troubleshooting webhook delivery problems. Trigger with phrases like \"clay error\", \"fix clay\", \"clay not working\", \"debug clay\", \"clay enrichment failed\", \"clay webhook error\". '

'Collect Clay debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Clay integration problems. Trigger with phrases like \"clay debug\", \"clay support bundle\", \"collect clay logs\", \"clay diagnostic\", \"clay support ticket\". '

'Execute Clay incident response procedures for enrichment failures, credit exhaustion, and data flow outages. Use when Clay enrichments stop working, webhook delivery fails, or CRM sync breaks in production. Trigger with phrases like \"clay incident\", \"clay outage\", \"clay down\", \"clay emergency\", \"clay broken\", \"clay enrichment stopped\". '

'Identify and avoid the top Clay anti-patterns, gotchas, and integration mistakes. Use when reviewing Clay integrations for issues, onboarding new team members, or auditing existing Clay table configurations. Trigger with phrases like \"clay mistakes\", \"clay anti-patterns\", \"clay pitfalls\", \"clay what not to do\", \"clay gotchas\", \"clay code review\". '

'Migrate to Clay from other enrichment tools or consolidate multiple data sources into Clay. Use when migrating from ZoomInfo, Apollo, Clearbit, or custom enrichment scripts to Clay, or consolidating fragmented enrichment workflows. Trigger with phrases like \"migrate to clay\", \"clay migration\", \"switch to clay\", \"replace zoominfo with clay\", \"consolidate enrichment tools\". '

'Optimize Clay table enrichment throughput, reduce processing time, and improve hit rates. Use when experiencing slow enrichment, poor email find rates, or needing to process large tables efficiently. Trigger with phrases like \"clay performance\", \"optimize clay\", \"clay slow\", \"clay throughput\", \"clay fast enrichment\", \"clay batch optimization\". '

'Design production Clay enrichment pipelines with table schemas, waterfall patterns, and CRM sync. Use when architecting new Clay integrations, reviewing data flow design, or establishing enrichment pipeline standards. Trigger with phrases like \"clay architecture\", \"clay best practices\", \"clay pipeline design\", \"clay reference\", \"clay data flow\". '

'Navigate Clay plan changes, pricing migrations, and feature upgrades. Use when upgrading Clay plans, migrating to the 2026 pricing model, or adapting integrations to new Clay features. Trigger with phrases like \"upgrade clay\", \"clay migration\", \"clay pricing change\", \"clay plan upgrade\", \"clay new pricing\". '

Review generated or changed production code with Clean Code, SOLID, DRY, KISS, YAGNI, and LLM-specific failure-mode checks.

This skill embodies the principles of \\\"Clean Code\\\" by Robert C. Martin (Uncle Bob). Use it to transform \\\"code that works\\\" into \\\"code that is clean.\\\"

Use for authorized clean-room, reverse-engineering, source-to-implementation, compatibility rewrite, or migration tasks. Produces clean behavioral specs, implementation plans, clean code changes, verification reports, QC reports, open questions, and test plans without moving source expression into the clean implementation.

'Comprehensive codebase cleanup across 11 quality dimensions: dead code, duplication, weak types, circular deps, defensive cruft, legacy code, AI slop, type consolidation, security, performance, and async patterns. Analyzes code with confidence scoring and verifies changes with build/test gates. Use when codebase has accumulated tech debt, after major feature work, before releases, or when code quality metrics are declining. Trigger with \"/cleanup-code-code\", \"clean up the codebase\", \"re...

'Collect comprehensive debug information for Clerk issues. Use when troubleshooting complex problems, preparing support tickets, or diagnosing intermittent issues. Trigger with phrases like \"clerk debug\", \"clerk diagnostics\", \"clerk support ticket\", \"clerk troubleshooting\". '

'Manage incident response for Clerk authentication issues. Use when handling auth outages, security incidents, or production authentication problems. Trigger with phrases like \"clerk incident\", \"clerk outage\", \"clerk down\", \"auth not working\", \"clerk emergency\". '

'Migrate from other authentication providers to Clerk. Use when migrating from Auth0, Firebase, Supabase Auth, NextAuth, or custom authentication solutions. Trigger with phrases like \"migrate to clerk\", \"clerk migration\", \"switch to clerk\", \"auth0 to clerk\", \"firebase auth to clerk\". '

'Optimize Clerk authentication performance. Use when improving auth response times, reducing latency, or optimizing Clerk SDK usage. Trigger with phrases like \"clerk performance\", \"clerk optimization\", \"clerk slow\", \"clerk latency\", \"optimize clerk\". '

'Reference architecture patterns for Clerk authentication. Use when designing application architecture, planning auth flows, or implementing enterprise-grade authentication. Trigger with phrases like \"clerk architecture\", \"clerk design\", \"clerk system design\", \"clerk integration patterns\". '

'Manage Clerk SDK version upgrades and handle breaking changes. Use when upgrading Clerk packages, migrating to new SDK versions, or handling deprecation warnings. Trigger with phrases like \"upgrade clerk\", \"clerk migration\", \"update clerk SDK\", \"clerk breaking changes\". '

| Diagnose and fix the top 15 ClickHouse errors — query failures, insert problems, memory limits, and merge issues. Use when a ClickHouse query or insert throws an exception, a server-side error appears in logs, or a failed query needs root-cause analysis. Trigger with \"clickhouse error\", \"fix clickhouse\", \"clickhouse not working\", \"debug clickhouse\", \"clickhouse exception\", \"clickhouse syntax error\".

| Collect ClickHouse diagnostic data — system tables, query logs, merge status, and server metrics for support tickets and troubleshooting. Use when investigating persistent issues, preparing debug artifacts, or collecting evidence for ClickHouse support. Trigger with \"clickhouse debug\", \"clickhouse diagnostics\", \"clickhouse support bundle\", \"collect clickhouse logs\", \"clickhouse system tables\".