solid-hunter-go

Identify SOLID design-principle violations in Go packages and dependencies.

5|Updated Jan 14, 2026

Search Tags:#architecture #refactoring #go #lsp #code-quality #solid #dependency-inversion

Ready to run

npx skills add https://github.com/skyosev/agent-skills --skill solid-hunter-go

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: solid-hunter-go
Source: https://github.com/skyosev/agent-skills/tree/main/hunter-party-go/solid-hunter-go
Command: npx skills add https://github.com/skyosev/agent-skills --skill solid-hunter-go

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit Go code for design principle violations — god packages, rigid extension points, broken interface contracts, fat interfaces, and concrete dependency chains. Adapted from SOLID for Go's composition-over-inheritance model.

Core Features & Use Cases

Assess package-level responsibilities and identify god structs or overly broad packages.
Detect rigid extension points and opportunities to introduce interfaces and composition.
Highlight potential DIP violations and opportunities to depend on abstractions to improve testability.

Quick Start

Run an initial SOLID scan of a Go module to surface high-priority improvements for client-facing packages.

Frequently Asked Questions about solid-hunter-go

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

FAQPage Schema

How do I audit Go code for SOLID design principle violations?▼

To audit Go code for SOLID violations, analyze packages, structs, interfaces, and constructors to surface SRP, OCP, LSP, ISP, and DIP issues like god packages, rigid extension points, and concrete dependency chains.

What is a god package in Go and how do I detect it?▼

A god package in Go is an overly broad package lacking cohesive responsibilities. You can detect it by assessing package-level responsibilities to identify god structs and high-priority improvements for client-facing modules.

How do I find rigid extension points and fat interfaces in a Go module?▼

Find rigid extension points and fat interfaces in a Go module by analyzing interface contracts and struct dependencies to highlight broken segregation and opportunities to introduce composition.

Can I check my Go code for Dependency Inversion Principle violations to improve testability?▼

Yes, you can check Go code for Dependency Inversion Principle violations by tracing concrete dependency chains and highlighting opportunities to depend on abstractions to improve testability.

Does this SOLID analysis approach work with Go's composition-over-inheritance model?▼

Yes, this SOLID analysis works with Go's composition-over-inheritance model by adapting traditional design principles to detect rigid extension points and identify opportunities to introduce interfaces and composition.