Hunt down Go interface implementations like a bloodhound with trust issues.

Tired of grep-ing through thousands of lines trying to figure out which structs actually implement that damn interface? This tool does the heavy lifting so you don't have to suffer through another existential crisis at 3am.

go install github.com/psyb0t/gofindimpl@latest

go run github.com/psyb0t/gofindimpl@latest \
  -interface ./path/to/file.go:InterfaceName \
  -dir ./search/directory

git clone https://github.com/psyb0t/gofindimpl.git
cd gofindimpl
go build -o gofindimpl

gofindimpl \
  -interface ./path/to/file.go:InterfaceName \
  -dir ./search/directory

go run github.com/psyb0t/gofindimpl@latest \
  -interface ./path/to/file.go:InterfaceName \
  -dir ./search/directory

gofindimpl -interface ./internal/app/server.go:Server -dir ./internal/pkg/

go run github.com/psyb0t/gofindimpl@latest \
  -interface ./internal/app/server.go:Ser
95A6
ver \
  -dir ./internal/pkg/

# Installed
gofindimpl \
  -interface ./internal/app/server.go:Server \
  -dir ./internal/pkg/ \
  -debug

# Direct run  
go run github.com/psyb0t/gofindimpl@latest \
  -interface ./internal/app/server.go:Server \
  -dir ./internal/pkg/ \
  -debug

JSON, because XML is for people who hate themselves:

[
  {
    "package": "impl",
    "struct": "WebServer",
    "packagePath": "github.com/yourproject/internal/pkg/impl"
  },
  {
    "package": "mock",
    "struct": "MockServer",
    "packagePath": "github.com/yourproject/internal/pkg/mock"
  }
]

1. Parse Interface: Reads the specified Go file and extracts interface methods
2. Scan Directory: Recursively walks through Go files (skips test files because reasons)
3. Type Check: Uses Go's type checker to validate method signatures
4. Match Methods: Finds structs that implement all interface methods
5. Output Results: Spits out JSON with implementation details

• Go 1.24+: Because living in the past is for historians
• go.mod: Must run from a proper Go module root (not some anarchist directory)
• Valid Go Code: Broken syntax makes this tool cry

• Method Set Analysis: Checks both value and pointer receiver methods
• Recursive Search: Crawls directories like a determined spider
• Type Safety: Uses Go's actual type checker instead of regex nightmares
• Package Filtering: Skips vendor directories and hidden folders automatically
• Error Handling: Fails gracefully instead of exploding in your face
• Debug Mode: For when things go sideways and you need to know why

The tool will tell you exactly what's wrong instead of leaving you guessing:

• Interface file not found: Check your file path
• Interface not found in file: Make sure the interface name exists
• No go.mod found: Run from a proper Go module root
• Directory not found: Search directory doesn't exist
• Parse errors: Fix your Go syntax first

Current coverage: 90.8%

Because untested code is like unprotected... well, you get it.

MIT - because pkg.go.dev are corporate fuckers who won't index WTFPL packages.