Build Release
Produce a production-like git-agent binary with CLIENT_TOKEN, WORKER_URL, and MODEL embedded via scripts/build.sh for manual QA or pre-release verification.
Overview
Build-release is an agent skill for the Ship phase that builds git-agent with embedded credentials through scripts/build.sh for manual or pre-release binary verification.
Install
npx skills add https://github.com/gitagenthq/git-agent-cli --skill build-releaseWhat is this skill?
- Single entry: bash scripts/build.sh loads .env or CI vars then compiles with -ldflags
- Validates CLIENT_TOKEN, WORKER_URL, and MODEL before build fails fast
- Strips debug symbols and writes binary to OUTPUT (default git-agent)
- disable-model-invocation: deterministic build steps without model side trips
- 3 required env vars validated: CLIENT_TOKEN, WORKER_URL, MODEL
Adoption & trust: 1 installs on skills.sh; 68 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You need to exercise git-agent end-to-end but dev builds lack embedded CLIENT_TOKEN, WORKER_URL, and MODEL, so manual testing does not match what users run.
Who is it for?
Maintainers of git-agent who already have .env populated and want a one-command release-style binary before tagging.
Skip if: Greenfield clones without .env secrets, automated CI release pipelines that do not use scripts/build.sh, or cross-compilation matrix needs the readme does not cover.
When should I use this skill?
User needs a fully functional git-agent binary for manual testing or pre-release verification via scripts/build.sh with embedded credentials.
What do I get? / Deliverables
You get a stripped, ldflags-embedded git-agent binary (or custom OUTPUT name) ready for hands-on QA once required env vars validate.
- Compiled git-agent binary (or OUTPUT path)
- Build validation against required env keys
Recommended Skills
Journey fit
Compiling a credentialed release candidate is a ship gate—not feature coding—so the canonical shelf is Ship right before you hand a binary to testers or staging. Launch subphase covers cut builds and release verification artifacts rather than unit tests or security audits alone.
How it compares
Focused compile-and-embed script skill—not a full semantic-versioning or GitHub Releases workflow.
Common Questions / FAQ
Who is build-release for?
Solo maintainers of git-agent who run local or staging verification with the same embedded credentials model as production builds.
When should I use build-release?
Use in Ship launch prep when you need a credentialed binary for manual testing or pre-release verification immediately before distribution.
Is build-release safe to install?
It instructs compiling with secrets from .env via ldflags—never commit .env; review the Security Audits panel on this Prism page and rotate tokens if logs might leak flags.
SKILL.md
READMESKILL.md - Build Release
Build the binary with embedded credentials from `.env`: ```bash bash scripts/build.sh ``` This script: 1. Loads `.env` (or uses CI env vars if already set) 2. Validates that `CLIENT_TOKEN`, `WORKER_URL`, and `MODEL` are present 3. Compiles with `-ldflags` to embed credentials and strip debug symbols 4. Outputs the binary to the name specified by `OUTPUT` (defaults to `git-agent`) If the build fails due to missing env vars, check that `.env` exists and contains the required keys. See `.env.example` for the expected format.