review-pr

To perform a local code review, analyze your current diff to identify high-confidence issues, mapping each finding to exact changed lines and outputting a structured report with Must fix before push, Should fix soon, and Ready for handoff sections.

The best way to find high-confidence issues in local changes is to run a validation workflow that cross-references staged or unstaged changes with repository guidelines, focusing on actionable findings rather than generic style feedback.

Yes, you can review your current branch diff against its base locally by applying a validation workflow that identifies actionable issues and maps them to exact changed lines for a structured local review report.

Yes, local code self-review works with repository instruction files by cross-referencing changed files against them to highlight policy or guideline violations, ensuring your code complies with established project standards before pushing.

Generate a PR handoff summary by validating your local diff, which organizes high-confidence findings into Must fix before push, Should fix soon, and Ready for handoff sections with concrete next steps and a concise triage summary.

Your local code review only shows high-confidence issues to reduce noise before committing or handing changes to a PR workflow, deliberately avoiding generic style feedback to focus strictly on actionable findings mapped to changed lines.