gosu-review

Review Go diffs against idiomatic refactoring rules and generate Korean Markdown reports.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/MODAC-Agent/hwichan-agent --skill gosu-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gosu-review
Source: https://github.com/MODAC-Agent/hwichan-agent/tree/main/week2
Command: npx skills add https://github.com/MODAC-Agent/hwichan-agent --skill gosu-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps teams review Go code changes consistently by detecting design and contextual issues that static linters can’t reliably catch, and packaging findings into a structured Korean Markdown report.

Core Features & Use Cases

  • Trigger-based, rule-scoped review: scans change-relevant patterns and loads only the corresponding reference materials for efficient reviews.
  • Idiomatic Go-focused output contract: produces a Korean Markdown report that separates new (changed-line) violations from existing ones, including rule numbers, names, and one-sentence justifications.
  • Linter-aware boundary: avoids duplicating findings covered by golangci-lint, focusing the skill on architectural and judgment-heavy guidance.
  • Use Cases: reviewing .go file changes in PRs, refactoring proposals, and catching risky Go patterns (e.g., error handling, defer usage, slice/string memory pitfalls, package structure smells).

Quick Start

Use gosu-review to review the changed Go files in the current git repository and ask for a Korean Markdown report of idiomatic Go refactoring issues.

Frequently Asked Questions about gosu-review

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

FAQPage Schema
How do I review Go PR diffs for idiomatic refactoring issues that linters miss?

Review Go PR diffs for idiomatic refactoring by mapping change-trigger patterns to predefined rules, enforcing scoped reference loading, and generating a structured Markdown report that separates new violations from existing ones.

What is the best way to generate a structured Go code review report in Korean?

Generate a structured Go code review report in Korean by scanning non-test `.go` file changes, applying idiomatic refactoring rules, and outputting per-finding evidence with one-line actionable suggestions.

Does this Go review skill check for architectural smells or just standard static analysis errors?

This Go review skill checks for architectural smells and judgment-heavy design issues, explicitly excluding rules already covered by golangci-lint to focus on deeper contextual guidance like error handling and package structure.

Can I use this to review working directory changes instead of a formal pull request diff?

You can review working directory changes as well as formal pull request diffs, because the skill processes any git change set targeting non-test `.go` files to highlight risky Go patterns.

How are Go code review findings formatted in the final output?

Go code review findings are formatted as a consistent per-finding output containing rule numbers, names, one-sentence justifications, and one-line actionable suggestions within a Korean Markdown report.

What limitations exist when reviewing Go code for idiomatic patterns?

Limitations include excluding test `.go` files from review targets, omitting linter-covered rules to avoid duplication, and restricting output to Korean Markdown with fixed per-finding formats.