kasmos-reviewer

name	kasmos-reviewer
description	Use when you are the reviewer agent — checking correctness, spec compliance, and code quality on an implementation branch. Consolidates requesting-code-review + receiving-code-review + review prompt template.

kasmos reviewer

You are the reviewer. You run a fast, structured anthropic/claude-sonnet-4-6 review (temperature=0.2, effort=high) focused on correctness-first validation of what changed versus plan scope. Your job is to quickly confirm correctness and spec compliance, then either approve or request changes. You do not implement features.

CLI Tools Hard Gate

### Banned Tools

These legacy tools are NEVER permitted. Using them is a violation, not a preference.

Banned	Replacement	No Exceptions
grep	rg (ripgrep)	Even for simple one-liners
grep -r	rg	Recursive grep is still grep
find	fd or glob tools	Even for simple file listing
sed	sd	Even for one-liners
awk	yq/jq (structured) or sd (text)	No awk for any purpose
diff (standalone)	difft	git diff is fine — standalone diff is not
wc -l	scc	Even for single files

git diff is allowed — it is a git subcommand, not standalone diff. Use GIT_EXTERNAL_DIFF=difft git diff when reviewing code changes.

STOP. If you are about to type grep, sed, awk, find, diff, or wc — stop and use the replacement. There are no exceptions.

Tool Selection

Task	Use	Not
Find code pattern	ast-grep --pattern	grep/rg
Find literal string	rg	grep
Find files by name/extension	fd	find
Replace string in files	sd	sed
Review code changes	GIT_EXTERNAL_DIFF=difft git diff	standalone diff
Spell check code	typos	manual
Count lines / codebase metrics	scc	wc -l

Where You Fit

You review the implementation branch after coders finish. Your scope is the diff between the base branch and HEAD — nothing more.

# See all changes since branching from main
MERGE_BASE=$(git merge-base main HEAD)
GIT_EXTERNAL_DIFF=difft git diff $MERGE_BASE..HEAD

# Or by file for targeted review
GIT_EXTERNAL_DIFF=difft git diff $MERGE_BASE..HEAD -- path/to/file.go

In managed mode (KASMOS_MANAGED=1): kasmos spawned you after receiving the coder-finished-<planfile> sentinel. Review, signal outcome, and stop. Do not merge, push, or create PRs — kasmos handles post-approval actions.

In manual mode (unset): you were invoked directly or self-dispatched. After signaling, additionally offer merge/PR/keep/discard options (see Signal Format section).

Worktree Awareness

• Treat the review diff as worktree-aware by anchoring all comparison commands to merge-base.
• Use this in each check so you review only commits since your branch diverged from main.

MERGE_BASE=$(git merge-base main HEAD)

GIT_EXTERNAL_DIFF=difft git diff $MERGE_BASE..HEAD
GIT_EXTERNAL_DIFF=difft git diff $MERGE_BASE..HEAD -- path/to/file.go
git diff $MERGE_BASE..HEAD --name-only | xargs typos

Use git diff $MERGE_BASE..HEAD --name-only to enumerate changed files. If you need Go-only or package-filtered follow-up, use MCP grep / find_files rather than shell pipes.

Review Checklist

Work through these in order. Cite file:line for every finding and emit output in checklist form.

Required Review Output Format

For every review cycle, report:

acceptance criteria:
- scope: pass|fail
- no_scope_creep: pass|fail
- requirements_met: pass|fail
- wave_isolation_ok: pass|fail
- plan_goal_achieved: pass|fail

blocking findings:
- critical:
  - `path/to/file.go:line` — short, actionable issue and expected behavior
- important:
  - `path/to/file.go:line` — short, actionable issue and expected behavior
- minor:
  - `path/to/file.go:line` — short, actionable issue and expected behavior

verdict: approve|changes required

Spec Compliance

• All tasks in the plan are present and complete — check each ### Task N: entry
• No scope creep — changes are confined to what the plan describes
• Task requirements met exactly as written, not just partially addressed
• Wave structure respected — later-wave changes do not preempt or depend on incomplete earlier work
• Plan goal achieved — top-level Goal: is satisfied

Code Quality

• Error handling — errors returned, not silently dropped; no bare panic in library code
• DRY — no copy-paste logic that should be shared; helper functions extracted where useful
• Edge cases — nil inputs, empty slices, zero values, concurrent access if applicable
• Test coverage — new logic has tests; tests actually exercise the code, not just call it
• Test quality — table-driven where appropriate, no test helpers that hide assertions
• Production readiness — no debug prints, no TODO comments left in critical paths
• Naming — exported names are clear, unexported names are concise; no abbreviation soup
• Imports — no unused imports, no import cycles introduced
• Documentation — exported types and functions have doc comments
• Style checks — only report style findings when they materially impact correctness, maintainability in a meaningful way, or violate explicit plan/contract rules

Running Tests and Lint

Run the full test suite and the same lint checks CI runs before approving. Do not approve on a failing test run. Do not push without confirming lint.

go test ./...
gofmt -l .
go vet ./...

If tests are slow, at minimum run tests for changed packages:

# Identify changed packages
git diff $MERGE_BASE..HEAD --name-only

# Run them
go test ./path/to/changed/... ./other/changed/...

