tooling-go

Run and aggregate Go security, quality, and vulnerability tooling audits.

Updated May 5, 2026
One-click install
npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill tooling-go
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tooling-go
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/sdlc-audit/skills/tooling-go
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill tooling-go

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Go audit tooling consolidates leading static analysis and security checks for Go projects, reducing manual setup and drift across audit phases.

Core Features & Use Cases

  • Comprehensive Analysis Suite: Integrates golangci-lint, gosec, govulncheck, staticcheck, gocyclo, deadcode, go-mutesting, and Nancy for end-to-end quality and security evaluation.
  • Vulnerability & Quality Insights: Detects CVEs, code smells, dead code, and mutation opportunities to strengthen Go codebases.
  • Use Case: When auditing a Go repository, run this tooling to surface security gaps, complexity hotspots, and maintenance risks in a single pass.

Quick Start

Run the tooling against a Go project to surface vulnerabilities and code-quality issues.

Frequently Asked Questions about tooling-go

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

FAQPage Schema
How do I automate Go project auditing with multiple static analysis tools?

Automate Go project auditing by running and aggregating security, quality, and vulnerability tooling in a single pass. This consolidates golangci-lint, gosec, govulncheck, staticcheck, deadcode, gocyclo, go-mutesting, and Nancy to detect vulnerabilities, code smells, and performance concerns.

What is the best way to detect CVEs and code smells in a Go repository?

Detect CVEs and code smells in a Go repository by running integrated security and quality tooling. This suite surfaces vulnerability insights, complexity hotspots, dead code, and mutation opportunities to strengthen your codebase during audit phases.

Can I run golangci-lint and gosec together for comprehensive Go code quality analysis?

Yes, you can run golangci-lint and gosec together with govulncheck, staticcheck, and other tools for comprehensive Go code quality analysis. The toolchain integrates these tools to provide structured outputs for review across varying repository sizes.

Does this Go audit tooling work on repositories of varying sizes?

Yes, this Go audit tooling works on repositories of varying sizes during audit phases. It applies integrated static analysis and security checks to detect vulnerabilities, code smells, dead code, and performance concerns regardless of project scale.

How do I get structured outputs from govulncheck and staticcheck for review?

Get structured outputs from govulncheck and staticcheck by running the integrated Go audit toolchain. It aggregates results from multiple security and quality tools into structured outputs, reducing manual setup and drift across audit phases.

Why use an integrated Go toolchain instead of running static analysis tools separately?

Use an integrated Go toolchain to reduce manual setup and configuration drift across audit phases. Running tools separately risks inconsistent results, while this approach consolidates security, quality, and vulnerability checks into a single structured output.