verify

skills/groundwork/commands/verify.md skills/groundwork/templates/hook.sh.template skills/groundwork/templates/husky-pre-commit.template skills/groundwork/templates/context-check.yml.template

If the agent does not have verification commands, you become the verification step. That is slow and unreliable. verify moves the commands to the top of every context file, wires a pre-commit hook, and stops the agent from shipping you broken diffs.

When to use it

Every repo, every time. If you only run one command after init, run this one.

  • Right after init or document.
  • Test framework changed.
  • New CI pipeline.
  • audit flagged "missing verification".

What it produces

  • Verification section near the top of AGENTS.md (and two-file CLAUDE.md). Fast command in the per-harness pointer files.
  • .context/hooks/check-context.sh: pre-commit hook for repo-specific drift.
  • Hook-runner registration (husky / pre-commit / lefthook) if one is detected. Suggested, not silently installed.
  • The detector wired into pre-commit and CI (.github/workflows/context-check.yml if you use Actions).
  • A test run of every verification command, so you know the baseline.

How it works

  1. Detect. Reads manifests for test, lint, typecheck, build, format.
  2. Ask. Detected commands preselected. You adjust. Pick the fast subset (every change) vs the full set (before done).
  3. Run each command once. Captures pass / fail. If something is failing, you choose: skip, fix now, or include with a "known failing" note.
  4. Update the files. Verification section near the top of each.
  5. Wire the detector. npx @ignitic/groundwork detect --fail-on P0 in pre-commit and CI.
  6. Install the local drift hook. Catches package-manager drift against AGENTS.md, missing ADRs on multi-file commits, ADRs without a Status.
  7. Register with your hook runner, or tell you the one-line install.