pr-conventions

Enforce PR conventions, templates, CLI constraints, and issue linkage during pull request creation.

2|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/stlwolf/ai-development-hub --skill pr-conventions-stlwolf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-conventions
Source: https://github.com/stlwolf/ai-development-hub/tree/main/canonical/skills/pr-conventions
Command: npx skills add https://github.com/stlwolf/ai-development-hub --skill pr-conventions-stlwolf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR creation often lacks consistency and governance across teams, leading to misaligned reviews and slower delivery.

Core Features & Use Cases

  • Enforces mandatory fields and templates during PR creation.
  • Provides guidance on referencing PR templates and CLI constraints.
  • Ensures proper issue linkage and drafting workflow.

Quick Start

Create a new pull request following the standard conventions in place and reference the appropriate template and issues.

Frequently Asked Questions about pr-conventions

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

FAQPage Schema
How do I enforce pull request conventions across my repository workflows?

You can enforce pull request conventions by standardizing PR creation with mandatory templates, CLI constraints, and proper issue linkage to ensure consistent repository collaboration and governance.

How do I link issues and use templates when creating a pull request via CLI?

To link issues and use templates during PR creation, reference the appropriate PR template and associated issue numbers directly in your pull request drafting workflow to satisfy CLI constraints.

Why does PR creation lack consistency and how do templates help?

PR creation lacks consistency due to misaligned reviews and missing governance. Using mandatory PR templates enforces required fields and standardizes the drafting process to accelerate delivery.

Can I use this to standardize code review workflows for my team?

Yes, you can standardize code review workflows by enforcing mandatory fields, referencing PR templates, and applying CLI constraints to streamline reviews and align team collaboration.

What is the best way to manage mandatory fields during pull request drafting?

The best way to manage mandatory fields during PR drafting is to enforce conventions through standardized templates, ensuring all required metadata and issue references are populated before submission.

What are the limitations of enforcing PR conventions without proper issue linkage?

Without proper issue linkage, enforcing PR conventions yields misaligned reviews and slower delivery, as the drafting workflow loses traceability between code changes and tracked repository issues.