gopherstack: Instructions file for GitHub Copilot

Session Management

• Commit and push after completing each task.
• Your max session is 1 hour — when approaching the limit, create checkpoint.md at the repo root (what is done, what remains, any blockers) and push. Remove checkpoint.md when the full issue is complete.
• Run task test after each task before committing. Resolve all lint issues via task lint-fix.
• Min test coverage is 85%.
• Add integration tests in test/integration/ as you go for everything you implement.
• Run task build before pushing.

Go Development Instructions

Follow idiomatic Go practices and community standards when writing Go code. These instructions are based on Effective Go, Go Code Review Comments, and Google's Go Style Guide.

General Instructions

• Write simple, clear, and idiomatic Go code
• Favor clarity and simplicity over cleverness
• Follow the principle of least surprise
• Keep the happy path left-aligned (minimize indentation)
• Return early to reduce nesting
• Prefer early return over if-else chains; use if condition { return } pattern to avoid else blocks
• Make the zero value useful
• Write self-documenting code with clear, descriptive names
• Document exported types, functions, methods, and packages
• Use Go modules for dependency management
• Leverage the Go standard library instead of reinventing the wheel (e.g., use strings.Builder for string concatenation, filepath.Join for path construction)
• Prefer standard library solutions over custom implementations when functionality exists
• Write comments in English by default; translate only upon user request
• Avoid using emoji in code and comments
• Avoid break statements; any loop break should be factored into a separate function with a fast return
• Logging MUST always be performed via log/slog and MUST always be pulled from the context (e.g. logger.Load(ctx))
• Avoid nolint directives; removing rules is forbidden unless no other fix is available