lint-fix-go

Automate golangci-lint fixes for whitespace, naming, and logic in Go code.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/CaptainPhantasy/floyd-v5 --skill lint-fix-go
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-fix-go
Source: https://github.com/CaptainPhantasy/floyd-v5/tree/main/extensibility/skills/linting/lint-fix-go
Command: npx skills add https://github.com/CaptainPhantasy/floyd-v5 --skill lint-fix-go

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Golangci-lint warnings often require repetitive, manual fixes; this skill automates fixes for whitespace, naming, and simple logic adjustments in Go code.

Core Features & Use Cases

  • Analyze golangci-lint output and apply fixes for common issues in Go code.
  • Normalize whitespace, enforce naming conventions, and adjust simple logic to satisfy lint rules.
  • Use in CI pipelines to reduce PR review time by automatically correcting routine issues in Go projects.

Quick Start

Run lint-fix-go on your Go project to automatically apply fixes suggested by golangci-lint.

Frequently Asked Questions about lint-fix-go

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

FAQPage Schema
How do I auto-fix golangci-lint issues in Go code?

You can auto-fix golangci-lint issues in Go code by parsing linter results and applying in-place changes to normalize whitespace, enforce naming conventions, and adjust simple logic.

What routine golangci-lint warnings can I automatically fix in Go projects?

You can automatically fix routine golangci-lint warnings for whitespace inconsistencies, naming convention violations, and simple logic adjustments in Go source files.

Can I use an automated linter fix tool in my Go CI pipelines?

Yes, you can use an automated linter fix tool in Go CI pipelines to automatically correct routine issues, which reduces PR review time by handling repetitive manual fixes.

Does automated golangci-lint fixing change the behavior of my Go code?

Automated golangci-lint fixing operates on Go source files by applying in-place changes that specifically preserve behavior while adjusting whitespace, naming, and simple logic.

What is the best way to handle repetitive golangci-lint naming and whitespace fixes?

The best way to handle repetitive golangci-lint naming and whitespace fixes is to automate the adjustments, applying in-place changes to Go source files based on parsed linter results.

Do I need to manually resolve all golangci-lint warnings for simple logic adjustments?

No, you do not need to manually resolve all simple logic adjustments; you can automate the application of these fixes to satisfy lint rules while preserving code behavior.