Skip to content
TrustedSkillsbeta
Back to all skills

Go Code Review

Checked
cxuu·vlatest·backend·Apache-2.0

Helps with Go, code review as part of developing backend services and APIs workflows.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add cxuu/golang-skills --skill go-code-review -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

cxuu

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned cxuu/golang-skills at 91f0c2eef5.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
4 files, 582 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The go-code-review skill enables AI agents to analyze Go source code, identifying potential bugs, security vulnerabilities, and style inconsistencies. It provides actionable feedback to help developers maintain high-quality, idiomatic Golang implementations.

When to use it

  • Before merging pull requests involving critical backend logic or API endpoints.
  • During the initial development phase to catch syntax errors and logical flaws early.
  • When refactoring legacy Go codebases to ensure adherence to modern best practices.
  • To automate routine linting tasks, freeing up human reviewers for complex architectural decisions.

Key capabilities

  • Static analysis of Go source files for common error patterns.
  • Detection of security vulnerabilities specific to the Go ecosystem.
  • Code style validation against standard Golang formatting and conventions.
  • Identification of performance bottlenecks in concurrent goroutines or memory management.

Example prompts

  • "Review this Go function for race conditions and suggest fixes."
  • "Analyze the provided backend handler code for security vulnerabilities and inefficiencies."
  • "Check if this new module adheres to standard Go formatting and best practices."

Tips & gotchas

Ensure the AI agent has access to the full dependency tree, as context is often required to accurately assess import usage and external library interactions. While effective at catching syntax and logic errors, complex architectural decisions may still require human oversight.