/review-code

Code Review Request

!{ echo "## Context" echo "" echo "Working directory: $(pwd)" echo ""

Git context with error handling

if git rev-parse --git-dir > /dev/null 2>&1; then BRANCH=$(git rev-parse --abbrev-ref HEAD 2>/dev/null || echo "unknown") echo "Branch: $BRANCH" echo ""

echo "### Modified Files"
echo '```'
git diff --name-only HEAD 2>/dev/null | head -20 || echo "No uncommitted changes"
echo '```'
echo ""

echo "### Diff Summary"
echo '```'
git diff --stat HEAD 2>/dev/null | tail -10 || echo "No diff available"
echo '```'

else echo "Note: Not a git repository" echo "" echo "### Recently Modified Files" echo '' find . -type f -name "*.java" -mmin -60 2>/dev/null | head -10 || echo "No recent files found" echo '' fi

Bead context

echo "" echo "### Active Beads" echo '' if command -v bd &> /dev/null; then bd list --status=in_progress --limit=3 2>/dev/null || echo "No in-progress beads" else echo "Beads not available" fi echo ''

}

Project Context

Gather project context using MCP tools:

• Use memory_get tool: project="{project}", title="" to list T2 memory entries
• Use scratch tool: action="list" to list T1 scratch entries

Focus Areas

$ARGUMENTS

Action

Invoke the code-review skill with the following relay. Fill in dynamic fields from the context above:

## Relay: code-review-expert

**Task**: Review the code changes for quality, security, and best practices
**Bead**: [fill from active bead above or 'none']

### Input Artifacts
- Files: [fill from modified files list above]

### Deliverable
Structured code review with severity-rated findings, grouped by category (correctness, security, maintainability, performance).

### Quality Criteria
- [ ] All changed files reviewed
- [ ] Findings categorized by severity (critical, important, suggestion)
- [ ] Actionable fix recommendations for each finding

### Focus Areas
$ARGUMENTS

For full relay structure and optional fields, see RELAY_TEMPLATE.md.