Skip to content

Command Reference

This comprehensive guide covers all reviewtask commands, their options, and usage examples.

AI Provider Transparency

All major commands now display the active AI provider and model at startup:

🤖 AI Provider: Cursor CLI (grok)

This feature ensures you always know: - Which AI tool is being used - What model is active - Whether configuration is working correctly

Core Commands

Main Command

reviewtask [PR_NUMBER]

Analyze PR reviews and generate actionable tasks.

# Analyze current branch's PR
reviewtask

# Analyze specific PR
reviewtask 123

# Clear cache and reprocess all comments
reviewtask --refresh-cache

Options: - --refresh-cache - Clear cache and reprocess all comments

What it does: - Fetches PR reviews and comments from GitHub - Processes comments using AI analysis - Generates actionable tasks with priorities - Saves results to .pr-review/PR-{number}/ - Preserves existing task statuses

Task Management

reviewtask status [PR_NUMBER] [options]

Show task status and statistics across PRs.

# Current branch status
reviewtask status

# Specific PR (v3.0.0: simplified interface)
reviewtask status 123

# All PRs
reviewtask status --all

# Brief output format
reviewtask status --short

Options: - --all, -a - Show information for all PRs - --short, -s - Brief output format

Changes in v3.0.0: - PR number is now a positional argument: status 123 instead of --pr 123 - Removed --pr, --branch, --watch flags - Simplified to only 2 flags for clarity

reviewtask show [task-id]

Show current/next task or specific task details.

# Show current/next task
reviewtask show

# Show specific task details
reviewtask show task-uuid-here

reviewtask start <task-id> (v3.0.0)

Start working on a task (sets status to "doing").

reviewtask start task-uuid-here

What it does: - Marks task as "doing" to indicate active work - More intuitive than reviewtask update <task-id> doing - Recommended for new workflows

Complete task with full automation workflow including verification, commit, thread resolution, and next task suggestion.

# Complete task with full automation
reviewtask done task-uuid-here

# Skip specific phases if needed
reviewtask done task-uuid-here --skip-verification
reviewtask done task-uuid-here --skip-commit
reviewtask done task-uuid-here --skip-resolve
reviewtask done task-uuid-here --skip-suggestion

What it does (in order): 1. Verification: Runs build/test/lint checks (if enable_verification: true) 2. Status Update: Marks task as "done" 3. Auto-commit: Creates structured commit with changes (if enable_auto_commit: true) 4. Thread Resolution: Resolves GitHub review thread (based on enable_auto_resolve mode) 5. Next Task: Shows next recommended task (if enable_next_task_suggestion: true)

Configuration:

{
  "done_workflow": {
    "enable_auto_resolve": "complete",
    "enable_verification": true,
    "enable_auto_commit": true,
    "enable_next_task_suggestion": true
  }
}

Options: - --skip-verification - Skip build/test/lint checks - --skip-commit - Don't auto-commit changes - --skip-resolve - Don't resolve review thread - --skip-suggestion - Don't show next task

Why use done instead of complete: - done provides full workflow automation - complete only handles verification + status update - done is the recommended command for most workflows

reviewtask hold <task-id> (v3.0.0)

Put a task on hold (sets status to "pending").

reviewtask hold task-uuid-here

What it does: - Marks task as "pending" to indicate it needs evaluation or is blocked - More intuitive than reviewtask update <task-id> pending - Use when you need to evaluate feedback or are blocked by dependencies

reviewtask update <task-id> <status>

Update task status (traditional interface).

reviewtask update task-uuid-here doing
reviewtask update task-uuid-here done
reviewtask update task-uuid-here pending

Valid statuses: - todo - Ready to work on - doing - Currently in progress - done - Completed - pending - Blocked or low priority

Note: This command is still supported but the new start, done, and hold commands are recommended for better clarity. Use reviewtask cancel command for canceling tasks instead of update <id> cancel.

Task Lifecycle Management

reviewtask cancel <task-id> [options]

Cancel a task with explanatory comment posted to GitHub review thread.

# Cancel a specific task with reason
reviewtask cancel task-uuid-here --reason "Already addressed in commit abc1234"

# Cancel all pending tasks with same reason
reviewtask cancel --all-pending --reason "Deferring to follow-up PR #125"

Options: - --reason <text> - Required explanation for cancellation (posted to GitHub) - --all-pending - Cancel all tasks with status "pending"

