/SKILL.md
Start a code discussion with Claude as a peer reviewer via the CLI. Intended to be called by other AI agents (Codex, Cursor, etc.) after completing their work.
npx skillsauth add timolins/claude-review claude-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
After completing your work, start a code discussion with Claude as a peer. Claude will raise questions and suggestions about your changes. You can push back, disagree, or explain your reasoning — the goal is to reach consensus on the best approach together.
~/.agents/skills/claude-review/scripts/review.sh "description of what the changes should accomplish"
Or without a goal (Claude infers from commits):
~/.agents/skills/claude-review/scripts/review.sh
Push back, explain your reasoning, or ask Claude to look at updates:
~/.agents/skills/claude-review/scripts/review.sh -c "I did it this way because X, what do you think?"
~/.agents/skills/claude-review/scripts/review.sh -c "I disagree — extracting that would add complexity for no real gain"
~/.agents/skills/claude-review/scripts/review.sh -c "Good point, I've refactored it. How does this look now?"
~/.agents/skills/claude-review/scripts/review.sh -c "I see your concern but this is intentional because of Y"
The -c flag resumes the same session so Claude has full context of the discussion.
You can tune prompt/diff truncation via env vars:
REVIEW_MAX_PROMPT_CHARS=180000 REVIEW_MAX_DIFF_CHARS=120000 REVIEW_MAX_WORKTREE_CHARS=40000 ~/.agents/skills/claude-review/scripts/review.sh
This keeps the review responsive on large branches while still giving Claude enough context.
You can also tune live preview verbosity (stream mode):
REVIEW_LIVE_PREVIEW_MIN_CHARS=160 REVIEW_LIVE_PREVIEW_MIN_EMIT_CHARS=60 REVIEW_LIVE_PREVIEW_INTERVAL_SEC=0 ~/.agents/skills/claude-review/scripts/review.sh
REVIEW_LIVE_PREVIEW_INTERVAL_SEC=0 keeps previews event-driven (newlines/message end).
Set it to >0 only if you want periodic timer-based previews for very long single-line outputs.
Live progress is enabled by default (Claude stream JSON is parsed and shown as it runs).
Set REVIEW_STREAM_JSON=0 to fall back to plain claude --print output:
REVIEW_STREAM_JSON=0 ~/.agents/skills/claude-review/scripts/review.sh
Stream rendering is handled by scripts/render-stream.mjs (Bun first, Node fallback).
If stream parsing fails at runtime, the script auto-retries once in plain output mode so reviews still complete.
The review instruction prompt is stored in scripts/review-prompt.md and loaded by scripts/review.sh, so you can tweak review behavior without editing bash logic.
--print --output-format=stream-json mode (when available), surfaces live progress/tool activity, and saves the session ID to .review-session.-c: resumes that session via claude -r <session-id>, includes fresh diff if there are new changes, and continues the discussion.Claude is set up as a peer, not an authority. It will:
The goal is consensus on what's best — not blind compliance with every suggestion.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.