Update to Go: Production Engineering

{
  "description": "Use for general Go diff/PR review. Do not use when distributed-systems or fintech correctness dominates.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 257
    },
    {
      "relative_path": "evals.json",
      "size_in_bytes": 15037
    },
    {
      "relative_path": "references/finding-standard.md",
      "size_in_bytes": 501
    },
    {
      "relative_path": "skill.json",
      "size_in_bytes": 2351
    }
  ],
  "name": "review-go-engineering-change",
  "skill_md_contents": "---\nname: review-go-engineering-change\ndescription: \"Use for general Go diff/PR review. Do not use when distributed-systems or fintech correctness dominates.\"\nlicense: Apache-2.0\ncompatibility: \"Go 1.24 or newer; changed repository contracts outrank generic conventions.\"\n---\n\n# Review a Go engineering change\n\nReview behavior created by the diff, not resemblance to a checklist.\n\n## Establish scope\n\nInspect changed code and only the callers, callees, schemas, configs, tests, and history needed to determine the changed contract. State the input, decision, side effects, output, and compatibility surfaces.\n\nLoad the focused engineering skills for the risks actually present; this review skill sets finding quality and precedence rather than duplicating their conditional guidance.\n\n## Trace applicable risk\n\n- Language: aliasing, mutation, nil and zero values, error identity, interface method sets, generics, overflow.\n- API: exported behavior, serialization, config defaults, mixed versions, migrations, rollback.\n- Boundary: validation, authorization, body/stream lifetime, cancellation, protocol status, shutdown.\n- Verification: missing oracle for a changed invariant, nondeterminism, mocks standing in for claimed dependency semantics.\n- Performance: unbounded allocation or work on a reachable path; do not report speculative micro-optimization.\n- Security: attacker-controlled input reaching authority, storage, execution, filesystem, or network destinations.\n- Operations: readiness, telemetry, overload, recovery, and incident ambiguity.\n\nWhen concurrency, persistence, messaging, leases, or money movement dominates the change, route to the corresponding distributed or fintech review skill.\n\n## Write findings\n\nEach finding needs a tight changed line, trigger, impact, causal mechanism, and smallest correction. Rank severity from impact and plausible reachability. Report defects and material risks; omit preferences unless requested. Do not demand tests, interfaces, comments, abstractions, or retries by default.\n\nRead [references/finding-standard.md](references/finding-standard.md) before finalizing findings.\n\n## Output contract\n\nLead with actionable findings in descending severity. If none exist, say so and name only significant residual uncertainty. Never claim a check ran when it did not.\n"
}