create-pr_skill

This skill automates pull request creation using GitHub CLI, generates conventional-commit-based titles and bodies for clear, high-quality PRs.

TypeScript

181

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill first-fluke/fullstack-starter --skill create-pr

SKILL.md1.3 KB

Overview

This skill automates creation of clear, consistent Pull Requests using the GitHub CLI. It parses conventional commits to produce concise titles and structured bodies that include summaries, issue links, and verification steps. It reduces manual formatting and helps maintain high-quality PRs across a monorepo with multiple services and languages.

How this skill works

The skill inspects the local git log and detects conventional commit tags like feat, fix, and chore to generate a meaningful PR title. It composes a detailed body that summarizes changes, references related issues, and adds suggested verification steps. Finally, it invokes the GitHub CLI (gh pr create) to open the PR interactively or with supplied flags for full automation.

When to use it

Creating a PR after finishing a focused change or feature branch.
Opening a PR in a large monorepo where consistent descriptions help reviewers.
Linking commits to issues or tasks automatically during PR creation.
Automating CI-driven PR creation in scripts or pipelines.
When you want standardized titles and verification instructions for every PR.

Best practices

Keep each PR small and focused on a single logical change to simplify review.
Use conventional commit messages so generated titles and summaries are accurate.
Always link related issues or tasks (e.g., "Closes #123") in the PR body.
Run a quick self-review of the diff before creating the PR, even when automating.
Include concrete verification steps and artifacts (screenshots, test output) in the generated body.

Example use cases

Developer finishes a feature branch; run gh pr create to generate a title from commit messages and open the PR.
Automated CI job creates a PR for dependency updates with a standardized body and linked issue.
Maintainer submits a hotfix branch; tool generates a concise "fix:" title and verification checklist.
Repo templates and multi-service changes in a monorepo get uniform PR descriptions for easier cross-team review.
Scripting full automation: pass --title and --body flags to skip interactive prompts for machine-generated changes.

FAQ

You must have the GitHub CLI (gh) installed and authenticated, and the local branch must contain commits not yet pushed to the target remote branch.

Can I override the generated title or body?

Yes. You can run gh pr create interactively or pass --title and --body flags to provide a custom title and description.