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
- thanhthanh11/claudeCodetheir own version, first seen Oct 25, 2026
- google/boringssltheir own version, first seen Oct 20, 2026
- microsoft/agent-frameworktheir own version, first seen Oct 13, 2026
- huynhsontung/Screenboxtheir own version, first seen Oct 8, 2026
- dotnet/runtimetheir own version, first seen Oct 8, 2026
- microsoft/wassettetheir own version, first seen Aug 5, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- dotnet/runtime★ 18ksame name
- microsoft/agent-framework★ 15ksame name
- huynhsontung/Screenbox★ 4.7ksame name
- google/boringssl★ 2.3ksame name
- microsoft/wassette★ 977same name
- thanhthanh11/claudeCode★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- broker-federationSkill
- drive-a-mirrored-iphoneSkill
- journal-evidence-exportSkill
- lease-and-drive-a-simSkill
- park-thaw-semanticsSkill
- run-evalsSkill
- run-the-daemonSkill
- ui-audit-and-predicatesSkill
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
- Distinctive: line 36
Keep macOS-leg tests fast and never add steps that boot simulators or need sudo there.
“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.
Files
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 filesmake 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-gousesgo-version: "stable", NOT 1.22 — the Go 1.22 linker emits binaries withoutLC_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 installsThe 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.mddescribes 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.
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
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.

