code-review-pi

Orchestrate Go code quality review with linters, tests, and coverage.

122|13|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/dimetron/pi-go --skill code-review-pi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-pi
Source: https://github.com/dimetron/pi-go/tree/main/.pi-go/skills/code-review-pi
Command: npx skills add https://github.com/dimetron/pi-go --skill code-review-pi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review and quality assurance for Go projects by running linters, tests, and coverage, and capturing a final report for gating changes.

Core Features & Use Cases

  • Run automated linting with vet and golangci-lint
  • Execute tests with race detector and coverage, identify gaps
  • Spawn per-package subagents to write tests and fix issues, enforcing gates across the repo
  • Save the final report to ./specs/issues/003-code-review-pi/PROMPT.md for audit trails

Quick Start

Run a full code quality pass on your Go repository and save the final report to ./specs/issues/003-code-review-pi/PROMPT.md

Frequently Asked Questions about code-review-pi

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

FAQPage Schema
How do I automate Go code review with linting and coverage?

Automate Go code review by orchestrating go vet, golangci-lint, and go test with race detection and coverage reporting across a repository. The multi-stage workflow runs these tools to evaluate quality and writes a final summary report to PROMPT.md.

How do I run Go tests with race detection and coverage reporting?

Run Go tests with race detection and coverage reporting by executing go test with race flags across the repository. The workflow identifies coverage gaps and can spawn per-package subagents to write missing tests and fix issues, enforcing quality gates.

Can I use golangci-lint and go vet for automated quality assurance?

Yes, automated quality assurance uses golangci-lint and go vet to run linting checks across Go projects. The workflow orchestrates these linters alongside tests and coverage analysis, capturing results into a final audit report.

How do I enforce quality gates across multiple Go packages?

Enforce quality gates across multiple Go packages by spawning per-package parallel subagents that write tests and fix issues. The workflow coordinates these subagents to ensure linters, tests, and coverage thresholds pass across the entire repository.

What is the best way to generate a Go code quality audit trail?

Generate a Go code quality audit trail by running the full review workflow and saving the final report to ./specs/issues/003-code-review-pi/PROMPT.md. This file captures linting, testing, and coverage summaries for gating changes and historical review.

Does this automated code review work with large Go repositories?

Yes, automated code review applies to Go projects of varying sizes. By spawning per-package parallel subagents, the workflow handles large repositories efficiently, enforcing quality gates across all packages without manual intervention.