krishpunjabi.com ~/skills

← all commands

/verifier

/verifier agents

Verifies an implementation session: checks its handoff's claims against git, tests and CI, reviews the diff, updates docs/board/issues, reconciles deviations via consult-plan, and ends with the next task. Use after an implementer or manager finishes.

Install

Install just this, from a clone of the repo. Anything it needs comes with it.

./scripts/install-skills.sh --skill verifier   # bash, Git Bash, macOS, Linux
.\scripts\install-skills.ps1 -Skill verifier   # Windows PowerShell

Needs: consult-plan, next, update-progress, the guard-git hook (installed with it).

What it does

Verifies an implementation session and closes the loop.

  • maxTurns: 120.
  • The guard hook doesn't apply to it.

How to invoke

Agent(subagent_type="verifier", prompt=…)

You pass: - Handoff path (or saved manager report path).

  • Whether it may answer interview-style questions on your behalf.
  • review-done=yes|no (default no; yes = a manager already reviewed and reran tests).
  • decisions (ask|assume, default ask).
  • User-answered D<k> (settled; never re-decided).

How it works

  1. Runs update-progress end to end: claims vs git log, tests, CI, code review (skipped if review-done=yes), docs/board/issue updates. Code review is inline, on two axes (standards + spec), with no reviewer subagents.
  2. Deviations: if authorized, answers consult-plan itself from the written plan and lists every Q → A; if not, records the deviation and leaves the plan untouched.
  3. Calls next.

Design principles

  • A claim is not evidence, so every handoff claim is checked against git log, tests and CI.
  • Code review is inline on two axes (standards + spec) with no reviewer subagents.
  • A deviation changes the plan only when you authorized it to answer for you.

Shared context for these principles: Matt Pocock's video.

Use cases

  • Closing the loop after an implementer or manager finishes in a meta-orchestrator run.
  • Checking a handoff by hand before you trust it.

Tips

  • Pass review-done=yes when a manager already reviewed and reran tests, to skip a second review.
  • Without permission to answer for you, deviations come back as manual steps rather than plan changes.

Example

One issue through planner, manager and verifier, as an orchestrator (or you) calls them. The manager briefs and spawns its own implementer inside its turn, so only the manager's report comes back. You push and merge in between:

Agent(subagent_type="planner", prompt="~/code/myrepo; exclusions: label needs-design; order: priority label") (+7 lines)
Issue: #31 Add CSV export (checklist: 3 items) Key files: src/export.py, tests/test_export.py Constraints: none Branch: feat/issue-31-csv-export Gotchas: none Size, shape, model: small, pair, sonnet: narrow and well-specified Divide: no
Agent(subagent_type="manager", prompt="working directory: /home/you/code/_worktrees/myrepo-issue-31-csv-export; <the brief, verbatim>; prefix=feat; protected=main; max_rounds=3; never push or merge") (+7 lines)
Branch: feat/issue-31-csv-export, base 1a2b3c4, head 5d6e7f8 Commits: 5d6e7f8 feat: CSV export (#31) Tests: pytest, 118 passed; lint clean (run by me) Findings: none Rounds: 1 of 3 Unfinished: none Manual steps for caller: push, open the PR, merge
Bash(git push -u origin feat/issue-31-csv-export && gh pr create --fill) (+1 line)
https://github.com/you/myrepo/pull/44
Merged PR #44; saved the manager's report to skilleddocs/orchestrator/reports/.
Agent(subagent_type="verifier", prompt="skilleddocs/orchestrator/reports/<#31 report>; interview=park; review-done=yes") (+5 lines)
Verified by: 118 passed · CI run 9876543210 Findings: none Decided for you: none Manual steps for user: none 1. #28 Rework auth flow (unestimated, strong model: needs-design)

Prereqs

  • update-progress, consult-plan and next installed.
  • gh authenticated, plus the project scope for a kanban board.

You get back

  • Verified-by (tests + CI run id).
  • Findings fixed / issues filed.
  • Decided-for-you list.
  • Assumed open A-n list.
  • Manual steps for you.
  • Then next's output unedited.

Sample workflows

Source

Use cases & tips from the community