gosu-review-v1

Generate Korean Markdown code-review reports from changed Go files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns changed Go code into a structured Korean Markdown review report by detecting issues mapped from trigger-driven refactoring rules, while intentionally avoiding lint-covered rules to focus on design and context-sensitive concerns.

Core Features & Use Cases

  • Trigger-based Go code scanning: Identifies trigger locations by pattern in the full content of each relevant .go file.
  • Rules applied via modular references: Loads rule procedures from references/trigger-NN-*.md only for the triggered set.
  • Change-aware reporting: Separates newly triggered violations (🔴) from existing ones (🟡), grouped by file and sorted by line.
  • Context-aware workflow modes: Chooses either main direct processing or distributes to sub-agents based on trigger counts and a special always-main handling for trigger 14 (package/directory structure).

Quick Start

Provide the Git diff or the changed .go files to generate a gosu-review-v1 Markdown report that lists new (🔴) and existing (🟡) best-practice violations with suggested fixes.

Frequently Asked Questions about gosu-review-v1

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

FAQPage Schema
How do I generate a code review report for Go pull requests?

To generate a code review report for Go pull requests, provide the Git diff, changed `.go` files, or PR text. The tool outputs a structured Korean Markdown report flagging best-practice violations with suggested refactoring fixes.

What is trigger-based scanning for Go code refactoring?

Trigger-based scanning for Go code refactoring identifies specific pattern locations in `.go` files and maps them to modular refactoring rules. It focuses on design and context-sensitive concerns rather than basic linting errors.

Does this Go code reviewer separate new violations from existing ones in a diff?

Yes, this Go code reviewer separates new violations from existing ones. It annotates newly triggered violations on changed lines with a red circle and existing violations with a yellow circle in the final report.

Can I review specific changed line ranges in a Go diff?

Yes, you can review specific changed line ranges in a Go diff. In addition to providing the Git diff or changed files, you can optionally indicate the specific changed line ranges to focus the trigger scanning.

Are test files included in the Go pull request code review?

Test files are not included in the Go pull request code review. The scanning process intentionally excludes test files and deleted files to focus solely on active source code changes.

Why use a dedicated Go refactoring analyzer instead of a standard linter?

You use a dedicated Go refactoring analyzer instead of a standard linter to avoid duplicating lint-covered rules. This tool focuses exclusively on design and context-sensitive concerns mapped through trigger-driven refactoring rules.