Individual skill

go-cli-errors-observability

Design and review recoverable Go CLI errors, exit semantics, structured logging, debug modes, traces, profiles, redaction, and user-consented diagnostic bundles. Use when a CLI needs actionable failures, safe support evidence, production troubleshooting, or observability that does not corrupt command output or expose secrets.

plugins/LVTD-LLC/skills/skills/go-cli-errors-observability/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,533
Repository last updated: Nov 6, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai-coding Repository topic
awesome Repository topic
awesome-list Repository topic
codex Repository topic
codex-plugins Repository topic
openai Repository topic
codex-skill Repository topic
codex-skills Repository topic
marketplace Repository topic
codex-marketplace Repository topic
go,golang,cli,errors,observability,logging,diagnostics Declared skill tag
design Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,161 bytes
agents/openai.yamlasset · 255 bytes
guidelines.mddoc · 1,520 bytes
references/errors-observability/examples.mddoc · 1,675 bytes
references/errors-observability/knowledge.mddoc · 3,041 bytes
references/errors-observability/rules.mddoc · 2,206 bytes
workflows/add-safe-diagnostics.mddoc · 1,528 bytes
workflows/design-error-recovery.mddoc · 974 bytes

Read excerpt


# Go CLI Errors and Observability

Design failures for recovery first, then add the minimum safe evidence needed to
diagnose them. Keep internal detail out of the normal user contract.

## Core Workflow

1. Classify failures by user action, dependency, cancellation, and internal defect.
2. Preserve machine-checkable causes with wrapping, types, or sentinels.
3. Map causes to concise user messages and stable exit behavior at the boundary.
4. Assign one terminal owner to render, log, and map each failure.
5. Preserve material cleanup failures without hiding the primary cause.
6. Add opt-in verbosity and structured logs on stderr or a dedicated sink.
7. Allowlist and redact diagnostic evidence; require consent before collection or upload.