create-pr

Create pull requests with conventional commits and templated PR bodies.

11|2|Updated Apr 7, 2022

Search Tags:#automation #branching #pr #code-review #git-workflow #pull-request #conventional-commits

Ready to run

npx skills add https://github.com/nullhack/temple8 --skill create-pr-nullhack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/nullhack/temple8/tree/main/.opencode/skills/create-pr
Command: npx skills add https://github.com/nullhack/temple8 --skill create-pr-nullhack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the PR workflow by enforcing conventional commits, standardized branch naming, and automated PR creation, reducing review drift and merge conflicts.

Core Features & Use Cases

Enforces conventional commit messages and consistent PR formatting.
Supports feature, bugfix, and chore branches with descriptive titles.
Provides a templated PR body and reviewer checklist to speed approvals.

Quick Start

Provide a feature branch name and a concise description, then run the skill to create the PR.

Frequently Asked Questions about create-pr

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

FAQPage Schema

How do I automate pull request creation with conventional commits?▼

Automating pull request creation with conventional commits requires standardizing branch naming and PR body templating. This skill enforces conventional commit structure and generates templated PR bodies to reduce review drift and merge conflicts.

What is the best way to enforce conventional commit messages in a git workflow?▼

The best way to enforce conventional commit messages in a git workflow is by applying standardized branch naming and PR body templating. This ensures feature, bugfix, and chore branches maintain consistent titles and reviewer checklists for faster approvals.

How do I create a pull request using conventional commits for a feature branch?▼

To create a pull request using conventional commits, provide a feature branch name and a concise description. The skill automates the formatting, applying conventional commit structure and branch naming conventions to generate the PR.

Can I use a templated PR body and reviewer checklist for code reviews?▼

Yes, you can use a templated PR body and reviewer checklist to speed up code approvals. The skill provides standardized PR body templating and integrates reviewer checklists to ensure code-review traces and reproducible branching.

Does this PR automation tool work without external dependencies?▼

Yes, the PR automation tool works without external dependencies. It operates independently to enforce conventional commit messages, standardize branch naming, and automate PR creation for software teams requiring reproducible workflows.

When should I not use automated conventional commit PR creation?▼

You should not use automated conventional commit PR creation if your software team does not require standardized PRs or strict conventional commit structure. It is designed for teams needing code-review traces and reproducible branching for feature work and bug fixes.