Go

Skill jscraik/Agent-Skills/Skills/agent-ops/go

Governed skill foundry and Skills SDK for Codex/AI coding agents: author, validate, evaluate, and sync runtime projections through ask.

Install

npx -y skills add jscraik/Agent-Skills --skill go

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Best practices for working with Go codebases. Use when writing, debugging, or exploring Go code, including reading dependency sources and documentation.

SKILL.md

3.0 KB, as published. Nobody here has run it

When to use
Required inputs
Deliverables
Style
Error Flow
Examples
Failure mode
Gotchas

When to use

Use for Go code authoring and review tasks.
Use when package boundaries and error handling need tightening.

Required inputs

Package and file scope.
Expected API behavior.
Runtime/performance constraints.

Deliverables

Idiomatic Go changes.
Wrapped, actionable errors.
Minimal API churn outside requested scope.

Style

Keep functions small and package-focused.
Return concrete structs from constructors when interfaces are unnecessary.
Prefer composition over deep embedding chains.

Error Flow

Return wrapped errors with %w for traceability.
Avoid panic in library code.
Check and handle every returned error.

Examples

func ParsePort(value string) (int, error) {
	port, err := strconv.Atoi(value)
	if err != nil {
		return 0, fmt.Errorf("parse port %q: %w", value, err)
	}
	return port, nil
}

Failure mode

If API compatibility risk is high, keep signatures stable and narrow the patch.

Gotchas

Silent ignored errors usually become runtime bugs.

Skill	When to use
[[rust-pro]]	Systems programming with similar error-propagation and ownership concerns
[[he-fix-bugs]]	Triage Go runtime errors with evidence-first diagnosis

Philosophy

Optimize for clear, verifiable outcomes with the minimum necessary changes.
Keep guidance deterministic so repeated runs produce consistent decisions.

Procedure

Confirm scope, constraints, and required inputs before edits.
Apply focused changes tied directly to the requested outcome.
Re-run the highest-signal validations and capture concrete evidence.

Validation

Run the relevant local checks for touched files and workflow contracts.
Fail fast: stop at the first blocking validation failure and report exact evidence.
Re-run checks after fixes and record residual risk if any remains.

Constraints

Redact secrets, tokens, credentials, and sensitive data by default.
Do not expand scope beyond the request unless explicitly asked.
Prefer safe, reversible edits over broad refactors.

Anti-patterns

Skipping validation after making changes.
Applying broad refactors to solve narrow issues.
Assuming behavior without evidence from current checks.

References and assets

Open deep guidance: Infrastructure/references/deep-guidance.md
Read when: the task needs advanced edge cases, migration-safe patterns, or runtime-specific nuance beyond the core checklist.

Go