Skip to content

Feat/golang instructions#38

Merged
aaronpowell merged 2 commits into
github:mainfrom
salihdev0:feat/golang-instructions
Jul 3, 2025
Merged

Feat/golang instructions#38
aaronpowell merged 2 commits into
github:mainfrom
salihdev0:feat/golang-instructions

Conversation

@salihdev0

Copy link
Copy Markdown
Contributor

name: Pull Request
about: Submit a contribution to the awesome-copilot repository
title: 'Add Go language instructions'
labels: needs-review
assignees: ''

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • My contribution adds a new instruction, prompt, or chat mode file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, or chat mode with GitHub Copilot.
  • I have run node update-readme.js and verified that README.md is up to date.

Description

This PR introduces comprehensive Go language instructions for the awesome-copilot repository. The instructions provide detailed guidance for writing idiomatic Go code, covering all essential aspects of Go development from basic syntax to advanced patterns.

Key highlights:

  • Introduced a detailed guide for writing Go code adhering to idiomatic practices
  • Covers general instructions, naming conventions, code style, error handling, and security best practices
  • References established resources like Effective Go and Google's Go Style Guide
  • Follows the existing project structure and format used by other language instruction files
  • Includes Go-specific patterns such as goroutines, channels, and Go's unique error handling approach

The instructions are based on authoritative Go resources including:


Type of Contribution

  • New instruction file.
  • New prompt file.
  • New chat mode file.
  • Other (please specify):

Additional Notes

The Go instructions file (go.instructions.md) covers comprehensive topics including:

  • General Go principles emphasizing simplicity and clarity
  • Go-specific naming conventions for packages, functions, and types
  • Error handling patterns unique to Go
  • Concurrency patterns using goroutines and channels
  • Testing practices including table-driven tests
  • Performance optimization techniques
  • Security best practices
  • Standard project structure following Go conventions

The file uses the standard YAML frontmatter format with applyTo patterns covering Go source files (**/*.go) and module files (**/go.mod, **/go.sum).


By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

salihdev0 added 2 commits July 3, 2025 13:34
- Introduced a detailed guide for writing Go code adhering to idiomatic practices.
- Covers general instructions, naming conventions, code style, error handling, and security best practices.
- References established resources like Effective Go and Google's Go Style Guide.
- Introduced guidelines for writing Go code that adhere to idiomatic Go practices and community standards.
Copilot AI review requested due to automatic review settings July 3, 2025 10:36

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a new Go instructions file to provide idiomatic Go coding guidelines and updates the project README to include it.

  • Introduces instructions/go.instructions.md with comprehensive Go development guidance
  • Updates README.md to register the new Go instructions link

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
instructions/go.instructions.md Added comprehensive Go instructions front-matter and content
README.md Added entry for “Go Development Instructions”

@aaronpowell aaronpowell merged commit 4ab31cd into github:main Jul 3, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants