
Build Release
- 2 installs
- 78 repo stars
- Updated August 4, 2026
- gitagenthq/git-agent-cli
Build-release is an agent skill that builds git-agent with embedded credentials through scripts/build.sh for manual or pre-release binary verification.
About
Build-release is an agent skill for the git-agent CLI that runs scripts/build.sh to compile a fully functional binary with embedded credentials from .env or CI—CLIENT_TOKEN, WORKER_URL, and MODEL—using linker flags and stripped symbols for realistic manual testing or pre-release checks. Solo builders shipping an agent-powered git tool use it when they need a binary that behaves like production without juggling export commands each time. The skill is intentionally narrow: validate env, compile, name output via OUTPUT, and consult .env.example when keys are missing. It assumes you already configured worker endpoints and tokens elsewhere; it does not replace signing, store submission, or automated test matrices.
- 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
Build Release by the numbers
- 2 all-time installs (skills.sh)
- Ranked #199 of 248 Release Management skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/gitagenthq/git-agent-cli --skill build-releaseAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 78 |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | gitagenthq/git-agent-cli ↗ |
What it does
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.
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 you get
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
By the numbers
- 3 required env vars validated: CLIENT_TOKEN, WORKER_URL, MODEL
Files
Build the binary with embedded credentials from .env:
bash scripts/build.shThis 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.
Related skills
How it compares
Focused compile-and-embed script skill—not a full semantic-versioning or GitHub Releases workflow.
FAQ
Who is build-release for?
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.