One-click install
npx skills add https://github.com/zajca/zfaktury --skill go-code-review-zajca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-code-review
Source: https://github.com/zajca/zfaktury/tree/main/.agents/skills/go-code-review
Command: npx skills add https://github.com/zajca/zfaktury --skill go-code-review-zajca

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers ensure their Go code adheres to community best practices and common style guidelines, reducing bugs and improving maintainability.

Core Features & Use Cases

  • Checklist-based Review: Provides a comprehensive checklist covering formatting, documentation, error handling, naming, concurrency, interfaces, and more.
  • Reference to Detailed Skills: Each checklist item links to more in-depth explanations and guidance.
  • Quick Review Commands: Includes handy commands for formatting and linting.
  • Use Case: Before committing a new Go feature, use this Skill to quickly verify adherence to standard Go idioms and catch common mistakes.

Quick Start

Use the go-code-review skill to check the Go code for common style and best practice violations.

Frequently Asked Questions about go-code-review

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

FAQPage Schema
How do I review Go code against community standards and best practices?

Reviewing Go code against community standards involves using a comprehensive checklist covering formatting, documentation, error handling, naming, concurrency, interfaces, data structures, security, style, imports, and testing to ensure adherence to Go Wiki CodeReviewComments.

What should a Go code review checklist include to catch common mistakes?

A Go code review checklist should include formatting, documentation, error handling, naming, concurrency, interfaces, data structures, security, style, imports, and testing. Each checklist item must link to detailed explanations to facilitate adherence to standard idioms.

How do I check my Golang feature for standard idioms before committing?

Checking a Golang feature before committing involves using a review skill to quickly verify adherence to standard Go idioms and catch common mistakes against community style guidelines and best practices.

What is the best way to enforce Golang style guide and linting rules?

Enforcing Golang style guide and linting rules is best achieved by applying a checklist-based review process alongside handy formatting and linting commands to identify common violations and improve code maintainability.

Does Go code review cover concurrency and interface design best practices?

Yes, Go code review covers concurrency and interface design best practices. The review checklist explicitly includes these areas alongside error handling and data structures to ensure comprehensive adherence to community standards.

Why does my Go code review need to reference Go Wiki CodeReviewComments?

Referencing Go Wiki CodeReviewComments during a Go code review provides established community standards for formatting and error handling. This reference reduces bugs and improves overall code quality and maintainability.