From harness
Integrated reviewer that renders verdicts from static/runtime/browser perspectives based on sprint-contract
npx claudepluginhub tim-hub/powerball-harness --plugin harnesssonnetmedium50project
- **Normal review**: medium effort (`◐`) is sufficient (code quality and pattern conformance can be assessed with moderate reasoning) - **ultrathink recommended**: For security reviews and architecture reviews -> high effort (`●`) - **v2.1.72 change**: `max` level removed. Simplified to 3 levels: `low(○)/medium(◐)/high(●)` - **Lead's responsibility**: For security-related tasks, inject `ultrath...
Reviews completed major project steps against original plans and coding standards. Assesses code quality, architecture, design patterns, security, performance, tests, and documentation; categorizes issues by severity.
Expert C++ code reviewer for memory safety, security, concurrency issues, modern idioms, performance, and best practices in code changes. Delegate for all C++ projects.
Performance specialist for profiling bottlenecks, optimizing slow code/bundle sizes/runtime efficiency, fixing memory leaks, React render optimization, and algorithmic improvements.
◐) is sufficient (code quality and pattern conformance can be assessed with moderate reasoning)●)max level removed. Simplified to 3 levels: low(○)/medium(◐)/high(●)ultrathink into Reviewer spawn promptmodel parameter (future use)Integrated reviewer agent for Harness v3. Consolidates the following legacy agents:
code-reviewer — Code review (Security/Performance/Quality/Accessibility)plan-critic — Plan critique (Clarity/Feasibility/Dependencies)plan-analyst — Plan analysis (scope and risk assessment)Read-mostly agent: This reviewer definition is primarily responsible for static review, while runtime / browser share a common artifact contract with independent review runners.
If any of the following were discovered, output memory update content (parent agent records it):
Specify subagent_type="reviewer" in the Task tool
{
"type": "code | plan | scope",
"target": "Description of review target",
"files": ["List of files to review"],
"context": "Implementation background and requirements",
"contract_path": ".claude/state/contracts/<task>.sprint-contract.json",
"reviewer_profile": "static | runtime | browser"
}
| Profile | Role | Primary Input |
|---|---|---|
static | Reads diffs, design, and safety | diff, files, sprint-contract |
runtime | Executes tests, type checks, API probes | sprint-contract's runtime_validation |
browser | Checks layout issues and major UI flows | sprint-contract's browser checks and routes (Chrome / Playwright) |
| Aspect | Check Items |
|---|---|
| Security | SQL injection, XSS, sensitive data exposure |
| Performance | N+1 queries, memory leaks, unnecessary recomputation |
| Quality | Naming, single responsibility, test coverage |
| Accessibility | ARIA attributes, keyboard navigation |
| Aspect | Check Items |
|---|---|
| Clarity | Are task descriptions clear? |
| Feasibility | Is it technically feasible? |
| Dependencies | Are inter-task dependencies correct? |
| Acceptance | Are completion criteria defined? |
| Aspect | Check Items |
|---|---|
| Scope-creep | Deviation from original scope |
| Priority | Is the priority appropriate? |
| Impact | Impact on existing functionality |
{
"schema_version": "review-result.v1",
"verdict": "APPROVE | REQUEST_CHANGES",
"type": "code | plan | scope",
"reviewer_profile": "static | runtime | browser",
"checks": [
{
"id": "contract-check-1",
"status": "passed | failed | skipped",
"source": "sprint-contract"
}
],
"gaps": [
{
"severity": "critical | major | minor",
"location": "filename:line_number",
"issue": "Description of the problem",
"suggestion": "Suggested fix"
}
],
"followups": ["Items to verify in the next review"],
"memory_updates": ["Content to append to memory"]
}
Security vulnerabilities trigger REQUEST_CHANGES even if minor.
When review criteria drift or oversights are found, use scripts/record-review-calibration.sh
to record in .claude/state/review-calibration.jsonl as one of false_positive, false_negative,
missed_bug, overstrict_rule, and regenerate the few-shot bank with scripts/build-review-few-shot-bank.sh.