SupabaseKnown publishersupabase/supabase-go/.agents/skills/changing-build-and-continuous-integration/SKILL.mdchanging-build-and-continuous-integration
Skill10 starsChanged 44 days agoMITView on GitHub
Guides changes to this repository's build, module and CI machinery rather than the SDK's own code. Use when touching any go.mod, the go.work workspace, the scripts folder, GitHub Actions workflows, the pinned tool modules under tools or the spell-check configuration - including adding a new module, taking on a new dependency or bumping a Go or tool version. Covers workspace wiring for unpublished sibling modules, the published Go version floor versus the CI toolchain, digest pinning, the first-party-actions-only policy and the rule that CI jobs run the same scripts developers run locally.
In this repository7 other files it gives its agents.
The file
Files
The following documents will be helpful:
| Document | For |
DEVELOPMENT.md | How to build, test, lint and spell-check locally with the same scripts CI runs, the one-time npm tooling setup and the supply-chain commit-SHA/checksum pinning approach. |
decisions.md | Deep dive commentaries with both What and Why defined for key decisions that shape the structure of this codebase, including the build and verification machinery. |
standard.md | The canonical definition of "what good looks like" including authoritative guidance on dependencies, licensing, minimum Go version, module versioning and distribution. Frozen: consult it, never edit it (see DEVELOPMENT.md). |
Continuous Integration (CI) runs on GitHub's platform - inspect .github/workflows/ for details, including how commands are directed via scripts/ so that local developers can run exactly what runs in CI.
A new or changed convention should also trigger the recording-decisions skill.
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.