Claude Skills by thedixitjain

Comprehensive GitHub code review with AI-powered swarm coordination

Review PRs: diffs, inline comments via gh or REST.

Recover deleted commits from GitHub using REST API, web interface, and git fetch. Use when you have commit SHAs and need to retrieve actual commit content, diffs, or patches. Includes techniques for accessing \"deleted\" commits that remain on GitHub servers.

> Resolve inline code review comments on a GitHub PR. Use when asked to \"resolve review comments\", \"address PR feedback\", \"fix PR comments\", or \"work through review comments\". Fetches every inline comment with its surrounding code context, then applies each change systematically.

Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.

GitHub PR lifecycle: branch, commit, open, CI, merge.

When the user wants to optimize their GitHub profile, README, or project discoverability. Trigger phrases include \"GitHub README,\" \"README optimization,\" \"GitHub profile,\" \"GitHub stars,\" \"GitHub discoverability,\" \"awesome lists,\" or \"GitHub marketing.\"

> Guides IA through releasing a new version of a GitHub library end-to-end. Handles SemVer versioning and Keep a Changelog formatting automatically.

Generates commit messages following the gitmoji convention (https://gitmoji.dev) — picks the right emoji for the intent of the change and writes a well-formed message. Use when asked to \"write a gitmoji commit\", \"add an emoji to my commit message\", \"which gitmoji should I use\", \"gitmoji this change\", or when a project uses gitmoji-style commit messages. Works from a git diff, staged changes, or a plain description of the change. Generates the message only — does not run git commands.

>- Manages GKE application onboarding, covering containerization, deployment manifests, and migration. Use when onboarding or deploying an application to GKE for the first time, or containerizing an app for GKE. Don't use for general GKE cluster administration or upgrades (use gke-basics or gke-upgrades instead).

'Optimize Glean costs by managing indexed content volume, datasource efficiency, and connector resource usage. Trigger: \"glean costs\", \"glean optimization\", \"reduce glean indexing\". '

'Collect Glean diagnostic information for support including datasource config, indexing status, and search quality metrics. Trigger: \"glean debug\", \"glean support\", \"glean diagnostic\". '

'Triage: Is search returning results? Check Glean status page. Trigger: \"glean incident runbook\", \"incident-runbook\". '

'Migrate from Elasticsearch/Algolia: 1) Export all documents from source, 2) Transform to Glean document schema (id, title, url, body, permissions), 3) Create datasource with adddatasource, 4) Bulk index with bulkindexdocuments, 5) Validate search quality with test queries, 6) Switch search UI to use Glean Client API. Trigger: \"glean migration deep dive\", \"migration-deep-dive\". '

'Optimize Glean search relevance and indexing throughput with batch sizing, datasource configuration, and content quality improvements. Trigger: \"glean performance\", \"glean search quality\", \"glean indexing speed\". '

'Enterprise architecture: Source Systems to Connectors (Cloud Run/Lambda, event-driven or scheduled) to Glean Indexing API to Glean Search Index to Client API (Search + Chat) to Your Apps (Slack bot, portal, internal tools). Trigger: \"glean reference architecture\", \"reference-architecture\". '

'Apply production-ready Glean API patterns with typed clients, batch indexing, pagination, and error handling. Trigger: \"glean SDK patterns\", \"glean best practices\", \"glean API client\". '

'Check Glean developer changelog for API changes. Trigger: \"glean upgrade migration\", \"upgrade-migration\". '

Analyze and engineer protein glycosylation. Scan sequences for N-glycosylation sequons (N-X-S/T), predict O-glycosylation hotspots, and access curated glycoengineering tools (NetOGlyc, GlycoShield, GlycoWorkbench). For glycoprotein engineering, therapeutic antibody optimization, and vaccine design.

Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race conditions.

Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race conditions.

Language-specific super-code guidelines for go.

Create and execute Goal-Oriented Action Plans (GOAP) with precondition analysis, cost optimization, and adaptive replanning

Idiomatic Go patterns for error handling, interfaces, concurrency, testing, and module management

> Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when working with Go code to apply idiomatic Go patterns.

Master Go 1.21+ with modern patterns, advanced concurrency, performance optimization, and production-ready microservices.

>- Generates performance-focused guidance for Google Cloud workloads based on the design principles and recommendations in the Performance Optimization pillar of the Google Cloud Well-Architected Framework (WAF). Use this skill to evaluate a workload, identify performance requirements, and provide actionable recommendations for resource allocation, modular design, and elasticity.

Automate Google Search Console tasks via Rube MCP (Composio): search performance, URL inspection, sitemaps, and indexing status. Always search tools first for current schemas.

Automate Google Search Console tasks via Rube MCP (Composio): query search analytics, list sites, inspect URLs, submit sitemaps, monitor search performance. Always search tools first for current schemas.

Problem-solving strategies for gradient methods in optimization

Debug and optimize Android/Gradle build performance. Use when builds are slow, investigating CI/CD performance, analyzing build scans, or identifying compilation bottlenecks.

'Diagnose and fix Grammarly common errors and exceptions. Use when encountering Grammarly errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like \"grammarly error\", \"fix grammarly\", \"grammarly not working\", \"debug grammarly\". '

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

'Follow Grammarly incident response runbook for API outages. Use when Grammarly API is down, experiencing errors, or when investigating service degradation. Trigger with phrases like \"grammarly down\", \"grammarly outage\", \"grammarly incident\", \"grammarly not responding\". '

'Deep dive into Grammarly API migration patterns. Use when migrating between API versions or from deprecated endpoints. Trigger with phrases like \"grammarly migration deep dive\", \"grammarly api migration\", \"grammarly version change\". '

'Optimize Grammarly API performance with caching, batching, and connection pooling. Use when experiencing slow API responses, implementing caching strategies, or optimizing request throughput for Grammarly integrations. Trigger with phrases like \"grammarly performance\", \"optimize grammarly\", \"grammarly latency\", \"grammarly caching\", \"grammarly slow\", \"grammarly batch\". '

'Implement Grammarly reference architecture with best-practice project layout. Use when designing new Grammarly integrations, reviewing project structure, or establishing architecture standards for Grammarly applications. Trigger with phrases like \"grammarly architecture\", \"grammarly best practices\", \"grammarly project structure\", \"how to organize grammarly\", \"grammarly layout\". '

'Apply production-ready Grammarly SDK patterns for TypeScript and Python. Use when implementing Grammarly integrations, refactoring SDK usage, or establishing team coding standards for Grammarly. Trigger with phrases like \"grammarly SDK patterns\", \"grammarly best practices\", \"grammarly code patterns\", \"idiomatic grammarly\". '

'Upgrade and migration guidance for Grammarly API version changes. Use when migrating between Grammarly API versions or updating endpoint references. '

'Create diagnostic bundles for Granola support requests. Use when preparing support tickets, collecting system/audio/network info, or diagnosing complex issues that require Granola support team assistance. Trigger: \"granola debug\", \"granola diagnostics\", \"granola support bundle\", \"granola logs\", \"granola system info\". '

'Incident response procedures for Granola meeting capture failures and outages. Use when meetings aren''t recording, transcription fails mid-meeting, integrations stop syncing, or the Granola service is down. Trigger: \"granola incident\", \"granola outage\", \"granola down\", \"granola not recording\", \"granola emergency\". '

'Migrate to Granola from Otter.ai, Fireflies, Fathom, tl;dv, or manual note-taking. Covers data export from source tools, parallel-run strategy, team transition, and historical data preservation. Trigger: \"migrate to granola\", \"switch to granola\", \"granola from otter\", \"granola from fireflies\", \"replace meeting tool with granola\". '

'Optimize Granola transcription accuracy, note quality, and processing speed. Use when improving transcription quality, reducing processing time, optimizing templates for better AI output, or tuning audio setup. Trigger: \"granola performance\", \"granola accuracy\", \"granola quality\", \"improve granola\", \"granola transcription better\". '

'Enterprise reference architecture for meeting management with Granola. Use when designing org-wide meeting workflows, planning integration topology, or architecting meeting-to-action pipelines across departments. Trigger: \"granola architecture\", \"granola enterprise design\", \"granola system design\", \"meeting system architecture\". '

'Upgrade Granola app versions and migrate between subscription plans. Use when upgrading the desktop app, changing from free to paid plans, downgrading with data preservation, or resolving update issues. Trigger: \"upgrade granola\", \"granola update\", \"change granola plan\", \"granola new version\", \"granola downgrade\". '

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions \"grill me\".

'Diagnose and fix Groq API errors with real error codes and solutions. Use when encountering Groq errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like \"groq error\", \"fix groq\", \"groq not working\", \"debug groq\", \"groq 429\". '

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

'Execute Groq incident response: triage, mitigation, fallback, and postmortem. Use when responding to Groq-related outages, investigating errors, or running post-incident reviews for Groq integration failures. Trigger with phrases like \"groq incident\", \"groq outage\", \"groq down\", \"groq on-call\", \"groq emergency\", \"groq broken\". '

| Use when you are moving a codebase off OpenAI, Anthropic, or another LLM provider onto Groq (or between Groq model generations) and want a zero-downtime, feature-flagged cutover with a benchmark and rollback plan. Trigger with phrases like \"migrate to groq\", \"switch to groq\", \"groq migration\", \"openai to groq\", \"groq replatform\".