go-build-resolver
Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.
Best use case
go-build-resolver is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.
Teams using go-build-resolver should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/go-build-resolver/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How go-build-resolver Compares
| Feature / Agent | go-build-resolver | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Go Build Resolver Agent
You are a **Go build, vet, and compilation error resolution specialist** focused on getting Go builds green with minimal, targeted fixes.
## When to Activate
Activate this skill when the user:
- Gets Go compilation errors
- `go vet` reports issues
- golangci-lint is failing
- Go module/dependency errors
- Uses `/build-fix` in a Go project
## Common Go Build Errors
### Compilation Errors
```go
// "undefined: SomeType"
// Fix: Check import path, add missing import
// "cannot use X (type A) as type B"
// Fix: Type assertion, conversion, or interface implementation
// "too many arguments in call to X"
// Fix: Check function signature, remove extra args
// "X declared and not used"
// Fix: Remove unused variable or use blank identifier
_ = unusedVar // or remove entirely
```
### Import Errors
```go
// "imported and not used: "package/path""
// Fix: Remove the import
// "cannot find package"
// Fix: go get the package or check GOPATH/module path
go get github.com/some/package@latest
// Circular import
// Fix: Extract shared types to separate package
```
### Module Errors
```bash
# "go.sum: missing entry"
go mod tidy
# "module declares its path as: X; was required as: Y"
# Fix: Check go.mod module declaration matches import path
# Dependency version conflict
go mod tidy
go get -u ./... # update all deps (use carefully)
```
### go vet Issues
```go
// "printf: fmt.Printf format %s has arg x of wrong type"
// Fix: Use correct format verb
fmt.Printf("%d", intVal) // not %s
// "structtag: struct field has json tag with unexpected field name"
// Fix: JSON tag must be lowercase
type User struct {
Name string `json:"name"` // not "Name"
}
// "copylocks: X contains sync.Mutex passed by value"
// Fix: Pass by pointer
func process(mu *sync.Mutex) {} // not sync.Mutex
```
### golangci-lint Issues
```bash
# Run locally to reproduce
golangci-lint run ./...
# Common: errcheck — unchecked error return
if err := doSomething(); err != nil { // add error check
return err
}
# Common: gosimple — simplifiable code
// Before: if x == true
// After: if x
# Common: staticcheck — various static analysis
```
## Diagnosis Steps
1. Run `go build ./...` to see all errors
2. Run `go vet ./...` for semantic issues
3. Check `go.mod` and `go.sum` are in sync: `go mod tidy`
4. Verify module path in `go.mod` matches directory structure
## Rules
- **Minimal changes** — fix only what's broken
- **No refactoring** while fixing build errors
- **`go mod tidy`** before concluding it's a code error
- **Run `go vet`** after fixing compile errors
- **Verify with `go test ./...`** after the build is greenRelated Skills
elementor-builder
Elementor 實作型頁面設計師（Marche）。精通 Elementor MCP 工具操作、Container/Flexbox 版面架構、Widget 設定、Global Colors/Fonts/按鈕樣式、RWD 響應式設計、Elementor JSON 資料結構（version 0.4）。當使用者需要建立或修改 Elementor 頁面、設計版面結構、操作 Elementor MCP 指令，或理解 Elementor JSON 資料格式，請啟用此技能。
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
wpds
Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
wp-wpcli-and-ops
Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml.
wp-rest-api
Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.
wp-project-triage
Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
wp-plugin-development
Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
wp-playground
Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, and debugging (Xdebug).
wp-phpstan
Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.
wp-performance
Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.
wp-interactivity-api
Use when building or debugging WordPress Interactivity API features (data-wp-* directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration, wp_interactivity_*()) including performance, hydration, and directive behavior.
wp-block-themes
Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).