create-pull-request

Automates GitHub pull request creation with commit analysis and branch management using the gh CLI.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/alvIndieDevelop/my_care --skill create-pull-request-alvindiedevelop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pull-request
Source: https://github.com/alvIndieDevelop/my_care/tree/main/.kilocode/skills/create-pull-request
Command: npx skills add https://github.com/alvIndieDevelop/my_care --skill create-pull-request-alvindiedevelop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a GitHub pull request following project conventions. Use when the user asks to create a PR, submit changes for review, or open a pull request. Handles commit analysis, branch management, and PR creation using the gh CLI tool.

Core Features & Use Cases

  • PR creation: Create and submit PRs that follow a standardized template and allow reviewers to see the context.
  • Context-aware analysis: Inspect commits to determine sensible base/feature branches and suggested PR messages.
  • Use Case: When a developer finishes a feature, use this to open a PR with a clear title, description, and target base branch.

Quick Start

Create a pull request from the current branch to the main branch using the gh CLI.

Frequently Asked Questions about create-pull-request

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

FAQPage Schema
How do I create a GitHub pull request that follows project conventions?

To create a GitHub pull request that follows project conventions, this Skill automates PR creation by analyzing your commits to determine a sensible base branch and generating a standardized PR title and description using the gh CLI.

How does automated commit analysis work when opening a pull request?

Automated commit analysis inspects your branch history to identify feature and base branches, then uses that context to suggest a clear PR title and description for review, ensuring your pull request aligns with project conventions.

Do I need an authenticated gh CLI session to automate pull request creation?

Yes, an authenticated gh CLI session is required to automate pull request creation. You also need a clean working directory and a sensible base branch to ensure proper commit analysis and branch management during PR submission.

What is the best way to manage feature branches before submitting changes for code review?

The best way to manage feature branches before submitting changes for review is to ensure your working directory is clean. This Skill then guides branch naming and integrates your features into the base branch using the gh CLI.

Can I use this to open a PR with a standardized template for any feature branch?

Yes, you can use this to open a PR with a standardized template for any feature branch. It determines the target base branch from your commits and applies project conventions to generate a clear PR description for reviewers.

Why does pull request automation require a clean working directory?

Pull request automation requires a clean working directory to accurately analyze commits and manage branch integration without conflicts. This ensures the generated PR accurately reflects the feature changes meant for the base branch.