name	build-run
description	Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.
license	MIT
metadata	{"mode":"verify","purpose":"build-run"}

Build and Run

When to Use

Confirm the codebase compiles, reproduce a runtime issue locally, or validate environment-dependent changes.

Rules

Do not use production credentials or external services unless the user provides safe mocks/stubs.
Use source setTestEnv.sh for local env needed by tests or the app.
Prefer reproducible, minimal commands and capture key output lines.

Commands

Compile: go build -v ./...
Format: go fmt ./...
Vet: go vet -v ./...
Tidy deps: go mod tidy
Run tests that reproduce an issue: source setTestEnv.sh && go test -run <TestName> ./pkg/path
Start example app: cd example2/cmd/app && go run main.go (use with test env)

Output

Result: success or failure.
Key logs: first relevant error or stack lines.
Minimal repro: 1-3 commands.
Next steps: which logs/files to inspect or which mocks to add.

Examples

"Does the project compile?" - run go build -v ./... and report.
"Reproduce failing integration test X" - provide commands and first failing lines.

Related Skills

test-runner, ci-orchestrator, fix-suggester

References

AGENTS.md (build and run commands), setTestEnv.sh, llms.txt

Más de este repositorio

mismo repositorio

ci-orchestrator

pilinux/gorest

Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.

2026-06-24502

linter-runner

pilinux/gorest

Execute repository linters and surface highest-priority issues with minimal, targeted fixes.

2026-06-24502

ast-introspection

pilinux/gorest

Use Go AST-aware analysis to enumerate symbols, extract signatures, and propose mechanically safe refactors (read-only by default).

2026-02-19502

code-formatter

pilinux/gorest

Apply repository-standard formatting to minimize diff noise and meet linter expectations.

2026-02-19502

code-navigation

pilinux/gorest

Rapid, focused navigation to locate definitions/usages and map the impact of proposed changes.

2026-02-19502

config-loader-helper

pilinux/gorest

Diagnose configuration-related failures, enumerate required env vars, and guide safe local test setup (no secrets).

2026-02-19502

name	build-run
description	Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.
license	MIT
metadata	{"mode":"verify","purpose":"build-run"}

Build and Run

When to Use

Confirm the codebase compiles, reproduce a runtime issue locally, or validate environment-dependent changes.

Rules

Do not use production credentials or external services unless the user provides safe mocks/stubs.
Use source setTestEnv.sh for local env needed by tests or the app.
Prefer reproducible, minimal commands and capture key output lines.

Commands

Compile: go build -v ./...
Format: go fmt ./...
Vet: go vet -v ./...
Tidy deps: go mod tidy
Run tests that reproduce an issue: source setTestEnv.sh && go test -run <TestName> ./pkg/path
Start example app: cd example2/cmd/app && go run main.go (use with test env)

Output

Result: success or failure.
Key logs: first relevant error or stack lines.
Minimal repro: 1-3 commands.
Next steps: which logs/files to inspect or which mocks to add.

Examples

"Does the project compile?" - run go build -v ./... and report.
"Reproduce failing integration test X" - provide commands and first failing lines.

Related Skills

test-runner, ci-orchestrator, fix-suggester

References

AGENTS.md (build and run commands), setTestEnv.sh, llms.txt