OpenParable
Skip to content
← Back to skills

Go Authoring

Development
go-authoring

Go Authoring is an Agent Skill for development published in the nevalang/neva repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when editing, reviewing, or generating Go files in this repository. Covers Go style, local runtime boundaries, lint expectations, and validation.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/nevalang/neva/blob/HEAD/.codex/skills/go-authoring/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/go-authoring, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Go Authoring

Use this skill for changes touching *.go.

Rules

  • Follow the nearest AGENTS.md as scoped source of truth.
  • Source of truth for style and APIs: .golangci.yml, go.mod, and existing code patterns.
  • Treat go.mod as the version ceiling for Go features and stdlib APIs.
  • Prefer modern Go idioms available in the target version over legacy patterns.
  • Always run gofmt on changed Go files.
  • Respect active lints.
  • Never add file-wide or package-wide nolint directives. If suppression is unavoidable, keep it narrowly scoped to the exact line/rule and add a short justification.
  • Prefer Makefile targets for standard checks when applicable.
  • Do not add helper functions or methods unless they abstract at least two meaningful operations or remove real complexity.
  • Never ignore errors, including assignment to _. Handle the error locally or pass it to the caller; choose one outcome such as return (wrapping when useful), log, or panic, but do not both report and continue with the same error.

Runtime Boundaries

  • internal/runtime/*.go: stdlib imports only.
  • internal/runtime/funcs/**: stdlib + internal/runtime.
  • Binary runtime funcs in internal/runtime/funcs/** must receive left and right inputs concurrently; do not add sequential two-input receives in operator helpers or creators.
  • Runtime function changes must include focused unit tests, not only benchmarks or e2e coverage. Prefer table-driven tests that cover the normal path, error path, and meaningful corner cases for each public runtime behavior touched.

Comments

  • Add doc comments for new Go functions and types.
  • For newly generated Go code blocks longer than 3 lines, add a short one-line intent comment when the purpose is not immediately obvious.