boundary-hunter-go

Audit Go package exports and imports for boundary violations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Go packages often leak internals through their public API, creating brittle boundaries. boundary-hunter-go helps identify and enforce clean package boundaries to keep code maintainable and replaceable.

Core Features & Use Cases

  • Detect over-exported symbols and API surface boundaries that reveal implementation details.
  • Flag dependency-direction violations, internal/ boundary breaches, and deep import paths.
  • Produce a prioritized report to guide refactors and encapsulation improvements.

Quick Start

Run a boundary audit across the codebase to surface violations and actionable fixes.

Frequently Asked Questions about boundary-hunter-go

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

FAQPage Schema
How do I audit Go package boundaries for internal implementation leaks?

To audit Go package boundaries, analyze exported APIs for leaks of implementation details and improper coupling across defined layers. This process flags over-exported symbols and internal boundary breaches, producing a structured report to guide refactoring and encapsulation improvements.

What is a deep import path violation in Go architecture?

A deep import path violation in Go architecture occurs when packages improperly access deeply nested internal paths across defined boundaries. Auditing inspects the dependency graph to flag these deep import paths, preventing brittle boundaries and maintaining package replaceability.

How do I detect import cycles and dependency direction violations in Go packages?

Detect import cycles and dependency direction violations by inspecting packages' exports, imports, and the dependency graph. The analysis flags improper coupling across layered architectures, ensuring internal exposure is strictly controlled and boundary violations are measured.

Can I use a boundary audit on Go codebases with layered architectures?

Yes, boundary auditing is applicable to Go codebases with layered architectures where packages interact across defined boundaries. It specifically checks that internal exposure is controlled, identifying directional dependency issues and over-exported API surfaces.

What's the best way to enforce clean Go package boundaries and reduce over-exported symbols?

The best way to enforce clean Go package boundaries is running a comprehensive audit to identify and measure over-exported symbols and API surface leaks. This generates a prioritized report to direct refactoring efforts and encapsulation improvements.