Semantic code analysis with GitLab Knowledge Graph. Use for go-to-definition, find-usages, impact analysis, architecture visualization.
GitLab CLI (glab) for merge requests, issues, and CI/CD pipelines. Use when working with GitLab repositories for MR creation/review, issue management, pipeline debugging, or any…
Use when writing or reviewing Gleam code on the Erlang target — especially Wisp + Mist HTTP services, OTP-based processes (gen_server / supervisor analogues), justfile workflows,…
Use GliderMCP for C#/.NET navigation, diagnostics, references, call graphs, impact analysis, and safe refactoring.
GlitchTip is an open-source, Sentry-compatible error tracking platform built for self-hosted exception monitoring and alerting.
> Pattern library for cloud, infrastructure, and developer tool vendors that appear on bank statements and ledger detail worldwide.
code-reviewer 에이전트를 통해 코드 품질과 아키텍처를 검사하는 스킬. 레이어 경계 검증, 통신 패턴 검사, 코드 품질 이슈 식별. 특정 파일/디렉토리 경로를 지정하거나 인자 없이 현재 브랜치 변경 파일 자동 감지.
Implementation guide for Global Privacy Control (GPC) automated opt-out signal per CPRA Section 1798.135(e).
Revisão completa de segurança, arquitetura, performance e padronização para projetos em Rust. Use esta skill sempre que o usuário pedir para revisar, auditar, analisar a qualidade…
Runtime GLB/GLTF inspection — traverse nodes, identify screen meshes, inspect UV coordinates, material property dumping, fixing exported materials at runtime.
Expert Garry's Mod Lua (GLua) development with accurate GMod API signatures, client/server/menu realms, hooks, VGUI/derma panels, meta-table classes, enumerations and asset paths…
Gluegun CLI toolkit patterns for TypeScript-powered command-line apps. Use when building CLI tools, creating command structures, implementing template systems, filesystem…
Use when (1) building mobile app via EAS for distribution, (2) submitting to App Store or Google Play, (3) managing mobile release workflow.
Use when (1) deploying web application to Vercel staging or production, (2) monitoring deployment progress, (3) running post-deployment verification.
Use when (1) preparing a release for staging or production, (2) generating release notes and changelog, (3) verifying environment readiness before deployment.
GMailArchiver architecture, layer patterns, and component design. Use when working with cli, core, data, connectors, or shared layers, or understanding component dependencies.
Trade perpetuals and swap tokens on GMX V2 — a decentralized exchange with oracle-based pricing on Arbitrum, Avalanche, and Botanix.
Diagnose Chromium GN dependency and include-visibility failures, including BUILD.gn deps/public_deps, DEPS include rules, private headers, and circular dependencies.
gnomAD v4 population variant frequencies via GraphQL API. Allele counts and frequencies stratified by ancestry (AFR, AMR, EAS, NFE, SAS, FIN, ASJ, MID), gene-level constraint…
Submit compact gnomAD GraphQL requests for frequency, gene constraint, and variant context queries. Use when a user wants concise gnomAD summaries — from…
Opens the running app in a browser and verifies recent UI changes actually work. Use whenever the user wants a quick smoke test or sanity check of recent work, or says "go", "open…
REST and gRPC API design patterns for Go services. Covers HTTP handlers, middleware, routing, request/response patterns, versioning, pagination, graceful shutdown, and OpenAPI…
WHEN: Go API review with Gin/Echo/Fiber/Chi, router patterns, middleware, request handling WHAT: Router organization + Middleware patterns + Request validation + Error responses +…
Use when asked to measure, introduce, or improve Go project architecture quality. Applies modularity (coupling/cohesion) and testability (cognitive complexity, cyclomatic…
Designs implementation architecture following hexagonal patterns, produces TASKS.md and individual task-N.md files for the orchestrator to execute using red-green TDD.
Structure Go 1.22+ services — standard cmd/internal layout, constructor-based dependency injection, HTTP routing (net/http ServeMux vs chi vs echo/gin/fiber), and type-safe…
Review Go project architecture: package structure, dependency direction, layering, separation of concerns, domain modeling, and module boundaries.
Go backend development best practices for microservices with clean architecture, observability, and production-ready patterns
Go benchmarking methodology knowledge — testing.B API, benchstat comparison, sub-benchmarks, profile capture (-cpuprofile/-memprofile/-trace), reading output, dead-code…
Bootstraps a new Go project from scratch with hexagonal architecture, testcontainers, CI pipeline, and the full skill/agent suite installed.
Go CI/CD 工具配置：Makefile、golangci-lint、GitHub Actions、Docker、測試覆蓋率、 自動化流程、Pre-commit Hook。
Use when creating or refactoring GitHub Actions CI workflows for Go repositories. Covers repository-shape detection, Make-driven delegation with formal fallbacks, Go setup,…
Go code generation and TDD assistant. Use when writing new Go logic or updating existing features to ensure idiomatic code and comprehensive unit testing.
Review Go code in this project against the standard quality bar — formatting, vet, idiomatic style, error handling, concurrency, and testing.
Comprehensive code review checklist for Go projects. Evaluates code quality, idiomatic patterns, error handling, naming, package structure, and test coverage.
Review Go code with a defect-first approach using repository policy (constitution.md first, then AGENTS.md fallback).
Go coding standards and style conventions grounded in Effective Go, Go Code Review Comments, and production-proven idioms.
Développement Go avec focus sur la concurrence et les patterns idiomatiques. Se déclenche avec "Go", "Golang", "goroutine", "channel", "sync", "concurrency", "Go modules" — from…
Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race — from…
Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race — from…
Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race — from…
Review and implement safe concurrency patterns in Go: goroutines, channels, sync primitives, context propagation, and goroutine lifecycle management.
Data persistence patterns in Go covering raw SQL with sqlx/pgx, ORMs like Ent and GORM, connection pooling, migrations with golang-migrate, and transaction management.
Debug Go failures by reproducing the bug as a focused test, tracing root cause, fixing minimally, and verifying with race-enabled tests.
Idiomatic Go design patterns: functional options, builder, factory, strategy, middleware chain, pub/sub, and other patterns adapted for Go's type system.
Instructions for writing Go code following idiomatic Go practices and community standards. Use this when writing or reviewing any code written in Go (Golang).
Go documentation conventions — a doc comment on every exported function, struct, type, and package, package comments in a dedicated doc.go for multi-file packages, godoc style…
Go error handling patterns, wrapping, sentinel errors, custom error types, and the errors package. Grounded in Effective Go, Go Code Review Comments, and production-proven idioms.
Specialized knowledge for writing professional, idiomatic Go (Golang) code, specifically for the switchAILocal codebase (Gin, switchai, etc.).
Use when writing, refactoring, reviewing, or testing ANY Go code. The canonical reference for Go conventions — project taxonomy (CLI Only / Web Only / CLI + Web / Headless API…
Expertise in Go programming according to the Google Go Best Practices. Focuses on actionable advice for naming, error handling, performance, testing, and general idiomatic Go to…
gRPC Go knowledge — service/stream types, interceptors, status codes, deadline propagation, TLS/mTLS, bufconn testing, common pitfalls.
Idiomatic Go patterns for errors, interfaces, concurrency, and packages. Use when: - Writing or reviewing Go code - Designing interfaces or package structure - Implementing…
Provides reusable guidance for implementing and reviewing idiomatic Go code, with emphasis on clarity, simplicity, and maintainability across naming, error handling, control flow,…
Tests de integración en Go. Usar al testear múltiples componentes juntos o validar flujos end-to-end.
Go interface design patterns: implicit interfaces, consumer-side definition, interface compliance verification, composition, the accept-interfaces-return-structs principle, and…
Scaffolds reusable Go 1.26 library modules in the ralvarezdev DDD + hexagonal house style — domain-pure root package, ports as narrow interfaces, technology-named adapter…
Run golangci-lint to check Go code quality. Use when the user asks to lint, check for lint issues, or verify code quality in a Go project, or when linting is appropriate before…
WHEN: User wants to run linting on their Go project, understand lint findings, improve their golangci-lint configuration, or asks "what's wrong with my code?" from a linting…
Run golangci-lint and fix all reported issues. Use only when explicitly asked to fix lint issues in a Go project.