dlexa-go-cli-lint

Run the repo-local golangci-lint workflow on dlexa CLI Go code.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Disble/dlexa --skill dlexa-go-cli-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dlexa-go-cli-lint
Source: https://github.com/Disble/dlexa/tree/main/.claude/skills/dlexa-go-cli-lint
Command: npx skills add https://github.com/Disble/dlexa --skill dlexa-go-cli-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automatically run and interpret the repo-local Go lint workflow to ensure code quality and adherence to project standards in the dlexa CLI repository.

Core Features & Use Cases

  • Runs the repo-local golangci-lint configuration against the repository or targeted packages without requiring a global tool.
  • Produces actionable lint results and guidance to improve code quality and consistency across cmd/ and internal/ packages.
  • Use Case: When touching Go code, run the lint workflow to surface findings before commits and reviews.

Quick Start

Run the repo-local lint workflow on the dlexa CLI project to surface static analysis issues and suggested fixes.

Frequently Asked Questions about dlexa-go-cli-lint

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

FAQPage Schema
How do I run golangci-lint on specific Go packages without a global installation?

You can run golangci-lint on specific Go packages using a mod-scoped invocation that applies the repo-local configuration, eliminating the need for a global tool installation while enforcing project lint rules across cmd/ and internal/ packages.

What Go static analysis issues can I catch before committing code changes?

Running a Go static analysis lint workflow surfaces code quality and consistency issues across cmd/, internal/, and test files before commits, providing actionable feedback and suggested fixes based on the repo-local golangci-lint configuration.

Does this lint workflow require a pre-configured golangci-lint file to work?

Yes, the lint workflow requires the repo-local golangci-lint configuration to define project lint rules. It uses this file to deliver deterministic static analysis feedback on Go code changes without requiring external setup.

How do I interpret golangci-lint results for Go code reviews?

Interpreting golangci-lint results involves reading the actionable lint findings produced by the workflow, which highlights static analysis issues and provides guidance to improve code quality and consistency for Go code reviews.

Can I use this to lint Go tests and internal packages?

Yes, the lint workflow applies to changes across the internal/ packages and tests, running the repo-local golangci-lint configuration to report static analysis issues and ensure project standards are met.