Skip to content
TrustedSkillsbeta
Back to all skills

Go Testing

Checked
cxuu·vlatest·testing·Apache-2.0

Helps with Go, testing as part of testing, debugging, and quality assurance workflows.

Repository

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-testing -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.

Commit
91f0c2eef5
Manifest
skills/go-testing/SKILL.md
Scanned
8 files, 1,050 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

What it does

This skill assists with Go testing, debugging, and quality assurance workflows. It provides guidance on best practices for writing effective and diagnosable Go tests, covering topics from error reporting to comparison techniques and test structure. The skill emphasizes clear failure messages and discourages the use of assertion libraries in favor of direct comparisons using cmp.Diff.

When to use it

  • When you need help structuring Go tests for clarity and maintainability.
  • When writing table-driven tests with shared logic across multiple cases.
  • When debugging failing Go tests and needing to understand the root cause quickly.
  • To ensure your test failures provide sufficient information (function name, inputs, actual vs expected values).

Key capabilities

  • Guidance on using t.Error versus t.Fatal for reporting test failures.
  • Best practices for creating informative failure messages including function names and input values.
  • Recommendations for comparing data structures (structs, slices, maps, protobufs) using cmp.Diff.
  • Advice on structuring table-driven tests and when to use them appropriately.
  • Information about subtests for filtering, parallel execution, and naming.

Example prompts

  • "How should I format a test failure message in Go?"
  • "What's the best way to compare two structs in my Go test?"
  • "Should I use t.Error or t.Fatal for this failing test case?"

Tips & gotchas

  • Always include function names and inputs in your failure messages for easy debugging.
  • Avoid using assertion libraries; utilize cmp.Diff for complex comparisons.
  • Refer to the referenced documents (TEST-HELPERS.md, TABLE-DRIVEN-TESTS.md) for more detailed information on specific testing techniques.