review-domain

Audit Go domain-layer pull requests for architectural pattern compliance.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/viqueen/claude-go-playground --skill review-domain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-domain
Source: https://github.com/viqueen/claude-go-playground/tree/main/.claude/skills/review-domain
Command: npx skills add https://github.com/viqueen/claude-go-playground --skill review-domain

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the auditing of code changes within a project's domain layer, ensuring adherence to architectural standards and best practices, thereby improving code quality and maintainability.

Core Features & Use Cases

  • Automated Code Review: Checks for correct file structure, interface conventions, layer rules, and error handling within the domain package.
  • Transactional Integrity: Verifies the implementation of transactional outbox patterns for write operations and cache-first patterns for read operations.
  • Use Case: A developer submits a Pull Request to add new business logic. This Skill can be used to automatically review the changes in the internal/domain/ directory, flagging any deviations from the established patterns before a human reviewer even looks at it.

Quick Start

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

Frequently Asked Questions about review-domain

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

FAQPage Schema
How do I automate Go domain layer code review for pull requests?

Use automated code review to check pull requests for correct file structure, interface conventions, and error handling within the domain package, flagging any architectural deviations before a human reviewer evaluates it.

How do I enforce transactional outbox pattern compliance in a Go pull request?

Validate transactional outbox pattern compliance by auditing pull requests for correct outbox event emission and error handling, ensuring transactional integrity within the Go domain layer.

Can I check Go interface-first conventions and layer import rules in a PR audit?

Automated code review checks Go pull requests for correct interface conventions and layer import rules within the domain package, flagging any structural deviations from established architectural standards.

What is the best way to validate error handling and outbox event emission in Go domain logic?

Use automated code review to validate error handling and outbox event emission in Go domain logic, flagging deviations from established architectural patterns before human review.

Does this automated code review work with the internal/domain/ directory structure in Go projects?

Automated auditing reviews code changes within the internal/domain/ directory of Go projects, flagging deviations from established architectural patterns and interface-first conventions before human review.