Implement and review Go gRPC services with proto structure and error semantics.
npx skills add https://github.com/dmwin72015/netdisk --skill golang-grpc-dmwin72015
Please help me install this Agent Skill. Skill: golang-grpc Source: https://github.com/dmwin72015/netdisk/tree/main/.agents/skills/golang-grpc Command: npx skills add https://github.com/dmwin72015/netdisk --skill golang-grpc-dmwin72015
It prevents common Go gRPC mistakes that cause opaque errors, broken retry behavior, missing health signals, and fragile production operations.
proto/*/<domain>/v1/ layout and wrapper Request/Response messaging to keep APIs evolvable.Ask the agent to review your Go gRPC server implementation for status code correctness, deadlines, interceptors, health registration, and graceful shutdown, and then propose concrete code changes.
High-intent search queries and answers about installing and using this skill.
Graceful shutdown in a Go gRPC server requires calling GracefulStop with a timeout fallback to ensure in-flight RPCs complete or abort safely. This prevents broken connections and data loss during microservice deployments.
To return proper gRPC status codes in Go microservices, use status.Error and status.Errorf with specific gRPC codes instead of standard Go errors. This ensures correct error semantics, transparent client retry behavior, and reliable service communication.
Correct proto organization for versioned gRPC APIs uses a domain-based, versioned layout like proto/*/<domain>/v1/ with wrapper Request and Response messages. This structure keeps your APIs evolvable and maintainable as your microservices scale.
Setting up gRPC health checks and interceptors in a Go server involves explicit health check registration and applying interceptor patterns to the server configuration. These operationally sound defaults provide necessary health signals for Kubernetes and production monitoring.
Broken retry behavior and opaque errors in gRPC clients usually occur when the server returns standard Go errors instead of using status.Error with specific gRPC status codes. Implementing per-call deadlines and correct error semantics resolves these reliability issues.
Disabling gRPC reflection is a production security default for operationally sound Go gRPC servers. Combined with TLS configuration and connection reuse, it prevents unauthorized API discovery and secures your microservices against external probing.
muratmirgunDesign and harden Go gRPC services with versioned proto contracts and secure transport.
doanchienthangdevExplain service discovery patterns with Kubernetes and Consul examples.
ashchupliakDefine protobuf services and implement gRPC streaming RPCs with interceptors.
robotijnValidate API implementations against OpenAPI, AsyncAPI, GraphQL, and Protobuf contracts.