create-pr

Create GitHub pull requests from branch diffs and commit logs.

157|60|Updated Mar 16, 2024
One-click install
npx skills add https://github.com/genlayerlabs/genlayer-studio --skill create-pr-genlayerlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/genlayerlabs/genlayer-studio/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/genlayerlabs/genlayer-studio --skill create-pr-genlayerlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of GitHub pull requests, ensuring consistency and adherence to project templates by analyzing branch differences and commit history.

Core Features & Use Cases

  • Automated PR Generation: Creates pull requests with pre-defined titles and bodies based on project conventions.
  • Contextual Analysis: Gathers branch information, diffs against the main branch, and commit logs to inform PR content.
  • Use Case: After completing a feature on a new branch, use this Skill to generate a well-formatted pull request, including issue tracking and testing details, ready for review.

Quick Start

Use the create-pr skill to generate a pull request for your current branch.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate GitHub pull request creation from branch diffs and commit logs?

Automating GitHub pull request creation analyzes your branch diffs and commit logs against the main branch to generate PRs. This skill uses project templates to format titles and bodies, incorporating conventional commit types and issue tracking links.

Do I need the GitHub CLI authenticated to automate pull request generation?

Yes, you need the GitHub CLI (`gh`) authenticated to automate pull request generation. The skill relies on this dependency to interact with your repository and create pull requests directly from your feature branch.

Can I use conventional commit types and project templates for PR titles and bodies?

Yes, you can use conventional commit types and project templates for PR titles and bodies. The skill analyzes your commit history to ensure the generated pull request adheres to your project's specific formatting conventions.

What's the best way to generate a well-formatted pull request after committing changes locally?

The best way to generate a well-formatted pull request after committing changes locally is to run this skill on your feature branch. It evaluates your branch differences and automatically populates the PR body with issue tracking and testing details.

Why does automated PR creation require changes to be committed locally on a feature branch?

Automated PR creation requires changes to be committed locally on a feature branch because the tool analyzes your commit logs and branch diffs against the main branch. Uncommitted changes cannot be parsed to generate the pull request title and body.