Skip to content
TrustedSkillsbeta
Back to all skills

Go Linting

Checked
cxuu·vlatest·backend·Apache-2.0

Identifies potential code errors and style issues in various programming languages using cxuu's go-linting tool.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add cxuu/golang-skills --skill go-linting -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

cxuu

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned cxuu/golang-skills at 91f0c2eef5.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
91f0c2eef5
Manifest
skills/go-linting/SKILL.md
Scanned
3 files, 395 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to identify potential errors and style issues in Go code using golangci-lint. It leverages a configurable set of linters to enforce consistent coding standards, catch common mistakes, and improve overall code quality. The tool prioritizes consistency over strict adherence to any single linter's ruleset.

When to use it

  • When ensuring code adheres to project style guidelines.
  • Before committing code changes to a repository.
  • As part of an automated CI/CD pipeline for continuous code analysis.
  • To identify and address potential security vulnerabilities in Go applications (with the gosec linter).
  • When refactoring existing Go codebases to improve maintainability.

Key capabilities

  • Runs a suite of linters including errcheck, goimports, revive, govet, and staticcheck.
  • Supports configuration via .golangci.yml files, allowing customization of enabled linters and their settings.
  • Provides guidance on resolving linting errors category by category (formatting, vet, then style).
  • Includes example configurations for common scenarios.
  • Offers recommendations for additional linters to enhance code quality and security.

Example prompts

  • "Run the Go linter on this file: main.go."
  • "Analyze the entire project directory for linting issues."
  • "Check if these changes introduce any new linting errors."

Tips & gotchas

  • A .golangci.yml configuration file is required in the project root. The skill provides an example to use as a baseline.
  • When suppressing linting warnings using //nolint, always include a justification for why the warning is being ignored.
  • For optimal results, run linters consistently across the entire codebase.