smithery/matt-riley

testing-workflows

Run, debug, and structure tests for this Go project (unit + integration), including generation prerequisites. Use when changing domain logic, repositories, HTTP handlers, or migrations.

Installation

$ npx skills add smithery/matt-riley --skill testing-workflows

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/matt-riley.

npx skills add smithery/matt-riley

Browse all from smithery/matt-riley

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.3
LicenseMIT
CompatibilityRequires bash, git, Go, and make.
Allowed toolsBash(git:*) Bash(make:*) Bash(go:*) Read
Declared agents github-copilot
More metadata
repo
mjrwtf
runner
github-copilot-cli
version
1.3

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,287 B
  • docs SUMMARY.md 210 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Tooling assumptions

  • Use a terminal runner with bash and git available.
  • Prefer make targets when available; fall back to direct CLI commands when needed.

Fast paths

  • All tests (runs generation first):
make test
  • Unit tests only:
make test-unit
  • Integration tests only (HTTP server suite):
make test-integration

Debugging failures

  1. If you see compile errors for generated packages, run:
make generate
  1. Re-run the failing package with verbose output:
go test -v ./path/to/pkg
  1. If the failure is DB-related, confirm DATABASE_URL is correct and migrations are applied (for integration setups).

What to cover when adding features

  • Domain validation (table-driven tests).
  • Repository behavior (in-memory SQLite tests).
  • HTTP behavior (status codes + auth + schemas).