mcpField
G
go-skills

go-skills

github.com/llama-farmDevelopment83655 installsUpdated 21w ago
Repository

About go-skills

go-skills is a set of Go development guidelines for LlamaFarm CLI contributors. It covers idiomatic, maintainable, and secure code practices, with checklists for core engineering topics.

Key features

  1. 01Go error handling and concurrency guidance
  2. 02Testing and security checklists
  3. 03Idiomatic Go patterns
  4. 04LlamaFarm CLI codebase conventions

Use cases

  1. 01Reviewing Go changes in LlamaFarm CLI
  2. 02Applying consistent error and concurrency handling
  3. 03Checking tests and security practices

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/llama-farm/llamafarm --skill go-skills

After installing, type/go-skillsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

concurrency.md
error-handling.md
patterns.md
security.md
testing.md

Details

From the project README

Go Skills for LlamaFarm CLI

Shared Go best practices for LlamaFarm CLI development. These guidelines ensure idiomatic, maintainable, and secure Go code.

Tech Stack

  • Go 1.24+
  • Cobra (CLI framework)
  • Bubbletea (TUI framework)
  • Lipgloss (terminal styling)

Directory Structure

cli/
  cmd/           # Command implementations
    config/      # Configuration types and loading
    orchestrator/ # Service management
    utils/       # Shared utilities
    version/     # Version and upgrade handling
  internal/      # Internal packages
    tui/         # TUI components
    buildinfo/   # Build information

Quick Reference

Error Handling
  • Always wrap errors with context: fmt.Errorf("operation failed: %w", err)
  • Use sentinel errors for expected conditions: var ErrNotFound = errors.New("not found")
  • Check errors immediately after function calls
Concurrency
  • Use sync.Mutex for shared state protection
  • Use sync.RWMutex when reads dominate writes
  • Use channels for goroutine communication
  • Always use defer for mutex unlocks
Testing
  • Use table-driven tests for comprehensive coverage
  • Use interfaces for mockability
  • Test file names: *_test.go in same package
Security
  • Never log credentials or tokens
  • Redact sensitive headers in debug logs
  • Validate all external input
  • Use context.Context for cancellation

Checklist Files

FileDescription
patterns.mdIdiomatic Go patterns
concurrency.mdGoroutines, channels, sync
error-handling.mdError wrapping, sentinels
testing.mdTable-driven tests, mocks
security.mdInput validation, secure coding

Go Proverbs to Remember

  1. "Don't communicate by sharing memory; share memory by communicating"
  2. "Errors are values"
  3. "A little copying is better than a little dependency"
  4. "Clear is better than clever"
  5. "Design the architecture, name the components, document the details"

Common Patterns in This Codebase

HTTP Client Interface
type HTTPClient interface {
    Do(req *http.Request) (*http.Response, error)
}
Process Management with Mutex
type ProcessManager struct {
    mu        sync.RWMutex
    processes map[string]*ProcessInfo
}
Cobra Command Pattern
var myCmd = &cobra.Command{
    Use:   "mycommand",
    Short: "Brief description",
    RunE: func(cmd *cobra.Command, args []string) error {
        // Implementation
        return nil
    },
}
Bubbletea Model Pattern
type myModel struct {
    // State fields
}

func (m myModel) Init() tea.Cmd { return nil }
func (m myModel) Update(msg tea.Msg) (tea.Model, tea.Cmd) { /* ... */ }
func (m myModel) View() string { return "" }

Comments

Markdown supported