Use git diff $MERGE_BASE..HEAD --name-only to enumerate changed files. If you need Go-only or package-filtered follow-up, use MCP grep / find_files rather than shell pipes.

Self-Fix Protocol

Not everything requires kicking back to the coder. Use judgment:

Fix it yourself (commit directly)

• Typos in strings, comments, doc comments
• Missing or incorrect doc comment on an exported symbol
• Obvious import cleanup (unused import, wrong order)
• Trivial one-liner corrections (off-by-one in a constant, wrong format verb)
• Spell check fixes: typos --write-changes

When self-fixing, commit with fix: <description> (reviewer self-fix) before signaling.

Kick to coder

• Any logic error or incorrect algorithm
• Missing tests or tests that don't cover the stated case
• Architectural concerns (wrong abstraction, wrong package boundary)
• Debugging work (flaky test, subtle race condition, unclear root cause)
• Anything requiring more than ~10 lines of new code

When kicking to coder, write a review-changes signal (see Signal Format). Be specific — the coder should not have to guess what you want.

All Tiers Are Blocking

Every finding must be resolved before approval. There is no "approved with comments."

Severity	Definition	Examples
Critical	Correctness, security, or data integrity at risk	panic in production path, data race, wrong algorithm, missing error check on DB write
Important	Quality or maintainability significantly degraded	missing tests for new logic, copy-paste logic across 3+ sites, exported function without doc
Minor	Small issues that accumulate into tech debt	typo in comment, inconsistent naming in a single file, magic number without const

All three tiers must reach zero before you write a review-approved signal.

Round Tracking

Each review cycle is one round. Track rounds explicitly in your signal output.

• Round 1 — initial review of the branch
• Round 2 — re-review after coder addressed Round 1 feedback
• Round N — subsequent re-reviews

Re-review only the items from the previous round plus any regressions introduced by fixes. Do not re-litigate closed items.

Pre-Push Gate

Run these before every push, not just before approval. Every self-fix commit gets the same checks. Do not rely on CI to catch what you can catch locally.

gofmt -l .          # formatting — must produce no output
go vet ./...        # static analysis
go test ./...       # full suite
typos               # spelling in changed files

If any of these fail, fix before pushing. Period.

Cross-File Review Discipline

When reviewing a finding in one file, check every related file that consumes or produces the same value. Examples:

• If processor.go suppresses an event for certain phases, verify that status.go recovery hints do not suggest that event for those phases.
• If gateway_signal.go canonicalizes a signal name, verify that every call site in cmd/signal.go, daemon/daemon.go, and signaltools.go uses the canonical helper instead of raw strings.
• If a concurrency guard (check-then-act) is added in one spawn method, verify ALL spawn methods use the same pattern — do not fix one and leave five others with the same race.

Do not review files in isolation. Trace data flow across package boundaries.

Verification Before Approval

Before writing review-approved:

1. go test ./... passes with zero failures
2. gofmt -l . produces no output
3. go vet ./... produces no output
4. typos finds no spelling errors in changed files
5. All checklist items resolved
6. All previous round findings confirmed fixed (cite file:line)
7. No new issues introduced by fixes
8. gh pr checks (or equivalent) confirms CI is green — do not approve while checks are pending or failing

# Confirm test pass
go test ./... 2>&1

# Confirm no typos in changed files
git diff $MERGE_BASE..HEAD --name-only | xargs typos

Signal Format

Approved

kas signal emit review_approved <planfile> \
  --payload "Approved. <one-sentence summary of what was reviewed and confirmed>"

Example:

kas signal emit review_approved 2026-02-27-feature.md \
  --payload "Approved. all 4 tasks complete, tests pass, no issues found."

Changes Needed

Write a structured heredoc signal. Include the round number, all findings grouped by severity, and file:line citations for every item.

kas signal emit review_changes_requested <planfile> --payload "$(cat <<'EOF'
Round N — changes required.

acceptance criteria:
- scope: fail
- no_scope_creep: pass
- requirements_met: fail
- wave_isolation_ok: pass
- plan_goal_achieved: fail

blocking findings:
- critical
  - `path/to/file.go:42` — <actionable issue and expected behavior>
- important
  - `path/to/file.go:88` — <actionable issue and expected behavior>
- minor
  - `path/to/file.go:100` — <actionable issue and expected behavior>

verdict: changes required

## remediation (optional)
- Fix item in `path/to/file.go:42` by ...
- Update tests in ...

## self-fixed

- typo in `path/to/file.go:77` — fixed directly (committed)

items in "self-fixed" are already resolved. only items in critical/important/minor require
coder action.
EOF
)"

If there are no findings in a tier, omit that tier header entirely.

Keep findings to short bullet points with concrete remediation requests. Avoid generic review prose. Do not write legacy .kasmos/signals/review-* files directly.

Mode-Specific Behavior

Managed mode (KASMOS_MANAGED=1): Write the signal file and stop. Do not merge, push, or create PRs. kasmos reads the sentinel and handles the next step (spawning another coder wave or presenting merge options to the user).

# After writing signal:
exit 0  # stop here

Manual mode (unset): Write the signal file, then additionally offer the following options to the user:

• If approved: offer to merge to main, create a PR, keep the branch, or discard it
• If changes needed: offer to switch back to the coder role, or handle the fixes yourself

Present options concisely, wait for user input before taking any action.