Does it support different Conventional Commit types?

Yes, it supports all standard types including feat, fix, chore, docs, refactor, test, perf, style, ci, and build, prioritizing them based on the primary change.

Will it push my code to the remote repository?

Yes, the skill automatically checks if your current branch has an upstream tracking relationship and pushes the code before attempting to create the PR.

What tools are required for this skill to work?

This skill requires both Git and the GitHub CLI (gh) to be installed and authenticated on your system to analyze changes and create the PR.

Can I use this for non-draft pull requests?

By default, this skill creates draft pull requests to allow for final verification and to prevent accidental merges before the code is ready.

Standardized PR Creator

Name: Standardized PR Creator
Author: kkhys

bykkhys

•

Collaboration Tools

Automates the creation of GitHub pull requests with standardized Conventional Commit titles, draft status, and concise summaries.

About

The Standardized PR Creator skill streamlines the GitHub contribution workflow by managing the entire pull request lifecycle from your terminal. It analyzes your git changes to determine the appropriate Conventional Commits type, formats a standardized title including the target branch, and generates a bulleted description of your technical changes. By handling the branch pushing, draft status, and assignee settings automatically through the GitHub CLI, it ensures consistent repository standards and reduces the manual effort required to move code from local development to peer review.

Key Features

Ensures local branches are pushed to remote before PR execution
Automated summary generation using concise, imperative-mood bullet points
1 GitHub stars
Standardized title formatting using the [base-branch] type: description pattern
Enforces draft PR status and specific assignee requirements for consistency
Automatic Conventional Commit type detection based on git diffs

Use Cases

Maintaining a consistent git history and PR naming convention across a project
Generating technical change logs for reviewers without manual typing
Opening a draft pull request immediately after completing a feature or bug fix

About

Key Features

Ensures local branches are pushed to remote before PR execution
Automated summary generation using concise, imperative-mood bullet points
1 GitHub stars
Standardized title formatting using the [base-branch] type: description pattern
Enforces draft PR status and specific assignee requirements for consistency
Automatic Conventional Commit type detection based on git diffs

Use Cases

Maintaining a consistent git history and PR naming convention across a project
Generating technical change logs for reviewers without manual typing
Opening a draft pull request immediately after completing a feature or bug fix