What it does: - Updates task status to "cancel" - Posts cancellation reason as comment on GitHub review thread - Notifies reviewers why feedback wasn't addressed - Returns non-zero exit code on failure (safe for CI/CD)

Error Handling: - Exit code 0: Task(s) successfully cancelled - Exit code 1: Cancellation failed (error details provided) - Wraps first error with context using Go's %w error wrapping - In batch mode, continues processing all tasks before returning error

CI/CD Usage:

# Safe error handling in scripts
if ! reviewtask cancel --all-pending --reason "Sprint ended"; then
    echo "Failed to cancel pending tasks" >&2
    exit 1
fi

reviewtask verify <task-id>

Run verification checks before task completion.

# Verify task implementation quality
reviewtask verify task-uuid-here

What it does: - Runs configured verification checks for task type - Build verification (default: go build ./...) - Test execution (default: go test ./...) - Code quality checks (default: golangci-lint run, gofmt -l .) - Custom verification commands based on task type - Records verification results in task metadata

Task Type Detection: - test-task: Tasks containing "test" or "testing" - build-task: Tasks containing "build" or "compile" - style-task: Tasks containing "lint" or "format" - bug-fix: Tasks containing "bug" or "fix" - feature-task: Tasks containing "feature" or "implement" - general-task: All other tasks

Thread Resolution

reviewtask resolve [task-id] [options]

Manually resolve GitHub review threads for completed tasks.

# Resolve thread for a specific task
reviewtask resolve task-uuid-here

# Resolve all completed tasks' threads
reviewtask resolve --all

# Force resolution even if task isn't marked as done
reviewtask resolve task-uuid-here --force

Options: - --all - Resolve threads for all tasks marked as done - --force - Resolve thread even if task status is not done

What it does: - Resolves the GitHub review thread associated with the task - Requires task to be in done status (unless --force is used) - Uses GitHub GraphQL API to mark thread as resolved - Prevents duplicate resolution attempts

Auto-resolve mode: By default, threads are automatically resolved when all tasks from a comment are completed. Use reviewtask resolve for manual control or when auto-resolve is disabled.

Statistics

reviewtask stats [PR_NUMBER] [options]

Show detailed task statistics with comment breakdown.

# Current branch statistics
reviewtask stats

# Statistics for specific PR
reviewtask stats 123
reviewtask stats --pr 123

# Statistics for all PRs
reviewtask stats --all

# Statistics for specific branch
reviewtask stats --branch feature/new-feature

Output includes: - Comment-level breakdown with task counts - Priority distribution (critical/high/medium/low) - Status distribution (todo/doing/done/pending/cancel) - Completion metrics and progress tracking - File-level summary with affected files

Setup and Configuration

Repository Setup

reviewtask init

Interactive setup wizard that initializes repository with reviewtask configuration.

reviewtask init

Features: - Interactive language selection - Automatic AI provider detection (Cursor CLI, Claude Code) - Creates minimal 2-line configuration - Sets up .pr-review/ directory structure - Adds appropriate .gitignore entries - Verifies GitHub authentication

Configuration Management

reviewtask config <command>

Manage and optimize configuration settings.

# Show current configuration
reviewtask config show

# Validate configuration and suggest improvements
reviewtask config validate

# Migrate to simplified format (46+ lines → 2-8 lines)
reviewtask config migrate

Benefits of simplified configuration: - Auto-detects project type (Go, Node.js, Rust, Python, etc.) - Applies smart defaults for build/test commands - Reduces configuration complexity by 90% - Maintains full backward compatibility

Authentication

reviewtask auth <command>

Manage GitHub authentication.

# Interactive GitHub token setup
reviewtask auth login

# Show current authentication source and user
reviewtask auth status

# Remove local authentication
reviewtask auth logout

# Comprehensive validation of token and permissions
reviewtask auth check

Authentication sources (priority order): 1. GITHUB_TOKEN environment variable 2. Local config file (.pr-review/auth.json) 3. GitHub CLI (gh auth token)

Version Management

reviewtask version [VERSION]

Show version information or switch to specific version.

# Show current version with update check
reviewtask version

# Switch to specific version
reviewtask version v1.2.3
reviewtask version latest

# Check for available updates only
reviewtask version --check

reviewtask versions

List available versions from GitHub releases.

reviewtask versions

Shows recent 5 versions with release information.

AI Provider Integration

Prompt Generation

reviewtask prompt <provider> <target>

