review-pr
Review PR
Overview
Perform a read-only review and produce both human and machine-readable outputs.
Inputs
- Ask for PR number or URL.
- If missing, always ask.
Safety
- Never push, merge, or modify code intended to keep.
- Work only in
.worktrees/pr-<PR>. - Wrapper commands are cwd-agnostic; you can run them from repo root or inside the PR worktree.
Execution Contract
- Run wrapper setup:
scripts/pr-review <PR>
- Use explicit branch mode switches:
- Main baseline mode:
scripts/pr review-checkout-main <PR> - PR-head mode:
scripts/pr review-checkout-pr <PR>
- Before writing review outputs, run branch guard:
scripts/pr review-guard <PR>
- Write both outputs:
.local/review.mdwith sections A through J..local/review.jsonwith structured findings.
- Validate artifacts semantically:
scripts/pr review-validate-artifacts <PR>
Steps
- Setup and metadata
scripts/pr-review <PR>
ls -la .local/pr-meta.json .local/pr-meta.env .local/review-context.env .local/review-mode.env
- Existing implementation check on main
scripts/pr review-checkout-main <PR>
rg -n "<keyword>" -S src extensions apps || true
git log --oneline --all --grep "<keyword>" | head -20
- Claim PR
gh_user=$(gh api user --jq .login)
gh pr edit <PR> --add-assignee "$gh_user" || echo "Could not assign reviewer, continuing"
- Read PR description and diff
scripts/pr review-checkout-pr <PR>
gh pr diff <PR>
source .local/review-context.env
git diff --stat "$MERGE_BASE"..pr-<PR>
git diff "$MERGE_BASE"..pr-<PR>
- Optional local tests
Use the wrapper for target validation and executed-test verification:
scripts/pr review-tests <PR> <test-file> [<test-file> ...]
- Initialize review artifact templates
scripts/pr review-artifacts-init <PR>
- Produce review outputs
- Fill
.local/review.mdsections A through J. - Fill
.local/review.json.
Minimum JSON shape:
{
"recommendation": "READY FOR /prepare-pr",
"findings": [
{
"id": "F1",
"severity": "IMPORTANT",
"title": "...",
"area": "path/or/component",
"fix": "Actionable fix"
}
],
"tests": {
"ran": [],
"gaps": [],
"result": "pass"
},
"docs": "up_to_date|missing|not_applicable",
"changelog": "required"
}
- Guard + validate before final output
scripts/pr review-guard <PR>
scripts/pr review-validate-artifacts <PR>
Guardrails
- Keep review read-only.
- Do not delete worktree.
- Use merge-base scoped diff for local context to avoid stale branch drift.
More from linuxhsj/openclaw-zero-token
imsg
iMessage/SMS CLI for listing chats, history, and sending messages via Messages.app.
23obsidian
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
23coding-agent
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.
22sherpa-onnx-tts
Local text-to-speech via sherpa-onnx (offline, no cloud)
22sonoscli
Control Sonos speakers (discover/status/play/volume/group).
20skill-creator
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".
20