Run any Skill in Manus with one click

golang-build-deploy

Stars0

Forks0

UpdatedJune 7, 2026 at 08:23

Build, package, release, containerize, deploy, or audit Go applications and CLIs. Use for Golang build flags, module release checks, cross-compilation, Dockerfiles, CI/CD, version metadata, graceful shutdown, runtime configuration, security updates, production deployment plans, or reviewing existing Go release/deployment readiness.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Zate

Zate/golang-development

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

File Explorer

3 files

SKILL.md

readonly

name	golang-build-deploy
description	Build, package, release, containerize, deploy, or audit Go applications and CLIs. Use for Golang build flags, module release checks, cross-compilation, Dockerfiles, CI/CD, version metadata, graceful shutdown, runtime configuration, security updates, production deployment plans, or reviewing existing Go release/deployment readiness.

Go Build And Deploy

Build Workflow

Inspect existing build/release surfaces first: Makefile, CI workflows, Dockerfiles, goreleaser, task files, go.mod, and deployment manifests.
Build with the standard go tool unless the repo has a stronger wrapper. Prefer reproducible commands over hidden local state.
Keep build metadata explicit: version, commit, date, dirty state, target OS/arch, and module dependency info where useful.
For services, verify graceful shutdown, context propagation, health/readiness checks, config loading, logging, and metrics/tracing hooks already used by the repo.
For containers, prefer small multi-stage builds, non-root runtime users, CA certificates/timezone needs, and no source/toolchain in final image.
Before release/deploy, run tests, vet/lint, vulnerability checks when available, and a local smoke test of the built binary.

Audit Workflow

Inspect build scripts, CI, Dockerfiles, release config, runtime config, service startup/shutdown, and deployment manifests before judging.
Check reproducibility, version metadata, module hygiene, vulnerability scanning, container runtime user, image contents, and smoke-test coverage.
For services, flag missing graceful shutdown, HTTP timeouts, health/readiness checks, config validation, logging, metrics/tracing, or secret leakage.
Report release blockers separately from hardening recommendations.
Pair with golang-code-audit when producing a full findings-first review.

Load References

Read references/build-release-deploy.md for command patterns, Dockerfile shape, CI gates, and deployment checklist.
Pair with the companion golang-quality-linting skill for verification and the companion golang-testing skill for release test strategy.

More from this repository

same repository

golang-architecture-patterns

Zate/golang-development

Design or audit Go application architecture, package boundaries, dependency direction, interfaces, adapters, repositories, services, HTTP handlers, concurrency boundaries, and maintainable design patterns. Use for Golang service design, refactors, domain layering, dependency injection, ports/adapters, repository patterns, functional options, API design, concurrency architecture, or reviewing existing Go architecture for coupling and maintainability risks.

2026-06-070

golang-code-audit

Zate/golang-development

Audit existing Go and Golang codebases, pull requests, diffs, packages, services, CLIs, tests, build pipelines, and repository layouts against idiomatic Go development guidance. Use when reviewing, auditing, assessing, evaluating, inspecting, checking best-practice compliance, finding violations, identifying risks, or producing findings for already-built Go code.

2026-06-070

golang-development-workflow

Zate/golang-development

Route Go and Golang development work into the right build or audit workflow. Use for broad Go tasks such as building features, implementing changes, refactoring, planning, reviewing, auditing, assessing an existing codebase, checking against Go best practices, or deciding which Golang Development skills apply.

2026-06-070

golang-implementation-idioms

Zate/golang-development

Implement or audit idiomatic Go code using effective naming, errors, context, interfaces, generics, nil handling, slices/maps, documentation comments, and standard library conventions. Use when writing, refactoring, cleaning, or reviewing Golang code; reducing nesting; improving API ergonomics; checking idiomatic implementation style; or finding non-idiomatic Go in existing code.

2026-06-070

golang-planning-layout

Zate/golang-development

Plan or audit idiomatic Go modules, repository layout, package boundaries, command structure, migration strategy, and implementation plans. Use when working on Go or Golang projects before adding packages, moving code, choosing cmd/internal/pkg layout, splitting modules, introducing workspaces, writing a multi-step implementation plan, or reviewing an existing repo for layout and package-boundary problems.

2026-06-070

golang-quality-linting

Zate/golang-development

Verify, improve, or audit Go code quality with gofmt, goimports, go vet, static analysis, golangci-lint, security checks, code review, lint configuration, and completion verification. Use when reviewing Golang changes, fixing linter failures, setting up golangci-lint, deciding quality gates, auditing existing quality practices, or checking whether Go code is ready to ship.

2026-06-070

name	golang-build-deploy
description	Build, package, release, containerize, deploy, or audit Go applications and CLIs. Use for Golang build flags, module release checks, cross-compilation, Dockerfiles, CI/CD, version metadata, graceful shutdown, runtime configuration, security updates, production deployment plans, or reviewing existing Go release/deployment readiness.

Go Build And Deploy

Build Workflow

Inspect existing build/release surfaces first: Makefile, CI workflows, Dockerfiles, goreleaser, task files, go.mod, and deployment manifests.
Build with the standard go tool unless the repo has a stronger wrapper. Prefer reproducible commands over hidden local state.
Keep build metadata explicit: version, commit, date, dirty state, target OS/arch, and module dependency info where useful.
For services, verify graceful shutdown, context propagation, health/readiness checks, config loading, logging, and metrics/tracing hooks already used by the repo.
For containers, prefer small multi-stage builds, non-root runtime users, CA certificates/timezone needs, and no source/toolchain in final image.
Before release/deploy, run tests, vet/lint, vulnerability checks when available, and a local smoke test of the built binary.

Audit Workflow

Inspect build scripts, CI, Dockerfiles, release config, runtime config, service startup/shutdown, and deployment manifests before judging.
Check reproducibility, version metadata, module hygiene, vulnerability scanning, container runtime user, image contents, and smoke-test coverage.
For services, flag missing graceful shutdown, HTTP timeouts, health/readiness checks, config validation, logging, metrics/tracing, or secret leakage.
Report release blockers separately from hardening recommendations.
Pair with golang-code-audit when producing a full findings-first review.

Load References

Read references/build-release-deploy.md for command patterns, Dockerfile shape, CI gates, and deployment checklist.
Pair with the companion golang-quality-linting skill for verification and the companion golang-testing skill for release test strategy.