| name | claude-local-ultrareview |
| description | Run a local Claude Code PR ultrareview using the repository prompt and Claude CLI, then triage the returned findings and fix valid issues. Use when the user asks for a Claude ultrareview, local ultrareview, unpaid ultrareview-style review, Claude CLI review of a PR, or asks to replace paid/cloud ultrareview with a local workflow. |
Claude Local Ultrareview
Run the repo-local ultrareview prompt through the native claude CLI, wait for stdout, then treat the returned issues as review hypotheses to validate and fix.
Runner
Use:
.agents/skills/claude-local-ultrareview/scripts/run-local-ultrareview.zsh <PR_NUMBER>
If the PR number is omitted, the script attempts gh pr view for the current branch. The prompt source is .claude/prompts/local-ultrareview.md.
The runner defaults the orchestrating Claude session to claude-opus-4-7; override it only when needed with CLAUDE_LOCAL_ULTRAREVIEW_MODEL.
Useful options:
.agents/skills/claude-local-ultrareview/scripts/run-local-ultrareview.zsh --print-prompt <PR_NUMBER>
Use --print-prompt only for debugging prompt substitution. When both <PR_NUMBER> and OWNER/REPO are supplied, prompt rendering does not require gh or claude to be installed. Do not run the official claude ultrareview command for this workflow unless the user explicitly asks for the paid/cloud feature.
Workflow
- Check branch and worktree state with
git branch --show-current and git status --short.
- Run the local ultrareview script and wait for it to finish.
- Read the stdout review result carefully. Do not assume every finding is valid.
- For every reported issue, inspect the referenced code, the PR diff, relevant specs, and relevant
CLAUDE.md or AGENTS.md instructions before editing.
- Classify each finding as valid, partially valid, invalid, duplicate, already addressed, or product-decision needed.
- Fix valid and partially valid issues when they are in scope for the current PR.
- Prefer eliminating tech debt now when the fix is reasonably scoped and belongs to the PR.
- If a necessary refactor or clean-up is too large or outside the current PR, add a concise entry to
docs/master-future-considerations.md with enough context to recover the decision later.
- Run targeted verification for the files changed. Follow repository test and build policy before pushing updates to the PR.
GitHub Safety
- Do not post review comments, submit GitHub reviews, resolve threads, or mutate GitHub state as part of this skill.
- Use
gh only for read-only PR inspection unless the user separately asks for GitHub writes.
Triage Standard
Reject false positives, pre-existing issues, lint-only issues, broad style advice, and bugs on lines untouched by the PR unless the current change makes the issue meaningfully worse.
Fix P0/P1-equivalent correctness, security, data-integrity, permission, RLS, migration, and contract issues before considering the review complete. Fix P2 issues when they are real and small enough to handle without distorting the PR.
Final Response
Report:
- the PR reviewed;
- valid issues fixed;
- invalid findings rejected, with brief reasons for any serious-looking rejection;
- verification run;
- any entries added to
docs/master-future-considerations.md.
