skills.rest
matt-riley
matt-rileyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

testing-workflows

Automate debugging workflows for Go unit and integration tests.

1|1|Updated May 3, 2026
Search Tags:#testing#debugging#go#generator#workflows#ci
One-click install
npx skills add https://github.com/matt-riley/agent-skills --skill testing-workflows-matt-riley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-workflows
Source: https://github.com/matt-riley/agent-skills/tree/main/skills/testing-workflows
Command: npx skills add https://github.com/matt-riley/agent-skills --skill testing-workflows-matt-riley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Go tests can drift due to generated code changes, flaky runs, and misconfigurations, making failures hard to diagnose quickly.

Core Features & Use Cases

  • Guided debugging workflow: provide steps to reproduce, isolate, and fix failing unit and integration tests across domain, repository, and handler layers.
  • Generator refresh guardrails: prompts to run code generation before tests when necessary to avoid stale inputs.
  • Scope-aware recommendations: directs users to the appropriate tests (unit vs integration) and relevant areas of the codebase.

Quick Start

Run the testing-workflows skill to diagnose and fix failing Go tests across unit and integration scenarios.

Frequently Asked Questions about testing-workflows

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

FAQPage Schema
How do I debug failing Go tests when generated code changes cause failures?▼

Debug failing Go tests caused by generated code changes by following a guided workflow that detects stale inputs, refreshes generated code before running tests, and isolates failures across domain, repository, and handler layers.

Why do my Go unit tests fail after updating generated code?▼

Go unit tests fail after generated code updates when stale inputs are not refreshed before testing. Running code generation before tests ensures generated code matches current inputs and prevents misconfiguration-related test drift.

What's the best way to isolate failing Go integration tests in a CI workflow?▼

Isolate failing Go integration tests in CI by applying scope-aware recommendations that direct you to appropriate test targets, separating unit from integration tests and identifying relevant codebase areas for rapid diagnosis.

Do I need the Go toolchain installed to run these testing workflows?▼

Yes, the Go toolchain is required to run these testing workflows. The skill automates debugging for Go unit and integration tests and requires a disciplined approach to running code generation before tests and validating coverage.

How do I fix flaky Go test runs that are hard to diagnose?▼

Fix flaky Go test runs by following a guided debugging workflow that reproduces failures, isolates test targets across domain and handler layers, and validates test coverage to diagnose and resolve misconfigurations quickly.

Related Skills

Explore More Software Engineering Skills→
Veloxia-agencyVeloxia-agency

ci-cd-pipeline-builder

Detect repository stack signals and generate CI/CD pipeline templates for GitHub Actions or GitLab CI.

Community
Intermediate
porcupine-mdporcupine-md
11

fixing-flaky-tests

Diagnose and fix flaky tests caused by timing dependencies, test pollution, and async leaks.

Official
Intermediate
Sheldon-92Sheldon-92
3

Testing

Execute test suites and report failures with coverage metrics.

Community
Intermediate
dvy1987dvy1987
3

test-driven-development

Enforce Red-Green-Refactor by writing failing tests before production code.

Community
Intermediate