Generate AI provider command templates.

# Generate PR review workflow template for Claude Code
reviewtask prompt claude pr-review

# Output prompts to stdout for redirection or piping
reviewtask prompt stdout pr-review
reviewtask prompt stdout pr-review > my-workflow.md
reviewtask prompt stdout pr-review | pbcopy  # macOS clipboard
reviewtask prompt stdout pr-review | xclip   # Linux clipboard

Providers: - claude - Creates optimized command templates in .claude/commands/ directory - stdout - Outputs prompts to standard output

Targets: - pr-review - PR review analysis workflow

reviewtask claude <target> (Deprecated)

Legacy command for Claude integration. Use reviewtask prompt claude <target> instead.

Debug and Development

Debug Commands

reviewtask debug fetch <phase> [PR]

Test specific phases independently for troubleshooting.

# Fetch and save PR reviews only (no task generation)
reviewtask debug fetch review 123

# Generate tasks from previously saved reviews only
reviewtask debug fetch task 123

Features: - Automatically enables verbose mode for detailed logging - Isolates specific functionality for testing - Useful for troubleshooting issues

reviewtask debug prompt <PR> [--profile <profile>]

Render the analysis prompt locally from saved reviews (no AI calls). Useful for A/B comparisons between profiles.

# Save reviews for a PR, then render the prompt
reviewtask debug fetch review 123
reviewtask debug prompt 123 --profile v2
reviewtask debug prompt 123 --profile legacy

Options: - --profile — one of: v2 (default, alias: rich), compact, minimal, legacy

Command Examples

Daily Workflow

# Morning startup
reviewtask show           # What should I work on today?
reviewtask status         # Overall progress across all PRs

# During implementation
reviewtask show <task-id> # Full context for current task
# Work on the task...
reviewtask verify <task-id>         # Verify implementation quality
reviewtask done <task-id>           # Complete with full automation

# Alternative: Cancel unnecessary tasks
reviewtask cancel <task-id> --reason "Already addressed in commit abc1234"

# When blocked
reviewtask update <task-id> pending  # Mark as blocked
reviewtask show                      # Find next task to work on

# Clean up pending tasks
reviewtask cancel --all-pending --reason "Deferring to follow-up PR"

# Manually resolve review threads
reviewtask resolve --all            # Resolve all completed tasks

# When reviews are updated
reviewtask                # Re-run to get new feedback
# Tool automatically preserves your work progress

Advanced Usage

# Force complete refresh of all data
reviewtask --refresh-cache

# Comprehensive system check
reviewtask auth check
reviewtask version --check

# Generate documentation workflows
reviewtask prompt claude pr-review
reviewtask prompt stdout pr-review > custom-workflow.md

# Detailed statistics analysis
reviewtask stats --all
reviewtask stats --branch main

Troubleshooting Commands

# Authentication debugging
reviewtask auth status
reviewtask auth check

# Version management
reviewtask versions
reviewtask version latest

# Debug specific functionality
reviewtask debug fetch review 123
reviewtask debug fetch task 123

# Performance analysis
reviewtask stats --pr 123

Global Options

Most commands support these global options:

  • --help - Show command help
  • --version - Show version information (for main command)

Command Shortcuts

The main reviewtask command without arguments analyzes the current branch's PR automatically.

reviewtask        # Auto-detects PR from current branch
reviewtask 123    # Analyzes specific PR #123

Exit Codes

reviewtask uses standard exit codes:

  • 0 - Success
  • 1 - General error (including task cancellation failures)
  • 2 - Authentication error
  • 3 - Configuration error
  • 4 - Network error

Cancel Command Exit Codes: - Returns 0 when all tasks successfully cancelled - Returns 1 when one or more cancellations fail - Wraps first error encountered for debugging - Safe for use in CI/CD pipelines and scripts

Performance Considerations

Cache Management

  • Commands automatically cache GitHub API responses
  • Use --refresh-cache when you need to bypass caching
  • Cache improves performance and reduces API rate limit usage

Large PRs

  • Tool automatically optimizes performance based on PR size
  • Comments >20KB are automatically chunked
  • Parallel processing handles multiple comments efficiently
  • Auto-resume functionality for interrupted processing

Rate Limiting

  • Authenticated requests: 5,000/hour
  • Use reviewtask auth check to monitor rate limit status
  • Tool includes automatic retry logic for rate limit handling

For more detailed information on specific commands, use the --help flag with any command.