Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

building-go-binaries

Sterne0

Forks0

Aktualisiert7. März 2026 um 18:30

Build Go binaries for local development or release. Use when you need to compile the project, troubleshoot build failures, or understand the build pipeline.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

MrPointer

MrPointer/agentcoven

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	building-go-binaries
description	Build Go binaries for local development or release. Use when you need to compile the project, troubleshoot build failures, or understand the build pipeline.

Building Go Binaries

All commands run from the Go module root (cova/).

Local Development Build

task build

Builds a snapshot binary for the current platform via GoReleaser. Output goes to ./bin/. This is the only command you need for local builds.

How It Works

Task wraps GoReleaser in snapshot mode (no git tag required, single target)
GoReleaser config: .goreleaser.yaml
Task runner config: Taskfile.yml
Version info is injected via ldflags at build time (see main.go for the variables)

When Builds Fail

Check that go mod tidy has been run (GoReleaser runs it as a pre-hook in release mode)
Check for compilation errors in the go build output
For GoReleaser-specific issues, read .goreleaser.yaml for the current configuration

Mehr aus diesem Repository

gleiches Repository

developing-cli-apps

MrPointer/agentcoven

Develop CLI applications in Go. Use when creating or modifying CLI commands, adding flags or arguments, implementing command workflows, building interactive prompts, handling signals and exit codes, or working with stdin/stdout/stderr. Currently uses Cobra for command structure and Huh for interactive UI.

2026-03-140

linting-go-code

MrPointer/agentcoven

Lint and format Go code. Use when you need to run linters, fix lint errors, format code, or understand why a linter is complaining.

2026-03-070

testing-go-code

MrPointer/agentcoven

Run Go unit tests, coverage reports, and benchmarks. Use when you need to run tests, check coverage, run benchmarks, or regenerate mocks after interface changes.

2026-03-070

writing-go-code

MrPointer/agentcoven

Apply Go coding standards when writing or modifying Go code. Use when implementing functions, using dependency injection, handling errors idiomatically, or working with interfaces. For test conventions, use the `writing-go-tests` skill instead.

2026-03-070

writing-go-tests

MrPointer/agentcoven

Write Go tests following project conventions. Use when creating test files, writing unit or integration tests, choosing mocks, or setting up test fixtures. Covers test naming, assertions, mock usage, table-driven patterns, and common pitfalls.

2026-03-070

name	building-go-binaries
description	Build Go binaries for local development or release. Use when you need to compile the project, troubleshoot build failures, or understand the build pipeline.

Building Go Binaries

All commands run from the Go module root (cova/).

Local Development Build

task build

Builds a snapshot binary for the current platform via GoReleaser. Output goes to ./bin/. This is the only command you need for local builds.

How It Works

Task wraps GoReleaser in snapshot mode (no git tag required, single target)
GoReleaser config: .goreleaser.yaml
Task runner config: Taskfile.yml
Version info is injected via ldflags at build time (see main.go for the variables)

When Builds Fail

Check that go mod tidy has been run (GoReleaser runs it as a pre-hook in release mode)
Check for compilation errors in the go build output
For GoReleaser-specific issues, read .goreleaser.yaml for the current configuration