go-patterns

Query learned Go anti-patterns and fix patterns from go-guardian knowledge base.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kengou/go-guardian --skill go-patterns-kengou
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-patterns
Source: https://github.com/kengou/go-guardian/tree/main/skills/go-patterns
Command: npx skills add https://github.com/kengou/go-guardian --skill go-patterns-kengou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers identify and understand learned Go anti-patterns and their fix patterns from the go-guardian knowledge base, guiding smarter code reviews and architectural decisions.

Core Features & Use Cases

  • Read-only querying of anti-patterns and pattern dashboards produced by go-guardian scans.
  • Access pattern-stats and health-trend analyses to inform refactoring and architectural reviews.
  • Supports focused discussions on code smells, recurring bugs, and design concerns across a Go project.

Quick Start

Ask it to search for a pattern like 'goroutine leak' and return the top matches.

Frequently Asked Questions about go-patterns

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

FAQPage Schema
How do I find known Go anti-patterns in my codebase?

To find known Go anti-patterns, you can query the knowledge base to search for specific code smells like 'goroutine leak' and retrieve top matches with their corresponding fix patterns.

What are common Go anti-patterns and how do I fix them?

Common Go anti-patterns and their fix patterns are stored in the knowledge base, enabling you to browse learned code smells and apply the suggested fixes during code reviews.

How do I check the health trends of Go anti-patterns across my project?

You can check Go anti-pattern health trends by accessing the pattern-stats and health-trend artifacts generated by scans, which inform refactoring decisions and architectural reviews.

Do I need prior scan artifacts to query Go anti-patterns?

Yes, querying Go anti-patterns requires access to pattern dashboards and health-trends artifacts generated by prior go-guardian scans, as the skill retrieves data from these outputs.

Can I use this to find recurring Go bugs during code review?

Yes, you can use this to support focused discussions on recurring bugs during code review by querying the knowledge base for learned anti-patterns and their associated architectural concerns.

What is the best way to analyze architecture concerns in a Go project?

The best way to analyze architecture concerns is by querying the knowledge base for learned anti-patterns and reviewing pattern-stats dashboards to inform your architectural decisions.