skills.rest
MODAC-Agent
MODAC-AgentOFFICIAL
Explore all skills by this author →
GitHub

gosu-review-v2

Scan changed Go files and generate Markdown review reports from trigger-based rules.

Updated Apr 10, 2026
Search Tags:#static analysis#code review#go#git diff#idiomatic#markdown reporting#trigger-based rules
One-click install
npx skills add https://github.com/MODAC-Agent/hwichan-agent --skill gosu-review-v2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gosu-review-v2
Source: https://github.com/MODAC-Agent/hwichan-agent/tree/main/week2/scripts/skill-variants/gosu-review-v2
Command: npx skills add https://github.com/MODAC-Agent/hwichan-agent --skill gosu-review-v2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns a set of changed Go files into a focused, best-practice review report by detecting rule violations mapped to structured code-change triggers, reducing the risk of missing subtle idiomatic issues during reviews.

Core Features & Use Cases

  • Trigger-accurate scanning and rule application: Identifies where specific patterns appear in the changed Go code, then applies only the relevant, non-linter-covered rules for those triggers.
  • Change-aware reporting: Separates newly introduced violations (🔴) from existing ones (🟡) and consolidates multiple findings at the same location.
  • Context-first workflow: Reads full current file contents, uses reference documentation per trigger, and supports workflows based on direct files, git diffs, or PR text.

Quick Start

Use the gosu-review-v2 skill and ask it to review the Go files from your git diff and produce a Markdown report of new (🔴) and existing (🟡) idiomatic Go issues using the defined trigger rules.

Frequently Asked Questions about gosu-review-v2

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

FAQPage Schema
How do I review Go code changes for idiomatic best practices?▼

Review Go code changes for idiomatic best practices by scanning changed .go files and mapping detected patterns to predefined trigger-based rules, generating a consolidated Markdown report of violations.

Can I use git diff output to identify which Go files need review?▼

Yes, you can use git diff or git status output to identify changed Go files and line ranges. The review process also supports direct .go files or PR text as input to detect idiomatic issues.

How does trigger-based static analysis differ from standard linter checks?▼

Trigger-based static analysis applies only relevant, non-linter-covered rules to specific patterns found in changed code, focusing on subtle idiomatic Go issues rather than standard formatting or syntax violations.

Does the Go code review report distinguish between new and existing issues?▼

Yes, the Markdown report separates newly introduced violations marked with a red indicator from existing ones marked with a yellow indicator, while consolidating multiple findings at the same location.

Are test files included when scanning changed Go files for review?▼

No, _test.go files and deleted files are automatically excluded during the scanning process to ensure the review focuses only on functional Go source code changes.

Related Skills

Explore More Software Engineering Skills→
MODAC-AgentMODAC-Agent

gosu-review-v1

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

Official
Advanced
gopherguidesgopherguides
19

go-code-audit

Identify and report Go code quality issues with severity levels and remediation recommendations.

Official
Intermediate
maxrittermaxritter
1.8k

standards-golang

Enforce Go standards for dependency management, testing, and code quality.

Community
Advanced
1024XEngineer1024XEngineer
43

golang-patterns

Demonstrate idiomatic Go patterns for concurrency, error handling, and interfaces.

Official
Advanced