azure-dev go.instructions.md

Go code-review instructions for projects using Go 1.26 or newer. They explain which newer language patterns reviewers should accept and remind them to inspect the entire file, not only changed lines.

In plain words
What is it for?
Reviewing Go pull requests, checking command-line behavior and domain filtering, and verifying imports or declarations across complete files.
Why use it?
They help prevent valid modern Go code from being reported as an error and reduce review mistakes caused by missing context in a diff.

Instructions file for GitHub Copilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/azure/azure-dev/go
Clone the repo
git clone --depth 1 https://github.com/Azure/azure-dev

Made for: GitHub Copilot.

Per session 502 This file is loaded in full into every session.
When invoked 502 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00502 $0.00502
Opus 5 $0.00251 $0.00251
Sonnet 5 $0.00100 $0.00100
Haiku 4.5 $0.00050 $0.00050

Measured 2d ago against content hash 0a8f4d3a2188, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

azure-dev go.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/instructions/go.instructions.md · 35 lines

How it starts

The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.

applyTo:

  • "**/*.go"

Modern Go (1.26+) — PR Review Guidelines

This project uses Go 1.26 (cli/azd/go.mod). Do not flag modern Go 1.26 features as errors.

new(expr) creates typed pointers from values

new(false), new(true), new(0), new("s") are valid Go 1.26. They create a pointer to the given value. This replaces helper functions like to.Ptr(val). Do NOT suggest boolPtr() or &localVar replacements.

Other modern patterns to accept (not flag)

  • errors.AsType[*T](err) — generic error unwrapping (replaces var e *T; errors.As(err, &e))
  • for i := range n — range over integers
  • t.Context() — test context (replaces context.Background() in tests)
  • t.Chdir(dir) — test directory change (replaces os.Chdir + deferred restore)
  • wg.Go(func() { ... }) — WaitGroup shorthand (replaces wg.Add(1); go func() { defer wg.Done(); ... }())
  • min(), max(), clear() — built-in functions

Review the full file, not just the diff

Before flagging missing imports or undefined references, verify the symbol isn't already defined in unchanged portions of the file. The diff context may not show all existing imports or declarations.

CLI behavior and domain filtering

  • When reviewing command input resolution, explicit CLI args and flags should win over defaults. Do not prompt the user toward a different default when they provided a valid new value; reserve prompts for ambiguous choices and preserve deterministic --no-prompt behavior for CI/scripts.
  • When reviewing flag validation: if a flag was explicitly set (verifiable via cmd.Flags().Changed("<name>")) but the code path would silently ignore it, that is a bug. Reject the combination with a clear error — "success with dropped flags" breaks automation scripts.
  • When filtering AI models or quota data by location, keep location-specific usage data associated with only the models available in that location. Empty or unknown usage data from an unrelated location must not make a model eligible elsewhere; add regression coverage for cross-location quota cases.

Read the full file on GitHub · 35 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 35 lines · 502 tokens per session scan A 0a8f4d3a2188

Subscribe to this mod's changes

azure-dev go.instructions.md is an instructions file published in the GitHub repository Azure/azure-dev (567 stars, last pushed 2d ago), licensed MIT. It adds 502 tokens to every session, about $0.0025 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories