mirror of
https://github.com/garrytan/gstack.git
synced 2026-11-22 16:11:34 +01:00
When Claude Code calls /verify on its own right before `git commit`, gstack now runs one quick check-only command that ends in a single `VERIFY PASS`, `VERIFY FAIL` or `VERIFY skipped: ` line; typing /verify still runs the full skill. Why: since Claude Code 2.1.286 any skill named `verify` is run before every commit, so gstack's fix loop, its first-run notices and a hard stop in repos with no remote landed on ordinary commits. Nothing to do; `gstack-config set verify_before_commit off` turns the check off. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> Review-Finding: p1/specialist-batched#1 reader=specialist-batched Review-Finding: p1/specialist-batched#2 reader=specialist-batched
1.1 KiB
1.1 KiB
- When Claude Code runs /verify right before a commit, it now gets a quick check instead of the full fix loop (GST-3150). Claude Code 2.1.286 and later tell the model to run any skill named
verifybefore every commit that isn't docs-only or tests-only, so gstack's /verify was starting its whole build-and-fix workflow, first-run notices included, on ordinary commits. Now that call runs one command,gstack-checks quick: the repo's existing checks (typecheck, lint) and the tests /ship would pick for the change, with no code edits, no new tests and no questions, ending in one line:VERIFY PASS,VERIFY FAIL, orVERIFY skipped: <reason>. A repo with nooriginremote, check commands you haven't approved yet (type /verify once in that repo to review and approve them), or nothing to run is skipped and the commit goes ahead; a failure makes the model stop and ask you before committing. Typing /verify yourself still runs the full skill. To turn the pre-commit check off, rungstack-config set verify_before_commit off; to stop Claude Code from asking for it at all, install with./setup --prefix, which names the skill /gstack-verify.