pr-creator

Create GitHub pull requests with template checklists and conventional commit titles.

Updated Aug 30, 2025
One-click install
npx skills add https://github.com/vonomarap/kanokna --skill pr-creator-vonomarap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-creator
Source: https://github.com/vonomarap/kanokna/tree/main/.agents/skills/pr-creator
Command: npx skills add https://github.com/vonomarap/kanokna --skill pr-creator-vonomarap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures contributors create pull requests that strictly follow the repository's templates and standards to reduce review friction, omissions, and CI breakage.

Core Features & Use Cases

  • Branch management guidance to avoid working directly on main and to create descriptive feature branches.
  • Template discovery and adherence by locating and reading repository PR templates and preserving required headings and checklists.
  • Drafting compliant PR descriptions, linking related issues, performing preflight build/test checks, and producing a gh CLI invocation to create the PR.
  • Use case: When preparing a feature or bugfix PR, produce a ready-to-submit PR description that fills the template checklists, notes related issues, and includes a conventional-commit style title.

Quick Start

Create a pull request description for branch feature/login that follows the repository's PR template, marks completed checklist items, links related issues, and outputs the gh pr create command with a body file.

Frequently Asked Questions about pr-creator

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

FAQPage Schema
How do I create a GitHub pull request that follows a repository's PR template?

To create a compliant GitHub pull request, the Skill discovers and parses the repository's PR template, preserves required headings, populates checklists, links related issues, and outputs a gh pr create command with a conventional-commit style title and body file.

What is the best way to generate a conventional commit title for a pull request?

Generating a conventional commit title for a pull request involves drafting a compliant PR description that adheres to repository standards, filling template checklists, and producing a gh CLI invocation with a properly formatted conventional-commit style title.

How do I ensure my feature branch passes preflight checks before opening a PR?

To ensure your feature branch passes preflight checks before opening a PR, the Skill runs preflight build and test checks, verifies branch management guidance to avoid working directly on main, and generates a ready-to-submit PR description file.

Does this PR generation tool work with gh CLI and existing GitHub PR templates?

Yes, this PR generation tool works with gh CLI by producing a gh pr create invocation with a description file, and it strictly adheres to existing GitHub PR templates by locating, reading, and preserving required headings and checklists.

Can I use this for bug fix and documentation PRs or is it only for features?

You can use this for bug fix, documentation, and refactor PRs. The Skill applies to GitHub repositories when opening PRs for features, bug fixes, refactors, or documentation where conventional commit titles and template checklists are enforced.

Why do my pull requests fail repository checklist requirements?

Pull requests fail repository checklist requirements when required headings and checklists are omitted. The Skill solves this by discovering repository PR templates, marking completed checklist items, linking related issues, and ensuring strict template adherence.