golang-production-standards

Enforce production-grade Golang standards with linting and compilation check scripts.

1|Updated Jul 16, 2025
One-click install
npx skills add https://github.com/linskybing/platform-go --skill golang-production-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golang-production-standards
Source: https://github.com/linskybing/platform-go/tree/main/.github/skills/golang-production-standards
Command: npx skills add https://github.com/linskybing/platform-go --skill golang-production-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires go, golangci-lint, bash, and includes scripts (resource) components.

What problem does it solve?

This skill ensures that all Go code in the platform-go project adheres to production-grade standards, reducing defects and improving reliability.

Core Features & Use Cases

  • Standardized coding guidelines: Enforces error handling, context propagation, and concurrency patterns to improve maintainability.
  • Automated quality checks: Provides scripts for linting and compilation checks to catch issues early in PR workflows.
  • Guidance for best practices: Documents repository patterns, testing requirements, and performance targets to guide developers during feature work and code reviews.

Quick Start

  • Run the lint-check.sh script to validate code style and quality.
  • Run the compile-check.sh script to verify that the codebase compiles cleanly.

Frequently Asked Questions about golang-production-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce production-grade Golang standards for code reviews?

To enforce production-grade Golang standards for code reviews, apply standardized coding guidelines for error handling, context propagation, and concurrency, and run automated lint-check scripts to catch defects early.

How do I check if my Go code compiles cleanly and passes linting?

To check if your Go code compiles cleanly and passes linting, execute the compile-check.sh script to verify the build and run the lint-check.sh script using golangci-lint to validate code style and quality.

Do I need golangci-lint and bash to run these Go quality checks?

Yes, you need golangci-lint and bash installed in your environment to execute the provided scripts that automate Go static analysis, linting, and compilation checks for your repository.

What's the best way to standardize error handling and context propagation in Go?

The best way to standardize error handling and context propagation in Go is to codify these patterns into repository guidelines, ensuring maintainability and reliability during feature work, refactoring, and code reviews.

Why does my Go code fail static analysis during refactoring?

Your Go code fails static analysis during refactoring because it violates production-grade standards for concurrency or testing; running the lint-check.sh script identifies specific code quality issues to resolve before PR workflows.