br4zz4:pr

Creates GitHub pull requests from the current branch using the project PR template.

Updated May 25, 2025
One-click install
npx skills add https://github.com/oporpino/commons --skill br4zz4-pr-oporpino
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: br4zz4:pr
Source: https://github.com/oporpino/commons/tree/main/ai/shared/skills/br4zz4%3Apr
Command: npx skills add https://github.com/oporpino/commons --skill br4zz4-pr-oporpino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Opening a pull request often involves repetitive manual work: analyzing the diff, filling the PR template, enforcing team conventions like file-count limits, and linking the PR to an Asana task. This Skill automates that entire flow so every PR follows the same standard. ## Core Features & Use Cases - Template-driven PR creation: Detects or installs .github/PULL_REQUEST_TEMPLATE.md and fills TLDR, CONTEXT, CHANGES, HOW TO TEST, and RELATED sections. - File-count guardrails: Counts only code files (excluding docs and rules), warns above 5 files, and blocks PRs over 10 files unless it is a rename refactor, proposing splits by well-defined context. - Asana integration: Requires every PR to link to an Asana subtask and adds a ## Related section with parent task and subtask links. - PR sequencing: Supports a ## SEQUENCE section for dependent PRs that must merge in a fixed order. - Use Case: After finishing a feature branch, ask for a PR and get a fully filled template, an Asana-linked subtask, and a gh pr create call targeting main or any branch you specify. ## Quick Start Ask the assistant to create a pull request from the current branch to main using this skill.

Frequently Asked Questions about br4zz4:pr

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

FAQPage Schema
How do I create a GitHub pull request from the command line?▼

Use the GitHub CLI with `gh pr create --base <branch> --title "<title>" --body "<body>"`. This skill automates that call after analyzing the diff with git log and git diff, then filling the project PR template sections.

How do I fill a GitHub PR template automatically?▼

The skill checks for `.github/PULL_REQUEST_TEMPLATE.md`, copying a default template if missing, then fills TLDR, CONTEXT, CHANGES, HOW TO TEST, and RELATED sections based on the commits and diff between the base branch and HEAD.

Can I open a pull request to a branch other than main?▼

Yes. The default target is `main`, but saying "pr to staging" or naming any branch overrides the base. The skill passes that branch to `gh pr create --base`.

What happens if my pull request changes too many files?▼

The skill counts only code files, excluding markdown, docs, rules, and skills directories. Above 5 files it asks whether to split; above 10 it blocks the PR unless it is a rename refactor and proposes a split by well-defined context.

Does this workflow require linking PRs to Asana tasks?▼

Yes. Every PR must link to an Asana subtask whose name matches the PR title, and the PR body must end with a `## Related` section containing the parent task and subtask URLs. PRs without a linked subtask are not opened.