Troubleshooting Guide¶
This comprehensive guide helps you diagnose and resolve common issues with reviewtask.
Quick Diagnosis Commands¶
Start troubleshooting with these diagnostic commands:
# Check version and system info
reviewtask version
# Verify authentication
reviewtask auth status
reviewtask auth check
# Test basic functionality
reviewtask show
reviewtask status
Authentication Issues¶
Token Validation Failed¶
Symptoms: - "Authentication failed" errors - "Invalid token" messages - 401 Unauthorized errors
Solutions:
-
Check token validity:
-
Verify token hasn't expired:
- Check GitHub Settings > Developer settings > Personal access tokens
-
Look for expiration date and token status
-
Ensure correct scopes:
- Private repos: Requires
repo
scope - Public repos: Requires
public_repo
scope -
Organization repos: Requires
read:org
scope -
Re-authenticate:
Repository Access Denied¶
Symptoms: - "Repository not found" errors - "Access denied" when fetching PR data - 403 Forbidden errors
Solutions:
-
For private repositories:
-
For organization repositories:
-
Verify repository URL:
Multiple Authentication Sources¶
Symptoms: - Confusion about which token is being used - Inconsistent authentication behavior
Diagnosis:
Priority order:
1. GITHUB_TOKEN
environment variable (highest)
2. Local config file (.pr-review/auth.json
)
3. GitHub CLI (gh auth token
) (lowest)
Solutions:
# Use specific source
export GITHUB_TOKEN="your_token" # Environment variable
# Or remove conflicting sources
reviewtask auth logout # Remove local config
unset GITHUB_TOKEN # Remove environment variable
Rate Limit Issues¶
API Rate Limiting¶
Symptoms: - "Rate limit exceeded" errors - Slow or failing API requests - 429 Too Many Requests errors
Check current status:
Rate limits: - Authenticated: 5,000 requests/hour - Unauthenticated: 60 requests/hour
Solutions: 1. Ensure authentication:
-
Use caching:
-
Wait for reset:
- Rate limits reset every hour
- Check
X-RateLimit-Reset
time in auth check output
Version and Update Issues¶
Binary Not Found¶
Symptoms: - "command not found: reviewtask" - "reviewtask: command not found"
Solutions:
-
Check installation:
-
Verify PATH:
-
Add to PATH:
-
Reinstall:
Version Issues¶
Symptoms: - Old version behavior - Missing features - Update failures
Solutions:
-
Check current version:
-
Update to latest:
-
Manual reinstall:
Task Generation Issues¶
Missing Tasks¶
Symptoms: - No tasks generated from PR reviews - Empty task lists despite review comments
Diagnosis:
# Enable verbose mode
# Edit .pr-review/config.json:
{
"ai_settings": {
"verbose_mode": true
}
}
# Test specific phases
reviewtask debug fetch review 123
reviewtask debug fetch task 123
Solutions:
-
Force refresh:
-
Check AI provider:
-
Verify PR has reviews:
Inconsistent Task Generation¶
Symptoms: - Tasks appear and disappear - Duplicate tasks - Incorrect task content
Solutions:
-
Clear cache:
-
Check comment changes:
- Tasks are cancelled when comments change significantly
-
New tasks created for new/updated comments
-
Adjust deduplication:
Task Status Issues¶
Symptoms: - Task statuses reset unexpectedly - Cannot update task status - Status changes not persisting
Solutions:
-
Check task ID:
-
Verify file permissions:
-
Manual status check:
AI Provider Integration Issues¶
Claude Code Integration¶
Symptoms: - "claude command not found" - AI analysis failures - Empty or malformed task generation
Solutions:
-
Verify installation:
-
Check PATH:
-
Install Claude Code: Follow official installation instructions
-
Test Claude integration:
JSON Recovery Issues¶
Symptoms: - "unexpected end of JSON input" errors - Truncated responses - Malformed task data
Solutions:
-
Enable recovery:
-
Reduce prompt size:
-
Check response analytics:
Cache and Performance Issues¶
Cache Problems¶
Symptoms: - Outdated task content - Missing new comments - Inconsistent behavior
Solutions:
-
Force refresh:
-
Clear cache manually:
-
Check cache permissions:
Performance Issues¶
Symptoms: - Slow processing - Timeouts - High memory usage
Solutions:
-
Check PR size:
-
Enable optimization:
- Tool automatically optimizes for large PRs
-
Uses parallel processing and chunking
-
Reduce processing load:
Configuration Issues¶
Invalid Configuration¶
Symptoms: - Tool ignores configuration changes - Default behavior instead of custom settings - JSON parsing errors
Solutions:
-
Validate JSON syntax:
-
Reset to defaults:
-
Check file permissions:
Priority Assignment Issues¶
Symptoms: - All tasks get same priority - Priority rules not working - Unexpected priority assignments
Solutions:
-
Enable verbose mode:
-
Review priority rules:
-
Test with simple rules:
- Start with clear, distinct priority descriptions
- Add complexity gradually
Network and Connectivity Issues¶
GitHub API Issues¶
Symptoms: - Connection timeouts - Intermittent failures - "Network unreachable" errors
Solutions:
- Check GitHub status:
- Visit GitHub Status
-
Verify GitHub API is operational
-
Test connectivity:
-
Use retry logic:
- Tool includes automatic retry for transient failures
- Enable verbose mode to see retry attempts
Proxy and Firewall Issues¶
Symptoms: - Connection failures in corporate environments - SSL certificate errors - Blocked requests
Solutions:
-
Configure proxy:
-
Check firewall rules:
- Ensure access to api.github.com
- Verify HTTPS (443) is allowed
Debug Mode and Logging¶
Enable Verbose Output¶
For detailed troubleshooting, enable verbose mode:
Debug Commands¶
Test specific functionality:
# Test review fetching only
reviewtask debug fetch review 123
# Test task generation only
reviewtask debug fetch task 123
# Both commands enable verbose mode automatically
Log Analysis¶
Check log output for: - API request/response details - Task generation process - Error messages and stack traces - Performance metrics
Getting Additional Help¶
Self-Diagnosis Checklist¶
- ✅ Authentication working?
reviewtask auth check
- ✅ Latest version?
reviewtask version
- ✅ Valid configuration?
cat .pr-review/config.json | jq .
- ✅ AI provider available?
claude --version
- ✅ Repository access? Can you see PR on GitHub?
- ✅ Cache cleared? Try
reviewtask --refresh-cache
When to Seek Help¶
Open a GitHub issue if: - Self-diagnosis doesn't resolve the issue - You encounter unexpected behavior - You have feature requests or suggestions - Documentation is unclear or incomplete
Issue Report Template¶
When reporting issues, include:
**Environment:**
- reviewtask version: `reviewtask version`
- Operating system:
- AI provider: Claude Code version X.X.X
**Problem:**
- Clear description of the issue
- Steps to reproduce
- Expected vs actual behavior
**Logs:**
- Enable verbose mode and include relevant log output
- Sanitize any sensitive information (tokens, private repo names)
**Configuration:**
- Include .pr-review/config.json (sanitized)
- Mention any custom settings
For more help: - GitHub Issues - Command Reference - Configuration Guide