skills.rest
alexica00
alexica00COMMUNITY
Explore all skills by this author →
GitHub

pr

Analyze code changes and generate structured pull request descriptions.

Updated May 30, 2026
Search Tags:#automation#git#code-review#analyze#pull-request#pr-create
One-click install
npx skills add https://github.com/alexica00/claude-code-ultimate-guide --skill pr-alexica00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/alexica00/claude-code-ultimate-guide/tree/main/examples/skills/pr
Command: npx skills add https://github.com/alexica00/claude-code-ultimate-guide --skill pr-alexica00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze changes, detect scope issues, and create a well-structured PR following project conventions.

Core Features & Use Cases

  • Analyze Changes: Evaluate code modifications across commits and files to determine impact.
  • Detect Scope Issues: Warn if the PR is too large or combines unrelated changes.
  • Generate PR Content: Create TLDR, description, and checklist; propose a suitable title and labels for the PR.

Quick Start

Request Claude to generate a PR with a structured title, body, and labels for the current branch.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate pull request creation with a structured description?▼

Automate pull request creation by analyzing code changes to generate a structured PR description, including a TLDR, title, body, and labels. The workflow evaluates modifications across commits and files to determine impact and assemble the content automatically.

Can I check if my pull request is too large or mixes unrelated changes?▼

Checking pull request scope involves analyzing code modifications to detect scope issues and warn if the PR is too large or combines unrelated changes. This ensures the generated PR follows project conventions and maintains a manageable review size.

How do I generate a TLDR and labels for a git pull request?▼

Generate a TLDR and labels for a git pull request by analyzing code changes across commits and files. The analysis proposes a suitable title and labels based on the detected impact, creating a well-structured body for code review workflows.

Does this pull request automation prompt for draft status and target branch?▼

Pull request automation prompts for type, target branch, draft status, and post-PR follow-ups during the creation workflow. This ensures the structured PR description is generated according to specific user inputs and project requirements.

What is the best way to create a PR that follows project conventions?▼

The best way to create a PR that follows project conventions is to analyze changes and detect scope issues before generating the content. This approach assembles a structured title, body, and checklist while warning if the PR combines unrelated modifications.

Related Skills

Explore More Software Engineering Skills→
navidemadnavidemad

publish

Generate conventional commit messages and GitHub pull request descriptions.

Community
Intermediate
module-federationmodule-federation
2.6k

gh-pr-metadata

Normalize GitHub Pull Request titles to conventional commit format and rewrite bodies to match repository templates.

Official
Intermediate
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced
bmad-code-orgbmad-code-org
8

bmad-os-changelog

Generate structured changelog entries from git history and pull request metadata.

Official
Intermediate