Dispatches domain-aware code reviewers (ML/AI/embedded/frontend/backend/security) to evaluate git diffs against specs and standards after tasks, features, or before merging.
npx claudepluginhub gadaalabs/claude-code-on-steroidsThis skill uses the workspace's default tool permissions.
**TRIBUNAL** — *A tribunal is a formal body of judgment that delivers evidence-based verdicts.*
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
TRIBUNAL — A tribunal is a formal body of judgment that delivers evidence-based verdicts. When invoked: dispatches a domain-aware code reviewer (ML / AI / Embedded / Frontend / Security), evaluates the work against spec and quality standards, and returns a structured verdict before anything merges.
Dispatch superpowers:code-reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work.
Core principle: Review early, review often.
Mandatory:
Optional but valuable:
1. Get git SHAs:
BASE_SHA=$(git rev-parse HEAD~1) # or origin/main
HEAD_SHA=$(git rev-parse HEAD)
2. Identify domain(s) — this changes the review checklist:
| Domain | Add to reviewer context |
|---|---|
| ML / Data Science | DOMAIN: ml — reviewer applies ML checklist |
| AI / RAG / Agents | DOMAIN: ai — reviewer applies AI safety checklist |
| Embedded / Firmware | DOMAIN: embedded — reviewer applies real-time checklist |
| Frontend / UI | DOMAIN: frontend — reviewer applies a11y + perf checklist |
| General backend | DOMAIN: backend — reviewer applies standard checklist |
| Security-critical | DOMAIN: security — reviewer applies OWASP + threat model |
| Multi-domain | List all: DOMAIN: ml, frontend |
3. Dispatch code-reviewer subagent:
Use Task tool with superpowers:code-reviewer type, fill template at code-reviewer.md
Placeholders:
{WHAT_WAS_IMPLEMENTED} - What you just built{PLAN_OR_REQUIREMENTS} - What it should do{BASE_SHA} - Starting commit{HEAD_SHA} - Ending commit{DESCRIPTION} - Brief summary{DOMAIN} - Domain(s) from table above — required, not optional3. Act on feedback:
[Just completed Task 2: Add verification function]
You: Let me request code review before proceeding.
BASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | awk '{print $1}')
HEAD_SHA=$(git rev-parse HEAD)
[Dispatch superpowers:code-reviewer subagent]
WHAT_WAS_IMPLEMENTED: Verification and repair functions for conversation index
PLAN_OR_REQUIREMENTS: Task 2 from docs/superpowers/plans/deployment-plan.md
BASE_SHA: a7981ec
HEAD_SHA: 3df7661
DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
[Subagent returns]:
Strengths: Clean architecture, real tests
Issues:
Important: Missing progress indicators
Minor: Magic number (100) for reporting interval
Assessment: Ready to proceed
You: [Fix progress indicators]
[Continue to Task 3]
Subagent-Driven Development:
Executing Plans:
Ad-Hoc Development:
Never:
If reviewer wrong:
See template at: tribunal/code-reviewer.md