gitagenthq/git-agent-cli
3 skills3 installs204 starsGitHub
Install
npx skills add https://github.com/gitagenthq/git-agent-cliSkills in this repo
1Build ReleaseBuild-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.1installs2Use Git Agentuse-git-agent documents how solo builders wire the git-agent CLI into daily Git workflows. The tool auto-stages changes (unless disabled), plans splits into atomic commits with an LLM, and writes conventional commit messages aligned to your intent. Configuration layers global flags, per-repo git config keys, and a YAML config file with environment expansion, so you can standardize models and endpoints across machines without baking secrets into the repo. Dry-run lets you preview messages; amend regenerates the latest commit text; no-stage respects an already-curated index. It fits indie teams who want agent-assisted commits without abandoning normal git-agent commit ergonomics or provider choice.1installs3VerifyVerify is a git-agent-cli repository skill that tells your coding agent exactly how to validate the whole Go project after edits. Solo maintainers of CLI tools often skip e2e because it is slow or unclear; this skill standardizes on `make test`, which exercises application, domain, infrastructure, command, and end-to-end packages with uncached runs so the freshly built `git-agent` binary is what e2e actually hits. When something fails, the procedure narrows scope—rerun a single package or a named test—and for e2e regressions it explicitly prioritizes reading the failing spec in `e2e/` before chasing implementation details. That makes it a lightweight quality gate aligned with indie shipping habits: one command, fresh results, structured reporting back to you. Complexity is beginner-friendly if Go and Make are already on the machine. It does not replace linters or security scans; it confirms behavioral contracts across the repo layers your users depend on.1installs