creating-pr

Create or update GitHub pull requests with conventional commits.

1.2k|81|Updated Sep 5, 2024
One-click install
npx skills add https://github.com/udecode/dotai --skill creating-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-pr
Source: https://github.com/udecode/dotai/tree/main/.claude-plugin/plugins/git/skills/creating-pr
Command: npx skills add https://github.com/udecode/dotai --skill creating-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github-cli.

What problem does it solve?

This Skill streamlines the creation and updating of GitHub Pull Requests, ensuring high-quality, well-documented changes. It automates branch management, commit best practices, and PR description generation, saving developers time and promoting consistent workflows.

Core Features & Use Cases

  • Automated PR Creation: Generates new pull requests with comprehensive titles and descriptions.
  • Structured Update Comments: Adds detailed comments for each subsequent push to an existing PR, preserving context and tracking changes.
  • Conventional Commit Enforcement: Guides the use of conventional commit messages and branch naming for clear history.
  • Use Case: After completing a feature or bug fix, use this skill to automatically create a new pull request, ensuring all changes are properly documented and ready for review.

Quick Start

Use the creating-pr skill to create a new pull request for my completed feature branch.

Frequently Asked Questions about creating-pr

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

FAQPage Schema
How do I automate pull request creation with GitHub CLI?

Automate pull request creation by using GitHub CLI to generate PRs with structured titles and descriptions from your feature branch. This Skill handles branch management, commit formatting, and comprehensive PR documentation automatically, reducing manual setup and ensuring consistency across your workflow.

What's the best way to maintain conventional commit messages in Git?

Conventional commits follow a structured format (type: description) that clarifies changes in your Git history. This Skill enforces conventional commit formatting alongside branch naming standards, making your commit log readable and enabling automated changelog generation and semantic versioning.

How do I update an existing pull request while preserving its description?

Update existing PRs by adding structured comments that track each push without overwriting the original description. This Skill automates comment generation for subsequent pushes, maintaining full context of changes and review history across multiple iterations.

Can I use this with GitHub repositories and version control workflows?

Yes, this Skill applies to any Git repository using GitHub CLI and works across feature branches, bug fixes, and standard developer workflows. It integrates with your existing version control setup to streamline PR creation and enforce consistent branch and commit practices.

Why should I document pull requests with comprehensive descriptions?

Comprehensive PR descriptions provide reviewers with context, rationale, and change scope upfront, reducing review cycles and improving code quality. This Skill automates description generation based on your commits and branch structure, ensuring every PR includes the information reviewers need.

What happens when I push multiple times to a feature branch?

Each push to an existing PR generates a detailed update comment that preserves the original description while documenting new changes. This Skill automatically structures these updates, creating a clear audit trail of modifications without manual documentation.