agentleFS
BariBariGoodBariBariGood/manzanas/.agents/skills/build-and-test/SKILL.md

build-and-test

Skill22 starsChanged 3 months agoApache-2.0View on GitHub

Build, lint, and test manzanasd - the Go toolchain gate every PR must pass, the CI matrix (Linux + macOS), and how to build the simbridge helper. Use before opening any PR to this repo or when debugging CI failures.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep macOS-leg tests fast and never add steps that boot simulators or need sudo there.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Build and test manzanasd

Pure Go (module github.com/BariBariGood/manzanas, needs a recent stable Go toolchain). Everything below runs on Linux — no Mac required for the core gate.

The PR gate — run ALL of these before opening a PR

go build ./...
go vet ./...
go test ./...
gofmt -l .        # must print NOTHING; fix with gofmt -w on the listed files

make build produces bin/manzanasd, bin/manzanas, bin/manzanas-broker; make lint = vet + gofmt check. Unit tests are Linux-safe by design (mock registry, httptest fake daemons); code that needs macOS is behind interfaces (e.g. warm.Host) with fakes — keep it that way.

CI (.github/workflows/ci.yml)

The test job runs the same four commands on a two-leg matrix (ubuntu-latest + macos-latest).

Notes:

  • setup-go uses go-version: "stable", NOT 1.22 — the Go 1.22 linker emits binaries without LC_UUID, which macOS 26 refuses to execute. Don't pin the version down.
  • Keep macOS-leg tests fast and never add steps that boot simulators or need sudo there.

Other workflows: release.yml (GoReleaser on v* tags), site.yml (site/ npm build; only triggers on site changes).

simbridge (warm-actions helper)

CI cannot build it (needs macOS + Xcode + AXe frameworks). Build on a Mac:

helpers/simbridge/build.sh ~/bin/simbridge          # AXe frameworks at ~/axe/Frameworks
AXE_FRAMEWORKS=/opt/axe/Frameworks helpers/simbridge/build.sh   # other installs

The binary rpath-pins the frameworks dir it was built against — build on (or for) the host that runs it, one binary per architecture. If the shipped .swiftmodules don't match the local Swift compiler, rebuild the AXe frameworks first (see docs/actions-warm.md).

Conventions

  • Protocol changes: proto/ Go types are the source of truth; proto/PROTOCOL.md describes semantics. Within v0 changes must be additive. Same rule for the journal format (docs/journal.md).
  • The daemon owns all stateful policy in Go (unit-testable on Linux); helpers like simbridge stay deliberately dumb.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.