Raise Pull Requests

Raise high-quality pull requests that are easy to review, provide clear context, and follow team conventions. Use when a user asks to open, write, prepare, or submit a pull request. Covers PR sizing, self-review, writing descriptions, submitting PRs, responding to review feedback, and reviewing others' PRs. Follows GitHub best practices for collaboration and code review.

23 stars 2 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add willvelida/code-minions --skill raise-pull-requests
Manual install
git clone --depth 1 https://github.com/willvelida/code-minions.git /tmp/code-minions
mkdir -p ~/.claude/skills
cp -r /tmp/code-minions/packages/raise-pull-requests/skills/raise-pull-requests ~/.claude/skills/raise-pull-requests

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Raise Pull Requests

## Overview

A skill for raising pull requests that are easy to review, clearly described, and follow team conventions. Good pull requests reduce review time, catch bugs earlier, and keep the team informed about what is changing and why.

This skill covers the full lifecycle of a pull request — from preparing your changes through responding to review feedback.

## Principles

### 1. Write Small, Focused Pull Requests

Each PR should fulfill a single purpose. Small PRs are easier and faster to review, leave less room for bugs, and provide a clearer history of changes. If your change touches multiple concerns, split it into separate PRs.

### 2. Provide Context and Guidance

Reviewers should not have to guess what your PR does or why. Write clear titles and descriptions, link related issues, and guide reviewers through the changes — especially when the PR touches multiple files.

### 3. Review Your Own Work First

Before requesting review, read through your own diff. Build and test locally. Catch typos, leftover debug code, and missing edge cases before someone else does.

### 4. Keep Your Team Informed

Use labels, linked issues, and project boards to make progress visible. A well-structured PR doubles as a status update — reducing the need for separate check-ins.

### 5. Respond Constructively to Feedback
Read the full skill on GitHub

Details

Skill name
raise-pull-requests
Path
packages/raise-pull-requests/skills/raise-pull-requests/SKILL.md
License
Apache-2.0
Repo updated
11 June 2026

FAQ

What does the Raise Pull Requests skill do?

Raise high-quality pull requests that are easy to review, provide clear context, and follow team conventions. Use when a user asks to open, write, prepare, or submit a pull request. Covers PR sizing, self-review, writing descriptions, submitting PRs, responding to review feedback, and reviewing others' PRs. Follows GitHub best practices for collaboration and code review.

How do I install the Raise Pull Requests skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add willvelida/code-minions --skill raise-pull-requests. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Raise Pull Requests popular?

It lives in willvelida/code-minions, which has 23 GitHub stars and 2 forks.

Related skills

Creating Agent Skill

23

willvelida/code-minions

Create and review Agent Skills that follow the open Agent Skills specification and best practices. Use when a user asks to create a new skill, build skill instructions, generate a SKILL.md file, review an existing skill for compliance, or improve skill quality. Covers skill structure, naming conventions, progressive disclosure, writing effective descriptions, creating actions and standards, and validation.

AI, LLMs & Agents

Creating Agents

23

willvelida/code-minions

Create and review agent definition files (agents.md) that give AI coding agents a clear persona, project knowledge, executable commands, code style examples, and explicit boundaries. Use when a user asks to create an agent, define an agent persona, write an agents.md file, set up a custom Copilot agent, review an existing agent definition, or improve agent quality. Covers the six core areas: commands, testing, project structure, code style, git workflow, and boundaries.

AI, LLMs & Agents

Creating Devcontainers

23

willvelida/code-minions

Create and review DevContainer configurations that follow organisational standards. Use when a user asks to set up a dev container, configure a development environment, create a devcontainer.json, add lifecycle hooks, review an existing DevContainer for compliance, or improve container security. Covers base images, features, extensions, lifecycle hooks, and security hardening.

Security

Sharing Skills

43

lifangda/claude-plugins

Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository

Git & Code Review13

Merge

40

ArogyaReddy/alirezarezvani-claude-skills

Merge the winning agent's branch into base, archive losers, and clean up worktrees.

Git & Code Review11

Spawn

40

ArogyaReddy/alirezarezvani-claude-skills

Launch N parallel subagents in isolated git worktrees to compete on the session task.

Git & Code Review11

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.