lint

Run golangci-lint static analysis on Go projects with .golangci.yml configurations.

23|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/PeterBooker/veloria --skill lint-peterbooker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/PeterBooker/veloria/tree/main/.claude/skills/lint
Command: npx skills add https://github.com/PeterBooker/veloria --skill lint-peterbooker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of checking Go code quality and identifying potential issues before they reach the CI pipeline or production.

Core Features & Use Cases

  • Static Analysis: Runs golangci-lint to perform comprehensive static analysis on your Go codebase.
  • Code Quality Checks: Catches common programming errors, style violations, and security vulnerabilities.
  • Use Case: Before committing your changes, run /lint ./internal/ to ensure all internal packages adhere to project coding standards and are free of obvious errors.

Quick Start

Run the lint skill on all packages in the current directory.

Frequently Asked Questions about lint

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

FAQPage Schema
How do I run static analysis on Go code to check for programming errors?

To run static analysis on Go code, execute golangci-lint to catch common programming errors, style violations, and security vulnerabilities. This Skill automates the process and identifies potential issues before they reach the CI pipeline.

Can I lint specific packages in my Go project instead of the entire codebase?

Yes, you can lint specific packages in your Go project by passing the package path, such as `/lint ./internal/`. This ensures only targeted directories are checked against project coding standards and are free of obvious errors.

Does golangci-lint support auto-fixing issues found during code quality checks?

Yes, golangci-lint supports options for auto-fixing issues found during code quality checks. This allows developers to automatically resolve common style violations and programming errors detected during static analysis.

How does golangci-lint integrate with existing CI configurations?

golangci-lint integrates with existing CI configurations by reading project-defined settings from the .golangci.yml file. This ensures local static analysis aligns with the CI pipeline without requiring separate linting rules.

What is the best way to ensure Go code quality before committing changes?

The best way to ensure Go code quality before committing is to run golangci-lint for comprehensive static analysis. This catches security vulnerabilities and style violations early, preventing potential issues from reaching production.

Why should I use golangci-lint instead of other static analysis tools for Go?

You should use golangci-lint because it runs multiple linters concurrently for comprehensive code quality checks. It catches common programming errors and security vulnerabilities while aligning with your CI pipeline via .golangci.yml.