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.