gopls-lsp

What This Skill Does

The gopls-lsp skill provides a sophisticated interface for the official Go language server (gopls), enabling deep code intelligence directly within the OpenClaw environment. By integrating this skill, the agent gains the ability to parse Go source code, providing context-aware autocomplete, accurate go-to-definition navigation, and precise symbol references. It acts as the backbone for maintaining high-quality Go codebases, offering real-time diagnostics that identify compilation errors, syntax issues, and potential bugs before they reach the execution phase. Beyond basic navigation, this skill facilitates advanced code refactoring, such as renaming symbols across a workspace, organizing imports, and detecting unused code blocks, significantly accelerating development workflows for Go developers.

Installation

To integrate this skill, first ensure the Go toolchain is installed on your system. Run the command go install golang.org/x/tools/gopls@latest to fetch the latest binary. Verify that your system's $PATH includes the directory where the binary was installed, typically $GOPATH/bin or $HOME/go/bin. Once installed, you can register the skill by executing clawhub install openclaw/skills/skills/bowen31337/gopls-lsp. Finally, verify the installation by running gopls version in your terminal to ensure the agent can communicate with the server.

Use Cases

This skill is indispensable for managing large Go modules where manual code tracking becomes error-prone. Use it for: 1. Refactoring large structs or function signatures across multiple packages. 2. Debugging complex dependency trees using go mod commands through the agent. 3. Automatically identifying and fixing formatting issues using gofmt. 4. Running static analysis via go vet to identify suspicious constructs that might pass compilation but exhibit undefined behavior. 5. Generating boilerplate code for new project modules using go mod init.

Example Prompts

1. "OpenClaw, find all references to the UserService struct and rename it to AccountManager across the entire project."
2. "Review the current directory for any unused imports or variables in my Go code and provide a fix plan."
3. "Run the static analysis suite on this project and explain any errors found in main.go that might prevent a successful build."

Tips & Limitations

For optimal performance, always maintain a clean go.mod file in your project root. If the agent struggles with autocomplete, ensure the project is initialized as a Go module. Note that gopls performs better when the workspace root matches the directory containing go.mod. For highly complex or heavily generated codebases, consider adding a gopls.yaml file to configure specific analyses flags to prevent excessive memory usage or false positives. This skill requires file access to scan your repository effectively, so ensure the agent has the appropriate read/write permissions for the target directory.