review-test

Audit Go pull requests for test coverage and best practices.

1|Updated Mar 8, 2026

Search Tags:#testing #quality assurance #code review #pull request #go #auditing

Ready to run

npx skills add https://github.com/viqueen/claude-go-playground --skill review-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-test
Source: https://github.com/viqueen/claude-go-playground/tree/main/.claude/skills/review-test
Command: npx skills add https://github.com/viqueen/claude-go-playground --skill review-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the rigorous auditing of pull requests focused on tests, ensuring comprehensive code coverage and adherence to best practices, thereby improving software quality and reducing bugs.

Core Features & Use Cases

Automated Test Auditing: Systematically checks test code against a detailed checklist.
Best Practice Enforcement: Verifies adherence to established patterns for test setup, structure, and assertions.
Use Case: A developer submits a PR with new test cases. This Skill can be used to automatically flag any missing test scenarios, incorrect assertion methods, or anti-patterns before the code is merged, saving review time and preventing regressions.

Quick Start

Use the review-test skill to audit the test pull request for number 123.

Frequently Asked Questions about review-test

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

FAQPage Schema

How do I audit test code in a pull request for Go projects?▼

To audit test code in a pull request, you can analyze test setup, file structure, API coverage, assertion usage, and common anti-patterns to ensure comprehensive coverage and best practices. This skill validates test quality for Go projects using Connect-RPC or gRPC frameworks.

What is the best way to enforce quality assurance best practices on test PRs?▼

Enforcing quality assurance best practices on test PRs involves systematically checking test code against a detailed checklist covering test case ordering, naming conventions, and outbox worker tests. This automated auditing prevents regressions by flagging missing scenarios before merge.

Does this test auditing tool work with gRPC and Connect-RPC frameworks?▼

Yes, this test auditing tool works with gRPC and Connect-RPC frameworks. It specifically validates test quality for Go projects using these frameworks, analyzing API test coverage and common anti-patterns to ensure adherence to established testing patterns.

What common anti-patterns are checked during a pull request test audit?▼

During a pull request test audit, common anti-patterns are checked alongside assertion usage, test case ordering, and naming conventions. The audit systematically analyzes test setup and file structure to flag incorrect assertion methods and missing test scenarios.

Can I automatically flag missing test scenarios before merging a Go pull request?▼

Yes, you can automatically flag missing test scenarios before merging a Go pull request. By auditing test code against a detailed checklist for best practices and API coverage, the skill identifies gaps and incorrect assertions to save review time.

When do I need to run an automated test code review?▼

You need to run an automated test code review when a developer submits a pull request with new test cases. It systematically checks the test setup, structure, and assertions to improve software quality and reduce bugs before the code is merged.