Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

go-debug-flow

Sterne4

Forks0

Aktualisiert14. Juni 2026 um 21:10

Minimal Go build, test, debug, and lint workflow for pacman.

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

polkiloo

polkiloo/pacman

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	go-debug-flow
description	Minimal Go build, test, debug, and lint workflow for pacman.

Go Debug Flow

Start narrow. Run package-level tests before broader targets.

Identify the package from changed files.
Run targeted tests:
- go test -count=1 ./internal/controlplane
- go test -count=1 ./internal/agent
- go test -count=1 ./tools/jepsenctl/cmd
For a specific test, use -run '^TestName$' -v.
For flakes or race-prone logic, rerun the smallest package/test with -count=20 before widening scope.
Use go test ./... only after targeted tests pass or when shared contracts changed.
Build binaries with repo Make targets when packaging/link flags matter; otherwise go test usually compiles enough.
Run make lint or golangci-lint run when touching style-sensitive or shared packages.

Debugging hints:

Preserve context cancellation and deadlines in tests.
Prefer table-driven cases for state-machine and API validation.
Use existing test helpers in the package before adding new fixtures.
Check generated/OpenAPI/package artifacts only when the touched subsystem owns them.

Mehr aus diesem Repository

gleiches Repository

change-approval-gate

polkiloo/pacman

Require a concrete change explanation and explicit user approval before modifying a repository, then implement and verify the approved scope. Use whenever Codex is asked to create, edit, delete, generate, format, refactor, fix, upgrade, or otherwise mutate repository files, dependencies, configuration, tests, documentation, build artifacts, or version-control state.

2026-06-304

repo-map

polkiloo/pacman

Repository layout for the pacman Go PostgreSQL HA cluster manager.

2026-06-174

github-actions-triage

polkiloo/pacman

Use when inspecting GitHub Actions, CI failures, failed Go tests, workflow logs, or build/lint/test errors. Avoid reading full logs; summarize failed jobs and inspect only relevant snippets.

2026-06-144

api-contract

polkiloo/pacman

Maintain PACMAN-native and Patroni-compatible API contracts.

2026-06-144

cluster-state-machine

polkiloo/pacman

PACMAN domain rules for cluster state transitions and operation history.

2026-06-144

control-plane-quorum

polkiloo/pacman

Rules for PACMAN control-plane quorum, leases, epochs, fencing, and split-brain prevention.

2026-06-144

name	go-debug-flow
description	Minimal Go build, test, debug, and lint workflow for pacman.

Go Debug Flow

Start narrow. Run package-level tests before broader targets.

Identify the package from changed files.
Run targeted tests:
- go test -count=1 ./internal/controlplane
- go test -count=1 ./internal/agent
- go test -count=1 ./tools/jepsenctl/cmd
For a specific test, use -run '^TestName$' -v.
For flakes or race-prone logic, rerun the smallest package/test with -count=20 before widening scope.
Use go test ./... only after targeted tests pass or when shared contracts changed.
Build binaries with repo Make targets when packaging/link flags matter; otherwise go test usually compiles enough.
Run make lint or golangci-lint run when touching style-sensitive or shared packages.

Debugging hints:

Preserve context cancellation and deadlines in tests.
Prefer table-driven cases for state-machine and API validation.
Use existing test helpers in the package before adding new fixtures.
Check generated/OpenAPI/package artifacts only when the touched subsystem owns them.