go-test-runner

Execute Go backend tests and summarize failures with optional coverage.

5|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/no-problem-dev/claude-code-plugins --skill go-test-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-test-runner
Source: https://github.com/no-problem-dev/claude-code-plugins/tree/main/.agents/skills/agent--go-test-runner
Command: npx skills add https://github.com/no-problem-dev/claude-code-plugins --skill go-test-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the execution of Go backend tests, providing a clear summary of the results without overwhelming you with full logs.

Core Features & Use Cases

  • Automated Test Execution: Runs go test for your Go backend projects.
  • Concise Reporting: Summarizes test results, highlighting only failed tests with actionable details.
  • Optional Coverage: Generates coverage reports when explicitly requested.
  • Use Case: After making changes to your Go API, use this Skill to quickly verify that all tests pass and identify any regressions.

Quick Start

Run all Go tests in the current project and report any failures.

Frequently Asked Questions about go-test-runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Go backend tests and get a summary of failures?

Run Go backend tests by executing the test suite in projects with a go.mod file to receive a summarized output highlighting failed tests with actionable details.

Can I generate a test coverage report for my Go project?

Yes, you can generate a Go test coverage report by explicitly requesting coverage generation when running your backend test suite.

How do I reduce log verbosity when running go test in a CI/CD pipeline?

Reduce log verbosity in CI/CD pipelines by running automated Go tests that provide concise reporting and summarize only failed test cases.

Does the automated Go test runner require a specific project structure?

Yes, the automated Go test runner scopes to backend projects containing a go.mod file to detect the directory and execute tests.

Why should I use a summarized test runner instead of raw go test output?

A summarized test runner provides rapid developer feedback by minimizing log verbosity and highlighting only failed tests with actionable details instead of overwhelming logs.