smell-hunter-go

Identifies Go anti-patterns and smells in codebases with actionable feedback.

5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/skyosev/agent-skills --skill smell-hunter-go
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smell-hunter-go
Source: https://github.com/skyosev/agent-skills/tree/main/hunter-party-go/smell-hunter-go
Command: npx skills add https://github.com/skyosev/agent-skills --skill smell-hunter-go

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit Go code for design and maintainability issues by flagging classic smells such as feature envy, data clumps, shotgun surgery, primitive obsession, temporal coupling, comments as deodorant, and init() abuse, enabling targeted refactors.

Core Features & Use Cases

  • Detect Go code smells across packages, including feature envy, data clumps, shotgun surgery, primitive obsession, temporal coupling, and Go-specific antipatterns.
  • Provide guidance on refactoring and clearer domain modeling to improve cohesion and idiomatic Go.
  • Use during code reviews, audits, and maintenance planning to surface root causes and actionable improvements.

Quick Start

Start by running the smell hunter on your Go codebase to surface actionable findings for refactor planning.

Frequently Asked Questions about smell-hunter-go

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

FAQPage Schema
How do I find Go code smells during a code review?

You can detect Go code smells by analyzing packages for feature envy, data clumps, and primitive obsession. The audit provides actionable guidance with precise file:line evidence, avoiding non-idiomatic missteps and generic SOLID critiques.

What are common Go antipatterns and code smells?

Common Go code smells include feature envy, data clumps, shotgun surgery, primitive obsession, temporal coupling, comments as deodorant, and init() abuse. Identifying these antipatterns helps surface root design problems and improve domain modeling.

How do I plan refactoring for Go code with maintainability issues?

Plan refactoring for Go code by auditing for smells like primitive obsession and temporal coupling. This surfaces root causes and actionable improvements, enabling targeted refactors that improve cohesion and idiomatic Go.

Does this Go audit tool check for SOLID design principle violations?

No, this Go audit explicitly avoids SOLID critiques and non-Go-idiom missteps. It focuses entirely on detecting classic Go code smells and antipatterns to provide idiomatic, actionable refactoring guidance.

Can I detect shotgun surgery and data clumps across Go packages?

Yes, you can detect shotgun surgery and data clumps across Go packages. The audit identifies these and other structural smells, providing precise file:line evidence to guide targeted refactoring and improve cohesion.