code-review-request

MacroMan5's avatarfrom MacroMan5

Request and process code review efficiently with a simple rubric and patch plan

⭐1stars🔀0forks📁View on GitHub🕐Updated Nov 10, 2025
[Code Review]

When & Why to Use This Skill

The code-review-request skill streamlines the software development lifecycle by automating the generation of structured, actionable code review requests. It provides a comprehensive summary of changes, assesses potential risks, and organizes findings into a clear rubric with severity levels and a concrete patch plan, ensuring high code quality and efficient team collaboration.

Use Cases

  • Pre-commit Self-Review: Generate a structured summary and fix plan to identify and resolve critical issues before officially submitting code for peer review.
  • Pull Request Documentation: Create detailed, table-based findings and risk assessments to populate PR descriptions, helping reviewers understand the context and impact quickly.
  • Post-Task Validation: Use the skill after completing a coding task to ensure all changes align with the intended purpose and that no high-severity regressions were introduced.
  • Refactoring Assessment: Evaluate complex code changes by categorizing suggestions versus critical fixes, allowing teams to prioritize technical debt reduction effectively.
namecode-review-request
descriptionRequest and process code review efficiently with a simple rubric and patch plan
version0.1.0
tags[review, quality]

Code Review Request

Purpose

Summarize changes and request focused review with clear findings and an actionable fix plan.

When to Use

  • After quality pipeline passes in /lazy task-exec
  • Before commit or before /lazy story-review

Behavior

  1. Summarize: files changed, purpose, risks (≤5 bullets).
  2. Table rubric: Issue | Severity (Critical/Warning/Suggestion) | File:Line | Fix Plan.
  3. Patch plan: 3–6 concrete steps grouped by severity.
  4. Optional: produce a PR-ready comment block.

Output Style

  • table-based for findings; short bullets for summary and steps.

Guardrails

  • No auto-commits; propose diffs only.
  • Separate criticals from suggestions.

Integration

  • Coder/Reviewer agents; /lazy task-exec before commit; /lazy story-review pre-PR.

Example Prompt

Request review for changes in src/payments/processor.py and tests.