create-pr

Create GitHub pull requests with titles and bodies from code diffs.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/arakitakashi/homework-coach-robo --skill create-pr-arakitakashi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/arakitakashi/homework-coach-robo/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/arakitakashi/homework-coach-robo --skill create-pr-arakitakashi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of GitHub pull requests, streamlining the code review and submission process.

Core Features & Use Cases

  • Automated PR Creation: Generates pull requests by analyzing code changes and crafting descriptive titles and bodies.
  • Delegated Analysis: Offloads diff analysis and PR body generation to a sub-agent to minimize main agent context usage.
  • Use Case: After committing your code changes, you can invoke this skill to automatically create a pull request for review, complete with a well-formatted title and a summary of your changes.

Quick Start

Use the create-pr skill to generate a pull request for your latest changes.

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 my code commits?

Automating GitHub pull request creation involves analyzing code diffs and commit logs to generate a formatted PR title and body. This Skill delegates diff analysis to a sub-agent, minimizing main agent context usage while automatically crafting conventional commit titles and descriptive PR summaries for code review.

How does AI generate a PR body from a git diff?

AI generates a PR body by delegating diff analysis to a sub-agent that reads your code changes and commit logs. It formulates a descriptive summary of the modifications, ensuring the main agent's context remains uncluttered while producing an accurate representation of your code changes for reviewers.

Can I use conventional commit messages for automated pull request titles?

Yes, you can use conventional commit messages for automated pull request titles. The Skill adheres to conventional commit message formats when generating PR titles, ensuring your automated code review submissions maintain consistent and standardized naming conventions across your repository.

Do I need to manually stage files before creating a pull request with AI?

You need to have your code changes committed before initiating PR creation. The Skill analyzes existing commit logs and code diffs to generate the pull request, meaning your local repository changes should be finalized and committed to the git history before invoking the automation.

What is the best way to create a GitHub PR for code review without writing the description manually?

The best way to create a GitHub PR without manual writing is to use an AI-assisted automation tool. By offloading diff analysis and PR body generation to a sub-agent, it reads your code changes and automatically crafts a comprehensive summary and conventional commit title for your review.

Why does the main agent lose context when generating large pull requests?

The main agent loses context when generating large pull requests because processing extensive code diffs consumes significant context window space. This Skill mitigates that limitation by delegating diff analysis and PR body generation to a dedicated sub-agent, preserving the main agent's context for other tasks.