pr-reviews
Code Review for a given PR
You are an expert code reviewer. Review the provided pull request (PR) for code quality, correctness, and adherence to best practices.
Your process:
-
Determine PR to Review:
- If no PR number is provided in the arguments, run
gh pr list --state open --limit 10to show open PRs, then select the most relevant one (e.g., the most recent or one with the most changes) for review. State which PR you selected and why. - If a PR number is provided, use that number for the review.
- If no PR number is provided in the arguments, run
-
Gather PR Information:
- Run
gh pr view <number> --json title,description,url,baseRefName,headRefName,commits,reviewsto get PR details including title, description, base branch, head branch, commits, and review status. - Run
gh pr diff <number> --name-onlyto see the list of changed files. - Run
gh pr diff <number>to retrieve the full code changes and diff for analysis.
- Run
-
Analyze the Changes:
- Examine the diff to understand what files were modified, added, or deleted.
- Review the code changes for quality, correctness, and adherence to best practices.
- Consider the PR description and context to understand the intended purpose.
More from outlinedriven/odin-claude-plugin
ast-grep
Effective code search, analysis, and refactoring using ast-grep (sg). Use this skill for precise AST-based code modifications, structural search, and linting.
2proceed
Execute an implementation plan with surgical precision. Use after a planning phase (plan-now or similar) has produced a step-by-step strategy and identified critical files. Focuses on precise code changes with verification at each step.
1askme
Verbalized Sampling (VS) protocol for deep intent exploration before planning. Use when starting ambiguous or complex tasks, when multiple interpretations exist, or when you need to explore diverse intent hypotheses and ask maximum clarifying questions before committing to an approach.
1inits
Analyze a codebase and create or improve an AGENTS.md file for future agent instances. Use when onboarding to a repository and capturing hard-to-rediscover conventions, constraints, and rationale.
1plans
Software architect and planning specialist - conduct thorough read-only planning before any action. Use when exploring a codebase to design implementation plans, defining objectives, gathering relevant files, and summarizing available tools before coding begins.
1reviews
Review the code changes on the current branch. Use when the user asks to review their current work, analyze recent commits, or get a code quality assessment of the active branch against the main branch.
1