Skill: verify-setup

Purpose

This skill validates a Longhorn developer workspace after initialization. It checks toolchain readiness (Go version, Docker daemon, Dapper/make availability), git remote configuration, and workspace hygiene before development begins.

Usage

bash .opencode/skills/verify-setup/verify_setup.sh [options]

Options

Checks Performed

1. •Go toolchain
   • •Verifies go binary exists and prints version (expects Go ≥ 1.21; configurable via env MIN_GO_VERSION).
2. •Docker daemon
   • •Runs docker info to ensure Docker daemon is reachable.
3. •Dapper/make
   • •Verifies make is available (required for Dapper builds) and warns if dapper binary is missing.
4. •Git remotes
   • •Warns (instead of failing) if upstream remote or its HEAD reference is missing, so the script can run in freshly cloned workspaces.
   • •Warns if origin remote is missing (since PRs normally push to origin).
5. •Workspace cleanliness
   • •Fails if the workspace has uncommitted changes (git status --porcelain), unless SKIP_CLEAN_CHECK=true is set.
6. •Optional PATH sanity
   • •Warns if $GOPATH/bin is not in PATH when Go is installed.

Output

• •Logs are emitted via the shared defensive prelude (ISO timestamps, optional JSON).
• •Exit codes: 0 success, 2 argument errors, 3 environment/tooling issues.
• •On failure, the script prints remediation guidance (e.g., instructions to install Docker or configure upstream).

Example

# Standard run (default is execute)
bash .opencode/skills/verify-setup/verify_setup.sh

# Dry-run preview
bash .opencode/skills/verify-setup/verify_setup.sh --dry-run

# JSON logs for automation
bash .opencode/skills/verify-setup/verify_setup.sh --json-log > verify.log

Notes

• •Requires the shared .opencode/skills/lib/defensive_prelude.sh.
• •Does not modify any files unless future enhancements require caching.
• •Intended to run before major plan execution (e.g., immediately after repo-init).