go
Installation
SKILL.md
User-invoked full delivery: continue until verified or externally blocked.
Exit contract
Resolve objective, non-inferable guardrails, repository checks plus real-entrypoint behavior, requested commit/remote/PR/CI delivery, and stop condition.
Loop
Inspect -> verify -> repair -> repeat until verification passes.
- Inspect the whole branch and endpoint: committed, staged, unstaged, untracked. Exclude unrelated files.
- Run repository-native checks. Frontend normally includes focused tests,
bun run type:check,bun run lint:fix; Go uses documented tests, vet, build. - Exercise every material runnable change through its real user or public entrypoint, including one credible break or recovery path. Tests do not replace this.
- For a customer-facing surface, inspect the rendered or terminal result, states, accessibility, errors, and relevant viewports/platforms. Apply the PR visual evidence gate, for all visible changes.
- Review once for objective, guardrails, semantic density, and credible risk. Repair, invalidate, and replay affected evidence.
- If the change claims measurable impact, repeat the same baseline/candidate scenario; do not invent useless benchmarks.
For dependency version upgrades, verify lockfile, clean install/build, and every affected call site against current primary documentation.