--- description: "Comprehensive PR review using specialized agents"…
Community ralph loop for testing, sourced from github. Verified exit condition, evaluator-gated.
--- description: "Comprehensive PR review using specialized agents" argument-hint: "[review-aspects]" allowed-tools: ["Bash", "Glob", "Grep", "Read", "Task"] --- # Comprehensive PR Review Run a comprehensive pull request review using multiple specialized agents, each focusing on a different aspect of code quality. Review Aspects (optional): "$ARGUMENTS" ## Review Workflow: 1. Determine Review Scope - Check git status to identify changed files - Parse arguments to see if user requested specific review aspects - Default: Run all applicable reviews 2. Available Review Aspects: - comments - Analyze code comment accuracy and maintainability - tests - Review test coverage quality and completeness - errors - Check error handling for silent failures - types - Analyze type design and invariants (if new types added) - code - General code review for project guidelines - simplify - Simplify code for clarity and maintainability - all - Run all applicable reviews (default) 3. Identify Changed Files - Run git diff --name-only to see modified files - Check if PR already exists: gh pr view - Identify file
claude-code
More testing loops
Ship the release
Run tests and update changelog until both pass without altering the public API.
/goal ship the release --success "tests pass and changelog updated" --constraints "do not touch the public API" --mode ordered
testingmedium risk
/ralph-loop "fix all tests" --max-iterations 5 (iterates until…
Community ralph loop for testing, sourced from github. Verified exit condition, evaluator-gated.
/ralph-loop "fix all tests" --max-iterations 5 (iterates until passing
testingmedium risk
Trim what loads before first paint
Reduce the data downloaded before the first screen appears, with tests and screenshots guarding behavior and appearance.
Reduce the data [web app] downloads before its first screen appears. First record passing tests, mobile and desktop screenshots, and compressed transferred bytes—the data actually downloaded. Use the build report only to suggest candidates. Defer, compress, or remove one item, then rebuild and rerun every check. Keep it only if tests pass, screenshots are pixel-identical, and bytes decrease; otherwise revert. Stop when no safe candidate remains, progress stalls, or approval is needed. Return measurements, changes, and untested states.
testingmedium risk