How do I install the Lerd Preflight skill?

Run npx skillmds@latest add geodro/lerd-preflight in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Lerd Preflight safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Lerd Preflight?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Lerd Preflight free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Lerd Preflight?

geodro (@geodro) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Lerd Preflight by geodro — Agent Skill

Name: Lerd Preflight
Author: geodro

Lerd Preflight

Run the full local verification gate for lerd before committing — build, test, vet, gofmt, UI tests, installer tests, then install the local build and smoke-test. Use before every commit or PR, and whenever asked to "verify", "check CI locally", or "make sure it's green".

geodro 5d65793 1.9 KB Updated Sep 17, 2026

File contents

lerd preflight

Run the exact checks CI runs, locally, plus install + smoke. Stop at the first failure, report it plainly with the output, and fix before proceeding. Do not report "green" unless every step below actually passed.

1. Format (fastest signal)

gofmt -l .            # must print nothing

If it lists files, run gofmt -w ., then re-check.

2. Build the UI only if it changed

If anything under internal/ui/web/ changed:

make build-ui
make test-ui          # Vitest

Skip both if you only touched Go — the embedded dist/ is reused.

3. Go build, test, vet

CGO_ENABLED=1 go build ./cmd/lerd
CGO_ENABLED=1 go test ./...
CGO_ENABLED=1 go vet ./...

On macOS or a host without libayatana-appindicator, use the nogui path instead: CGO_ENABLED=0 go build -tags nogui ./cmd/lerd (and go test -tags nogui ./...).

4. Installer tests, if install.sh changed

bats tests/installer/installer.bats

5. Install and smoke-test

make install          # → ~/.local/bin/lerd, restarts lerd-ui/watcher

Then actually drive the affected surface — a CLI command, a UI page, an MCP call — and observe the behaviour. A change with a runtime surface is not verified by tests alone. For UI-only work, make install restarts lerd-ui; reload the dashboard and exercise the changed view.

Rules

Never sudo. If a step needs privilege, ask the human to run it.
Never install anywhere but ~/.local/bin/lerd.
If a step is skipped (e.g. UI tests because the UI was untouched), say so explicitly rather than implying full coverage.

---name: lerd-preflightdescription: Run the full local verification gate for lerd before committing — build, test, vet, gofmt, UI tests, installer tests, then install the local build and smoke-test. Use before every commit or PR, and whenever asked to "verify", "check CI locally", or "make sure it's green".---# lerd preflightRun the exact checks CI runs, locally, plus install + smoke. Stop at the firstfailure, report it plainly with the output, and fix before proceeding. Do notreport "green" unless every step below actually passed.## 1. Format (fastest signal)```bashgofmt -l . # must print nothing```If it lists files, run `gofmt -w .`, then re-check.## 2. Build the UI only if it changedIf anything under `internal/ui/web/` changed:```bashmake build-uimake test-ui # Vitest```Skip both if you only touched Go — the embedded `dist/` is reused.## 3. Go build, test, vet```bashCGO_ENABLED=1 go build ./cmd/lerdCGO_ENABLED=1 go test ./...CGO_ENABLED=1 go vet ./...```On macOS or a host without libayatana-appindicator, use the nogui path instead:`CGO_ENABLED=0 go build -tags nogui ./cmd/lerd` (and `go test -tags nogui ./...`).## 4. Installer tests, if install.sh changed```bashbats tests/installer/installer.bats```## 5. Install and smoke-test```bashmake install # → ~/.local/bin/lerd, restarts lerd-ui/watcher```Then actually drive the affected surface — a CLI command, a UI page, an MCP call —and observe the behaviour. A change with a runtime surface is not verified bytests alone. For UI-only work, `make install` restarts `lerd-ui`; reload thedashboard and exercise the changed view.## Rules- Never `sudo`. If a step needs privilege, ask the human to run it.- Never install anywhere but `~/.local/bin/lerd`.- If a step is skipped (e.g. UI tests because the UI was untouched), say so explicitly rather than implying full coverage.

Frequently asked questions