type-hunter-go

Audit Go type definitions for design debt and duplication.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit Go type definitions for design debt. It identifies duplicated struct shapes, misused generics, under-constrained type parameters, embedding antipatterns, poor enum patterns, and disorganized type architecture, enabling teams to improve maintainability.

Core Features & Use Cases

  • Identify type duplication across packages and derive a canonical source type to reduce maintenance burden.
  • Detect embedding antipatterns and guidance on explicit delegation to constrain API surface.
  • Highlight under-constrained generics and recommend tighter constraints to improve code safety and readability.
  • Provide actionable migration paths to reorganize type architecture after growth and refactoring.

Quick Start

Run a design-review pass over your Go types to surface duplicates, generics misuse, and embedding antipatterns.

Frequently Asked Questions about type-hunter-go

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

FAQPage Schema
How do I audit Go type definitions for design debt?

Audit Go type definitions by running a design-review pass to surface duplicated struct shapes, misused generics, and embedding antipatterns. This enforces evaluation of composition practices, generic constraints, and embedding usage to improve maintainability across large codebases.

What are common Go generics antipatterns and under-constrained type parameters?

Under-constrained type parameters in Go generics reduce code safety and readability. Auditing detects these antipatterns and recommends tighter constraints to ensure type parameters are properly bounded, preventing over-engineering and improving maintainability.

How do I find duplicated struct shapes across Go packages?

Reviewing Go type architecture identifies duplicated struct shapes across packages and derives a canonical source type. This reduces maintenance burden by consolidating redundant definitions during frequent refactoring and codebase evolution.

When should I use explicit delegation instead of struct embedding in Go?

Use explicit delegation instead of struct embedding when embedding antipatterns risk exposing an uncontrolled API surface. Auditing detects these cases and provides guidance on constraining the API surface to maintain clean type architecture.

Can this type audit handle large Go codebases with evolving type hierarchies?

Yes, the audit targets large Go codebases with many packages, evolving type hierarchies, and frequent refactoring. It provides actionable migration paths to reorganize type architecture after growth, addressing duplication and over-engineering that creep in.

What is the best way to reorganize poor Go enum patterns and type architecture?

The best way is to audit for disorganized type architecture and poor enum patterns, then follow the provided actionable migration paths. This reorganization process constrains API surface and improves maintainability after codebase growth.