Verify
Run the git-agent CLI monorepo full test suite with `make test` after code changes to catch regressions across Go layers and e2e.
Install
npx skills add https://github.com/gitagenthq/git-agent-cli --skill verifyWhat is this skill?
- Single entry: `make test` runs `go test -count=1` across application, domain, infrastructure, cmd, and e2e
- `-count=1` disables cache so results reflect the latest compile including fresh git-agent binary for e2e
- Targeted reruns: package-scoped `go test ./application/...` or `-run TestName` for one failing test
- E2e failures: read tests under `e2e/` for setup and assertions before diving into production code
- Agent reports back with output, failures, and likely causes
Adoption & trust: 1 installs on skills.sh; 68 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
Recommended Skills
Agent Browservercel-labs/open-agents
Tddmattpocock/skills
Use My Browserxixu-me/skills
Test Driven Developmentobra/superpowers
Verification Before Completionobra/superpowers
Webapp Testinganthropics/skills
Journey fit
Primary fit
Full-suite verification is the canonical Ship gate before merge or release, even though you rerun it whenever you change code during Build. `make test` spans application, domain, infrastructure, cmd, and e2e packages—classic automated testing subphase.
Common Questions / FAQ
Is Verify safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Verify
Run the full test suite: ```bash make test ``` This runs `go test -count=1` across `./application/...`, `./domain/...`, `./infrastructure/...`, `./cmd/...`, and `./e2e/...`. The `-count=1` flag disables caching so results are always fresh. The `e2e` package builds the `git-agent` binary once at the start — any code changes made before running this skill will be compiled in automatically. If a specific package is failing, re-run just that package: ```bash go test ./application/... go test ./infrastructure/config/... go test ./e2e/... ``` To run a single test by name: ```bash go test ./application/... -run TestCommitService_NoStagedChanges ``` If an e2e test fails, read the failing test file in `e2e/` to understand the setup and assertions before investigating the source code. Report back with the test output, highlighting any failures and their likely cause.