skills.rest
JNZader
JNZaderCOMMUNITY
Explore all skills by this author →
GitHub

branch-pr

Automate PR creation and branch management for Agent Teams Lite.

Updated Mar 15, 2026
Search Tags:#automation#workflow#github#pr#pull-request#branch-naming
One-click install
npx skills add https://github.com/JNZader/javi-ai --skill branch-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-pr
Source: https://github.com/JNZader/javi-ai/tree/main/upstream/agent-teams-lite/skills/branch-pr
Command: npx skills add https://github.com/JNZader/javi-ai --skill branch-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Branch-pr automates and enforces a standardized PR workflow for Agent Teams Lite, ensuring issues are linked, exactly one type label is applied, and branch naming rules are followed to improve traceability and code review efficiency.

Core Features & Use Cases

  • Workflow automation to verify issue linkage and enforce exactly one type label on PRs
  • Branch naming validation using a predefined regex and the ability to format branches as type/description
  • PR body templating and mandatory sections to standardize reviews and approvals
  • Use Case: when preparing a PR for an issue, branch must be named correctly and linked, otherwise checks fail

Quick Start

Create a feature branch for an approved issue, then open a PR that adheres to the 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 branch naming conventions and issue linkage when automating pull requests?▼

You can enforce branch naming conventions and issue linkage in pull requests by applying regex validation to branch names, mandating PR body templates, and verifying that exactly one type label is applied before workflow checks pass.

What is the best way to standardize pull request templates for consistent code reviews?▼

The best way to standardize pull request templates is to enforce mandatory PR body sections and apply strict labeling rules, ensuring issues are linked and traceable for efficient code reviews.

How do I validate a branch name format before opening a pull request on GitHub?▼

To validate a branch name format before opening a pull request, apply a predefined regex validation rule that checks your branch structure and formats it as type/description to meet workflow compliance.

Does branch naming automation require any specific dependencies to manage pull request workflows?▼

No specific dependencies are required to manage pull request workflows with branch naming automation, as the skill operates independently to enforce regex validation, labeling rules, and PR body templating.

Why does my pull request workflow fail when multiple type labels are applied?▼

Your pull request workflow fails when multiple type labels are applied because the automation enforces compliance by requiring exactly one type label per PR to maintain clear traceability and review efficiency.

Can I use PR body templating to require linked issues in my GitHub workflow?▼

Yes, you can use PR body templating with mandatory sections to require linked issues in your GitHub workflow, ensuring traceability and enforcing that every pull request is associated with an approved issue.

Related Skills

Explore More Software Engineering Skills→
chf3198chf3198

github-projects-agile-linkage

Implement Jira-like issue taxonomy, dependencies, and branch/PR linkage in GitHub.

Community
Advanced
taloncjonestaloncjones

ship

Automate code review, testing, version bump, merge, and post-merge cleanup for pull requests.

Community
Advanced
AlejandroFerpAlejandroFerp

branch-pr

Enforce issue linkage and single type:* labels on GitHub PRs.

Community
Intermediate
tachfineamnaytachfineamnay

Git Workflow & CI/CD

Standardize Git workflows and CI/CD pipelines with Husky and GitHub Actions.

Community
Intermediate