skills.rest
RamonsDka
RamonsDkaCOMMUNITY
Explore all skills by this author →
GitHub

branch-pr

Enforce issue linkage, single type labels, and standardized PR bodies.

1|1|Updated Apr 19, 2026
Search Tags:#workflow#templates#code-review#pull-request#conventional-commits#branch-naming
One-click install
npx skills add https://github.com/RamonsDka/the-architect-overlay --skill branch-pr-ramonsdka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-pr
Source: https://github.com/RamonsDka/the-architect-overlay/tree/main/skills/branch-pr
Command: npx skills add https://github.com/RamonsDka/the-architect-overlay --skill branch-pr-ramonsdka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR governance and consistency across teams is hard. This skill defines a structured process for creating pull requests that ensures issue linkage, single type labeling, and automated quality checks before merging.

Core Features & Use Cases

  • Enforces that every PR links to an approved issue.
  • Requires exactly one type:* label per PR.
  • Provides a PR body template and a standard naming convention for branches.
  • Integrates with automated checks to gate merges.
  • Supports scenarios such as feature development, bug fixes, documentation changes, and maintenance tasks.

Quick Start

Create a branch using type/description, implement changes, and open a PR following the prescribed template and labeling rules.

Frequently Asked Questions about branch-pr

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

FAQPage Schema
How do I enforce issue linkage and standardized PR bodies in a pull request workflow?▼

To enforce issue linkage and standardized PR bodies in a pull request workflow, you need a governance process that mandates approved issue references and provides a strict PR template before allowing merges.

What is the best way to maintain consistent branch naming conventions across feature and bugfix branches?▼

The best way to maintain consistent branch naming conventions is to apply a structured type/description format for feature, bugfix, and docs branches, ensuring traceability and standardized categorization across your codebase.

How do I require exactly one type label per pull request before merging?▼

To require exactly one type label per pull request before merging, implement automated PR checks that validate single type:* label assignment and block the merge if the labeling rules are violated.

Does conventional commit governance work for both bug fixes and documentation changes?▼

Yes, conventional commit governance works for both bug fixes and documentation changes by applying standardized branch naming and mandatory issue linkage across all supported branch types.

What are the prerequisites for automating PR governance and gating merges?▼

Prerequisites for automating PR governance include having an approved issue status, a defined PR body template, and conventional commit rules configured to gate merges before pull requests can be merged.

Why do I need an approved issue linked to my pull request?▼

You need an approved issue linked to your pull request to guarantee traceability and ensure that all code changes pass mandatory quality checks before entering the main branch.

Related Skills

Explore More Software Engineering Skills→
leeoohooleeoohoo
1

pr-creator

Create pull requests with repository templates and conventional commit titles via gh CLI.

Community
Intermediate
yutnayutna
2

quality-gates

Run type checks, linting, tests, and verification handoff in canonical order.

Community
Advanced
chiruu12chiruu12
1

ship

Automate software deployment with Git branch management, testing, and pull requests.

Community
Advanced
jguadagnojguadagno
18

pr-guardrails

Enforce branch naming, PR formatting, and issue linkage in GitHub workflows.

Community
Basic