Skip to content
TrustedSkillsbeta
Back to all skills

Go Testing Code Review

Checked
existential-birds·vlatest·testing·Apache-2.0

Helps with Go, testing, code review 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 existential-birds/beagle --skill go-testing-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

existential-birds

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 existential-birds/beagle at d1a74899fb.

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

Commit
d1a74899fb
Manifest
plugins/beagle-go/skills/go-testing-code-review/SKILL.md
Scanned
3 files, 914 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 provides guidance and checks for writing effective Go tests, focusing on code review best practices. It helps ensure test suites are well-structured, readable, and comprehensive by referencing established patterns and offering suggestions for improvement. The skill covers aspects like table-driven tests, mocking, error message clarity, parallel testing, cleanup routines, benchmarks, and fuzz tests (Go 1.18+).

When to use it

  • During code review of Go projects to ensure test quality.
  • When writing new Go tests or refactoring existing ones.
  • To identify potential issues with test structure, naming conventions, or error handling.
  • For teams adopting best practices for Go testing and wanting a checklist-driven approach.
  • When implementing performance benchmarks or fuzz tests in Go 1.18+ projects.

Key capabilities

  • Test Structure Guidance: Provides examples of good and bad test structures, emphasizing table-driven tests with clear case names.
  • Mocking Best Practices: Offers guidance on using interfaces for mocking.
  • Error Message Clarity: Promotes descriptive error messages including got/want comparisons.
  • Parallel Test Support: Guidance on running parallel tests safely and correctly.
  • Cleanup Routines: Demonstrates proper use of t.Cleanup to ensure resource cleanup even if tests panic.
  • Benchmark Testing: Provides a template for creating performance benchmarks using the Benchmark* pattern.
  • Fuzz Testing (Go 1.18+): Guidance on writing fuzz tests with seed corpus examples.
  • Golden File Tests: Supports golden file testing with -update flag usage.

Example prompts

  • "Review this Go test function for adherence to best practices."
  • "Suggest improvements to the structure of this table-driven test."
  • "How can I write a better error message in this failing test?"
  • “Show me an example of how to use t.Cleanup.”

Tips & gotchas

  • This skill focuses on code review and guidance; it doesn't automatically generate tests.
  • Fuzz testing functionality requires Go 1.18 or later.
  • The skill references external documentation (references/structure.md, references/mocking.md) for more detailed information.