go-patterns

Go code review for concurrency and error handling requires classifying task triggers like goroutines, channels, and errors.Is/As to load matching reference methodologies. This routing enforces deterministic execution by applying specific review phases and quality gate checks.

Applying SAP CC conventions in Go involves routing HTTP and JSON formatting tasks to specialized reference instructions. The process enforces codebase-specific lint-style checks and TODO-format enforcement to maintain deterministic quality gate verification.

Go benchmark comparisons for refactors require running provided scripts using the benchstat dependency. This script execution analyzes performance differences, ensuring refactored code maintains deterministic execution requirements and passes quality gate verification.

Go testing methodology integrates with standard quality gate runs by loading relevant domain reference files and executing optional scripts. It classifies the task domain, follows corresponding reference phases, and enforces deterministic execution requirements during make check operations.

Running Go error-handling anti-pattern scans requires bash, python3, and grep dependencies to execute provided scripts. These tools enable interface compliance checks and error-handling anti-pattern scanning by processing reference instructions loaded during task classification.

Go PR reviews skip hard methodologies when applying generic prompts instead of evidence-based routing. Classifying task triggers for testing, goroutines, or errors.Is/As loads matching reference files, enforcing deterministic guardrails and domain-specific review phases.