clawrium: Skill for Claude Code

PR Review

Request a code review for a pull request.

Instructions

1. Identify PR:

   • If PR number provided, use it
   • If not, find PR for current branch:

     gh pr view --json number,title,url
     

2. Get PR Details:

   gh pr view <number> --json number,title,body,files,additions,deletions
   gh pr diff <number>
   

3. Check Review Configuration:

   ITX_CONFIG="$(git rev-parse --show-toplevel)/.claude/itx-config.json"
   if [ -f "$ITX_CONFIG" ]; then
     REVIEW_ENABLED=$(jq -r '.mcp.review_enabled // false' "$ITX_CONFIG")
   else
     REVIEW_ENABLED="false"
   fi
   

4. Execute Review:

If Automated Review Enabled

Attempt each transport in order. Tool identifiers differ by harness, so do not invoke a configured or example name unless it is available in the current harness. An unavailable, failed, or timed-out attempt falls through to the next step.

1. ATX via MCP: Inspect the current tool list for an ATX request-review tool. If one is available, invoke it with Review PR #<number>. If MCP is unavailable, fails, or times out, continue to the CLI step.
2. ATX via CLI: Check command -v atx and require atx server status to report Running: true. If both checks pass, run the stateless review command so the result does not depend on harness-specific hooks:

   atx review request \
     --prompt "Review PR #<number>, including its full diff and tests." \
     --format json --timeout 15m
   

   If the CLI is unavailable, stopped, fails, or times out, continue to manual review.
3. Manual review: After both automated transports are exhausted, use the manual checklist below and state clearly which attempts were unavailable or failed.

Process Automated Review Results:

• If rating <= 3/5 or blocking issues exist:
  • List issues to fix
  • Recommend specific changes
• If rating > 3/5 and no blockers:
  • PR is ready for merge

Report:

## Automated Review Summary

**PR**: #<number> - <title>
**Rating**: <X>/5

### Blocking Issues
<table or "None">

### Warnings
<list or "None">

### Suggestions
<list or "None">

### Verdict
<READY FOR MERGE / NEEDS CHANGES>