Files
rook/.claude/commands/conductor-verify.md
Ed_ f15d1bc866 chore(setup): initialize project with CLAUDE.md, MCP config, and conductor commands
- CLAUDE.md: full project guidance (architecture, MMA workflow, beads task lifecycle,
  code conventions, policy rules, commit guidelines)
- .mcp.json: manual-slop-tools MCP server registration (26+ dev tools)
- .claude/settings.json: Claude Code project settings
- .claude/settings.local.json: MCP server permissions
- .claude/commands/: 9 conductor slash commands (conductor-setup, conductor-status,
  conductor-implement, conductor-new-track, conductor-verify, mma-tier1 through tier4)
2026-03-01 21:30:22 -05:00

2.1 KiB

description
description
Phase completion verification — tests, coverage, checkpoint commit

/conductor-verify

Execute phase completion verification and checkpointing. Run when a logical group of related tasks are all done.

Protocol

1. Announce

Tell the user: "Phase complete. Running verification and checkpointing protocol."

2. Identify Phase Scope

cd C:\projects\rook
git log --oneline -20   # find the previous checkpoint commit
git diff --name-only {previous_checkpoint_sha} HEAD

For each changed code file (exclude .json, .md, .toml, .ini):

  • Verify a corresponding test file exists in tests/
  • If missing: create one (analyze existing test style first via py_get_code_outline on existing tests)

3. Run Automated Tests

Announce the exact command before running:

"Running test suite. Command: uv run pytest --cov=src/rook --cov-report=term-missing -x"

cd C:\projects\rook
uv run pytest --cov=src/rook --cov-report=term-missing -x 2>&1 | Tee-Object logs/phase_verify.log

If tests fail with large output — delegate to Tier 4 QA:

cd C:\projects\manual_slop
uv run python scripts\claude_mma_exec.py --role tier4-qa "Analyze test failures. @C:\projects\rook\logs\phase_verify.log"

Maximum 2 fix attempts. If still failing: STOP, report to user, await guidance.

4. Present Results and WAIT

Display test results, coverage, any failures.

PAUSE HERE. Do NOT proceed without explicit user confirmation.

5. Create Checkpoint Commit

After user confirms:

cd C:\projects\rook
git add -A
git commit -m "conductor(checkpoint): end of phase {name}"
$sha = git log -1 --format="%H"
git notes add -m "Phase Verification`nTests: {pass/fail count}`nCoverage: {pct}%`nConfirmed by: user" $sha

6. Announce Completion

Tell the user the phase is complete with a summary.

Context Reset

After checkpointing, treat the checkpoint commit as ground truth. Prior conversational context about implementation details can be dropped. The checkpoint commit and git notes preserve the full audit trail.