Review and PR

Analyze the current branch with linting, type checks, and tests to create a PR or task list.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/zmchenry/dotfiles --skill review-and-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Review and PR
Source: https://github.com/zmchenry/dotfiles/tree/main/.claude/skills/review-and-pr
Command: npx skills add https://github.com/zmchenry/dotfiles --skill review-and-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines code reviews by analyzing the current branch and determining whether a PR should be created or if actionable tasks are needed.

Core Features & Use Cases

  • Automated branch analysis: Compare changes against the base branch and summarize diffs and potential issues.
  • Automated checks orchestration: Run linting, type checks, and tests to evaluate code quality.
  • PR decision and guidance: Either open a PR for approved changes or provide a prioritized task list for improvements.

Quick Start

When you want a review and PR, invoke this skill to assess the current branch and either create a PR or return a task list for improvements. The steps include gathering branch information, executing automated checks, and providing a structured recommendation or PR.

Frequently Asked Questions about Review and PR

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review and create a pull request from my current branch?

To automate code review and create a pull request, this skill analyzes your current branch against the base branch by running linting, type checks, and tests, then either opens a PR or returns a prioritized task list for improvements.

What is the process for checking branch readiness before opening a pull request?

Checking branch readiness involves comparing branch changes against the base, executing automated checks like linting and tests, and providing a structured recommendation on whether to open a PR or fix issues.

Can I run automated linting and type checks across any codebase before creating a PR?

Yes, you can run automated linting and type checks across typical codebases. The skill requires access to Git, the repository's base branch, and project-specific tooling to perform the automated validation.

How do I get a prioritized task list for code improvements instead of a pull request?

To get a prioritized task list for code improvements instead of a pull request, the skill evaluates your branch changes and returns structured, actionable tasks if the automated checks identify issues that block PR creation.

What's the best way to summarize code diffs and identify potential issues before review?

The best way to summarize code diffs and identify potential issues is through automated branch analysis, which compares changes against the base branch and highlights potential problems before deciding on PR creation.