Results for “pull-request-review”

The art of reviewing code that improves both the codebase and the developer - sharing knowledge, maintaining standards, and building cultureUse when "code review, PR review, pull request, merge request, review comments, LGTM, review feedback, approve PR, request changes, review checklist, code quality, review standards, code-review, pull-request, PR, quality, standards, feedback, collaboration, mentoring" mentioned.

Monitor a pull request or review cycle until all checks pass, comments are resolved, and the PR is ready to merge.

Create, update, and comment on GitHub pull requests with a focus on material impact, safety, and human reviewability.

Guides creating small, issue-linked pull requests with conventional branch naming, commit messages, and structured descriptions, plus a review cycle.

Review code for AEM Edge Delivery Services projects, validating code quality, performance, accessibility, and adherence to EDS best practices during self-review or pull request review.

Implements a code change on a feature branch, opens a single pull request to main, and runs a code review loop before handoff.

Automates repeated rounds of Copilot code review on GitHub pull requests: triggers review, triages threads, dispatches parallel fix agents, commits, replies, and loops until convergence.

Iterate on a pull request until actionable CI checks pass and high/medium review feedback is addressed, stopping at human approval, draft, or merge gates.

Runs a multi-perspective review of a pull request, including code quality, tests, and potential silent failures, then reports findings ranked by severity.

Creates a pull request from completed phase work, generates a rich PR body from planning artifacts, optionally runs code review, and prepares for merge.

Review a pull request and POST the review to GitHub via `gh pr review`. Use when asked to review a PR, or when the github-activity poller fires a PR-opened / PR-review-requested event. Always submits after drafting — a review that stays in turn output and never reaches GitHub is a non-review.

Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.

Safely upsert, inspect, review, or explicitly merge the pull request for an issue-backed work branch

Review an exact PR head in isolation using trusted-base instructions and execution evidence

Creates a GitHub pull request with an auto-generated summary, running mandatory pre-commit and code-quality review gates, plus optional deep-review subagents, and posts findings into the PR body.

Review pull requests following Sentry engineering practices, covering security, performance, testing, and design.

Split a large pull request into multiple smaller PRs to reduce the number of required CODEOWNERS reviewer groups.

Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member.

Requesting Code Review

PR Review Skill

Creates a convention-compliant pull request from the current branch, inferring details from git history and code changes.

Use this skill for code review and PR review tasks. Covers review methodology, what to flag, what to skip, and output structure.

Produces a maintainer-grade review of a pull request or large contribution, explaining the change tutorial-style and delivering a polished HTML or Markdown report with a concrete merge recommendation.

Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

Generates a pull request title and body from local git history, writing them to a draft file for review before publishing.

Decide which pull-request review comments are actionable. Use when addressing review feedback, monitoring a PR, or filtering already-handled comments.

Guides contributors through creating pull requests that add or fix skills, with a checklist covering metadata validation, risk labeling, and security disclaimers.

Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

Review and apply GitHub Copilot suggestions on pull requests. Trigger when reviewing PRs with Copilot suggestions.

Guides writing effective pull request descriptions focused on motivation, public API changes, and user impact while avoiding implementation details.