slop-hunter-go

Detects and removes AI-generated noise from Go code.

5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/skyosev/agent-skills --skill slop-hunter-go
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slop-hunter-go
Source: https://github.com/skyosev/agent-skills/tree/main/hunter-party-go/slop-hunter-go
Command: npx skills add https://github.com/skyosev/agent-skills --skill slop-hunter-go

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and remove AI-generated noise in Go code, including redundant comments, verbose godoc, style drift from project conventions, trivially dead code, and unnecessary error wrapping. The result is cleaner, more idiomatic Go that stays aligned with gofmt standards.

Core Features & Use Cases

  • Detect redundant comments that restate obvious behavior and clutter the codebase.
  • Flag verbose or repetitive godoc on exported and unexported symbols where unnecessary.
  • Identify style drift from the project's Go idioms, formatting, and import grouping.
  • Surface dead code, unused imports, and over-wrapped errors to improve maintainability.
  • Provide actionable cleanup guidance during AI-assisted code reviews or pre-merge hygiene passes.

Quick Start

Provide the Go source you want audited and I will surface noise patterns to remove.

Frequently Asked Questions about slop-hunter-go

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

FAQPage Schema
How do I remove redundant comments and verbose godoc from AI-generated Go code?

To remove redundant comments and verbose godoc from AI-generated Go code, you can audit the source to surface noise patterns like style drift and trivially dead code. This enforces project conventions and gofmt standards during code reviews or pre-merge hygiene passes.

What is the best way to enforce gofmt and project conventions during a Go code review?

The best way to enforce gofmt and project conventions during a Go code review is to scan the target path for AI-generated noise, including style drift, unnecessary error wrapping, and unused imports. This surfaces actionable cleanup guidance to ensure idiomatic Go.

Can I detect trivially dead code and unnecessary error wrapping in a whole Go codebase?

Yes, you can detect trivially dead code and unnecessary error wrapping across a whole Go codebase or a branch-level diff. The audit identifies AI-generated noise, providing actionable cleanup guidance to improve maintainability and align with established patterns.

Does this Go code hygiene audit work with branch-level diffs or only full repositories?

This Go code hygiene audit works with both branch-level diffs and full repositories. You can apply it during AI-assisted code reviews or pre-merge hygiene passes to surface style drift, redundant comments, and dead code across any target path.

Why does AI-assisted Go code often contain style drift and redundant comments?

AI-assisted Go code often contains style drift and redundant comments because AI models generate verbose explanations and trivially dead code that clutter the codebase. Auditing the source surfaces these noise patterns, ensuring the code stays aligned with gofmt and project idioms.