branch-pr

Enforce issue-linked pull request workflows with type/description branches and conventional commits.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/dtaborda/startup-saas-template --skill branch-pr-dtaborda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch-pr
Source: https://github.com/dtaborda/startup-saas-template/tree/main/skills/branch-pr
Command: npx skills add https://github.com/dtaborda/startup-saas-template --skill branch-pr-dtaborda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The branch-pr skill prevents undisciplined pull requests by mandating linked, approved issues, type:* labeling, and automated checks before any merge attempt.

Core Features & Use Cases

  • Issue linkage enforcement: Requires every PR to reference an approved issue and the status:approved label through the designated keywords.
  • Branch-and-PR discipline: Prescribes type/description branch names, conventional commit messages, and PR templates to align with team conventions.
  • Automated validation: Ensures shellcheck runs on scripts, single type:* labels, and CI jobs validating PR content before approval.

Quick Start

Apply the branch-pr checklist by confirming the approved issue link, using a type/description branch name, and adding the required type:* label before opening the PR.

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-linked pull request creation in my Git workflow?

Issue-linked pull request creation is enforced by requiring approved issue references, status:approved labels, and designated keywords before allowing any merge attempts. This workflow mandates structured branch naming and conventional commits.

What are the requirements for branch naming and conventional commits when opening a pull request?

Branch naming and conventional commits require type/description branch formats and structured commit messages. These align with team conventions and PR templates to ensure automated validation and single type:* labeling.

How do I validate pull request content with CI jobs before approval?

Pull request content validation with CI jobs is achieved by ensuring shellcheck runs on scripts, single type:* labels are applied, and PR templates are completed. These automated checks must pass before approval.

Can I open a pull request without an approved issue label?

Opening a pull request without an approved issue label is blocked. Every PR must reference an approved issue carrying the status:approved label through designated keywords to satisfy the workflow checklist.

Why does my pull request fail CI validation during automated checks?

Pull request CI validation fails when shellcheck is not run on scripts, multiple type:* labels are applied, or PR templates are incomplete. The workflow mandates these automated checks pass before approval.

What is the best way to maintain issue-first PR discipline for Agent Teams Lite?

Issue-first PR discipline is maintained by applying a checklist confirming approved issue links, type/description branch names, conventional commit messages, and required type:* labels before opening any pull request.