pr-template-builder

Creates GitHub pull request, issue, and discussion templates with YAML configuration.

2|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/sathishssj3/NexVR-Engine --skill pr-template-builder-sathishssj3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-template-builder
Source: https://github.com/sathishssj3/NexVR-Engine/tree/main/.agents/skills/pr-template-builder
Command: npx skills add https://github.com/sathishssj3/NexVR-Engine --skill pr-template-builder-sathishssj3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up consistent GitHub collaboration templates is repetitive and error-prone, and teams often ship repositories without structured PR checklists, issue forms, or contribution guidelines. ## Core Features & Use Cases - PR Templates: Generate default and specialized pull request templates (feature, bugfix, hotfix) with checklists, testing sections, and rollback plans. - Issue & Discussion Forms: Create YAML-based bug report and feature request forms with required fields, dropdowns, and validation, plus a config.yml to control issue creation flow. - Governance Files: Produce CODEOWNERS, CONTRIBUTING.md, and auto-labeling workflows (labeler.yml, PR size labels) to automate review assignment and categorization. - Use Case: When open-sourcing a project, generate the entire .github/ directory—PR template, issue forms, CODEOWNERS, and labeler workflows—in one pass so contributors follow a consistent process from day one. ## Quick Start Ask the AI to create a complete set of GitHub PR and issue templates for your repository, including a bug report form and CODEOWNERS file.

Frequently Asked Questions about pr-template-builder

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

FAQPage Schema
How do I create a pull request template on GitHub?▼

Add a PULL_REQUEST_TEMPLATE.md file to the .github/ directory with sections for summary, related issues, type of change, testing, and a reviewer checklist. For multiple templates, place separate markdown files in .github/PULL_REQUEST_TEMPLATE/.

How to create GitHub issue templates with YAML forms?▼

Create YAML files in .github/ISSUE_TEMPLATE/ defining form fields like textareas, dropdowns, and checkboxes with required validations. Add a config.yml to disable blank issues and link to documentation or community channels.

What is a CODEOWNERS file and how does it work?▼

CODEOWNERS is a file in .github/ that maps file paths or glob patterns to GitHub teams or users. GitHub automatically requests reviews from matching owners when a pull request touches those files.

Can GitHub automatically label pull requests?▼

Yes, use the actions/labeler workflow with a labeler.yml config mapping labels to changed file globs, such as frontend or backend paths. A PR size labeler action can also tag PRs as XS through XL based on line counts.

Should I use markdown or YAML for GitHub issue templates?▼

YAML forms provide a better experience with structured fields, required validation, and dropdowns, while markdown templates are simpler free-form text. YAML forms are recommended for bug reports and feature requests.