pr-creation

Automate Git pull request creation with verification, diff review, and conventional commits.

289|16|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/evrendom/rudel --skill pr-creation-evrendom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-creation
Source: https://github.com/evrendom/rudel/tree/main/.claude/skills/pr-creation
Command: npx skills add https://github.com/evrendom/rudel --skill pr-creation-evrendom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end PR preparation process by running verification, diff review, committing changes, and creating PRs with consistent metadata, reducing manual errors and saving time.

Core Features & Use Cases

  • Run verification (type-check, lint, tests) across the monorepo to ensure changes are safe to merge.
  • Review the workspace diff to understand the scope of changes before committing.
  • Commit and push changes using conventional-commit messages to maintain a clean history.
  • Create a PR with a properly formatted title and description, ensuring metadata consistency across merges.

Use Case: When contributing a large feature branch, this skill enforces QA steps, guardrails, and standardized PR metadata to accelerate reviews.

Quick Start

Enable the PR creation workflow on your feature branch to automatically verify, review changes, commit, push, and open the PR with conventional-commit metadata.

Frequently Asked Questions about pr-creation

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

FAQPage Schema
How do I automate a pull request workflow with built-in verification and conventional commits?

Automating a pull request workflow involves running type-checks, linting, and tests, reviewing the diff, and opening a PR with conventional commit metadata. This skill coordinates the end-to-end process to reduce manual errors and enforce QA guardrails.

What is the best way to ensure consistent PR metadata across a collaborative Git repository?

Ensuring consistent PR metadata requires formatting titles and descriptions with conventional commits. This skill automates the generation and submission of standardized metadata during the pull request creation process.

Do I need a specific Git environment setup to automate pull request creation end-to-end?

Automating pull request creation requires a configured Git repository with a remote origin. You also need tools such as bun, gh, and a workspace-diff utility to perform verification, diff analysis, and PR creation.

Can I enforce code review guardrails and tests before pushing a feature branch?

Enforcing code review guardrails is handled by running verification across the workspace to ensure changes are safe to merge. This skill performs diff analysis and executes type-checks, lint, and tests before committing and pushing.

Does this PR automation tool work for monorepos to verify changes before committing?

PR automation for monorepos runs verification across the entire workspace to ensure changes are safe. It reviews the workspace diff to understand the scope of changes before committing and pushing the feature branch.

Why should I use an automated pull request workflow instead of manual git commands?

Using an automated pull request workflow reduces manual errors and saves time by enforcing QA steps and standardized metadata. It coordinates verification, diff review, committing, pushing, and PR creation into a single process.