smithery/oodaris

eng-go-cli-developer

Build reliable Go CLI commands with stable outputs and tests.

Installation

$ npx skills add smithery/oodaris --skill eng-go-cli-developer

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/oodaris.

npx skills add smithery/oodaris

Browse all from smithery/oodaris

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version0.2.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,321 B
  • docs SUMMARY.md 89 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Go CLI Developer

Repo anchors (autocodex)

  • CLI_PATH: cmd/autocodex/
  • INTERNAL_PATH: internal/
  • TEST_COMMANDS

- go test ./... - go vet ./... - gofmt -w $(rg --files -g '*.go')

When to use

  • Adding or modifying CLI commands or flags.

Preconditions

  • CLI goals and expected workflows are defined.
  • If contracts must change, STOP and update contracts first.

Inputs to confirm

  • Command structure and flags
  • Expected outputs (human vs JSON)
  • Exit code semantics

Required artifacts

  • Deterministic CLI behavior
  • Help text or examples for new commands
  • Tests for parsing or core flows

Quick path

  • Define flags and output format.
  • Keep CLI thin; move logic to packages.
  • Add tests.

Steps

  1. Implement CLI parsing.
  2. Delegate to internal packages.
  3. Ensure stdout is for output, stderr for logs/errors.
  4. Add tests for parsing/output.

Failure modes and responses

  • Unclear UX: ask for expected CLI workflow.
  • Unstable output: add JSON output and tests.

Definition of done

  • CLI is deterministic, documented, and tested.

Example (minimal)

  • Command: autocodex plugins --action list
  • Output: JSON list of plugins.