skills.rest
daltoniam
daltoniamCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr-review

Review GitHub pull requests for the Switchboard Go MCP server.

15|7|Updated Feb 26, 2026
Search Tags:#testing#architecture#go#review#code-quality#pull-request#switchboard
One-click install
npx skills add https://github.com/daltoniam/switchboard --skill pr-review-daltoniam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/daltoniam/switchboard/tree/main/.agents/skills/pr-review
Command: npx skills add https://github.com/daltoniam/switchboard --skill pr-review-daltoniam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review GitHub pull requests for the Switchboard Go MCP server to ensure idiomatic Go, hexagonal architecture, and production readiness, delivering clear, actionable feedback.

Core Features & Use Cases

  • Enforce Go idioms, project conventions, and test coverage on PRs.
  • Validate architecture conformance (hexagonal design, port interfaces, and dispatch maps) and build stability.
  • Provide guidance for improvements and secure, maintainable changes in collaborative reviews.

Quick Start

Review a PR by its number, URL, or branch name to initiate the review workflow.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I review a GitHub pull request for idiomatic Go and hexagonal architecture?▼

Reviewing a GitHub pull request for idiomatic Go involves validating build viability, test coverage, and adherence to hexagonal architecture. This Skill checks PRs by number, URL, or branch name to enforce project conventions and production readiness.

Can I check a pull request by branch name or URL instead of a PR number?▼

Yes, you can check a pull request by branch name or URL instead of a PR number. The review workflow identifies and reviews GitHub pull requests using any of these three identifiers to enforce Go idioms and project conventions.

What is the best way to enforce test coverage and project conventions in a Go pull request?▼

The best way to enforce test coverage and project conventions in a Go pull request is to validate build stability and architecture conformance. This ensures secure, maintainable changes by providing actionable feedback on port interfaces and dispatch maps.

Does this pull request review process validate hexagonal architecture and port interfaces?▼

Yes, this pull request review process validates hexagonal architecture and port interfaces. It ensures production readiness by checking adherence to project architecture, security practices, and dispatch maps across Go adapters and core changes.

How do I ensure production readiness and security practices in a collaborative Go code review?▼

To ensure production readiness and security practices in a collaborative Go code review, validate build viability and architecture conformance. This Skill delivers clear, actionable feedback for secure and maintainable changes across core updates.

What are the limitations of automated PR reviews for Go adapters and core changes?▼

Automated PR reviews for Go adapters and core changes focus on architecture conformance and test coverage but may not catch highly context-specific business logic flaws. They enforce idiomatic Go and project conventions within the Switchboard MCP server scope.

Related Skills

Explore More Software Engineering Skills→
maveroxmaverox

pr-analysis

Parse GitHub pull request data and summarize metadata, diffs, and scope.

Community
Advanced
baphledbaphled
1

pre-merge

Execute a pre-merge validation checklist for Pull Requests.

Community
Intermediate
vrcmsvrcms
1

springboot-verification

Automate Spring Boot build, static analysis, test coverage, and security scans.

Community
Advanced
LuigiAPCPereiraLuigiAPCPereira

golang-naming

Validate Go naming conventions using linters like revive and misspell.

Community
Advanced