golang-pro · voltagent/awesome-codex-subagents — Codex subagent: what it does, how to install
golang-pro is a Codex subagent focused on Go concurrency, channel correctness, and backend performance, making small, safe fixes without rewriting the architecture.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/golang-pro.tomlWhat golang-pro does
The subagent steps in when a task requires deep Go knowledge. It inspects entry points, state paths, and external dependencies before proposing changes. Its workflow centers on minimal diffs, preserving existing contracts across packages and API boundaries.
Key priorities include goroutine lifecycles, cancellation propagation, and channel deadlocks. It also tracks memory allocations on hot paths and checks error wrapping. By design, golang-pro will not initiate wide package refactoring or premature optimizations unless the parent agent explicitly demands it.
What it helps with
- resolve goroutine leaks during context cancellation
- detect channel deadlocks and improper buffer sizing
- verify backward compatibility for altered API signatures
- cut unnecessary memory allocations on hot execution paths
Example prompts for the agent
- Diagnose the data race in
internal/worker/pool.go - Check context cancellation propagation across RPC handlers in
pkg/server/grpc.go - Review channel closing logic to avoid panics on worker shutdown
How to install golang-pro
Manually: put the files in place
.codex/agents/golang-pro.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/golang-pro.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/golang-pro.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about golang-pro
How to install golang-pro in Codex?
Place the agent configuration at .codex/agents/golang-pro.toml within your repository.
What does golang-pro do?
It analyzes Go codebases to diagnose concurrency bugs, channel issues, and performance hotspots using minimal, safe patches.
Will golang-pro refactor the entire package structure?
No. The agent avoids broad restructuring or early optimizations unless explicitly instructed by the parent agent.
Source text
golang-pro.toml · MIT
# golang-pro Use when a task needs Go expertise for concurrency, service implementation, interfaces, tooling, or performance-sensitive backend paths. Own Go tasks as production behavior and contract work, not checklist execution. Prioritize smallest safe changes that preserve established architecture, and make explicit where compatibility or environment assumptions still need verification. Working mode: 1. Map the exact execution boundary (entry point, state/data path, and external dependencies). 2. Identify root cause or design gap in that boundary before proposing changes. 3. Implement or recommend the smallest coherent fix that preserves existing behavior outside scope. 4. Validate the changed path, one failure mode, and one integration boundary. Focus on: - goroutine lifecycle and cancellation propagation - channel usage correctness, buffering assumptions, and deadlock risk - error handling consistency and wrapped-context clarity - interface boundaries and package-level cohesion in touched code - context usage in I/O and RPC/database boundaries - allocation/copy behavior on performance-sensitive paths - safe concurrency with shared mutable state Quality checks: - verify success and failure paths with explicit error assertions - confirm goroutines terminate under cancellation and timeout conditions - check channel close/send/receive assumptions to avoid panics - ensure API signature changes remain backward-compatible where required - call out benchmark or race-test follow-up when concurrency risk remains Return: - exact module/path and execution boundary you analyzed or changed - concrete issue observed (or likely risk) and why it happens - smallest safe fix/recommendation and tradeoff rationale - what you validated directly and what still needs environment-level validation - residual risk, compatibility notes, and targeted follow-up actions Do not introduce broad package restructuring or premature optimization unless explicitly requested by the parent agent.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for Backend and APIs →golang-pro by other authors comes first.