How do I install the Branch Pr skill?

Run npx skillmds@latest add leandrobenjaminl/branch-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Branch Pr safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Branch Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Branch Pr free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Branch Pr?

LeandroBenjaminL (@leandrobenjaminl) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Branch Pr by leandrobenjaminl — Agent Skill

Name: Branch Pr
Rating: 4.2 (5 reviews)
Author: LeandroBenjaminL

File contents

Skill: branch-pr

Enterprise PR workflow. Small PRs, clear descriptions, review before merge.

Trigger

You're creating a new branch to work on an issue
Changes are ready and you need to open a PR
Someone requested a review on your PR
A PR is too large and needs splitting (> 300 lines)

Workflow LEND

ANALYZE ├── Issue: is there an associated issue? what does it solve? ├── Scope: how many files? how many lines? (> 300 → chained-pr) ├── Base branch: main, develop, or feature branch? └── Dependencies: does this PR block or depend on others?
OFFER (Senior Menu) ├── A) Simple branch + PR — direct branch + PR with minimal template ├── B) PR with description — context, changes, testing, screenshots └── C) Structured PR — issue link, description, checklist, breaking changes
CHOOSE → user confirms
EXECUTE ├── Branch name: type/issue-number-description (feat/123-login, fix/45-crash) ├── Format types: feat/, fix/, chore/, docs/, refactor/, test/ ├── Commits: conventional commits in English, atomic ├── PR description: what, why, how, testing evidence, screenshots ├── Template: context, changes, testing, checklist for reviewer ├── Small PR: < 300 lines. If larger → chained-pr ├── Labels: feat, fix, chore, breaking, needs-review └── REVIEW CYCLE: author opens → reviewer approves/requests changes → author updates → merge
VERIFY ├── The PR has a clear description ├── Tests pass in CI ├── No conflicts with the base branch └── Reviewer is assigned

Post-task (always)

Save this task to Engram with mem_save
Review if documentation needs updating (README, AGENTS.md, ARCHITECTURE.md)
If docs changed → include in the same PR/commit

Patterns

Issue-first: every branch/PR comes from an issue
Small PRs: < 300 lines, one logical change
Branch naming: type/issue-number-description
PR description: what, why, how, screenshots, testing
Review cycle: author opens → reviewer feedback → author updates → merge

Anti-patterns

❌ PRs without an associated issue
❌ PRs with 1000+ lines — split them with chained-pr
❌ PR descriptions without context — "fixes stuff" is not a description
❌ Merging without review
❌ Branch names like "fix-stuff" or "asd123"

---name: branch-prdescription: Guides creating small, issue-linked pull requests with conventional branch naming, commit messages, and structured descriptions, plus a review cycle.license: MIT---# Skill: branch-prEnterprise PR workflow. Small PRs, clear descriptions, review before merge.## Trigger- You're creating a new branch to work on an issue- Changes are ready and you need to open a PR- Someone requested a review on your PR- A PR is too large and needs splitting (> 300 lines)## Workflow LEND1. ANALYZE ├── Issue: is there an associated issue? what does it solve? ├── Scope: how many files? how many lines? (> 300 → chained-pr) ├── Base branch: main, develop, or feature branch? └── Dependencies: does this PR block or depend on others?2. OFFER (Senior Menu) ├── A) Simple branch + PR — direct branch + PR with minimal template ├── B) PR with description — context, changes, testing, screenshots └── C) Structured PR — issue link, description, checklist, breaking changes3. CHOOSE → user confirms4. EXECUTE ├── Branch name: `type/issue-number-description` (feat/123-login, fix/45-crash) ├── Format types: feat/, fix/, chore/, docs/, refactor/, test/ ├── Commits: conventional commits in English, atomic ├── PR description: what, why, how, testing evidence, screenshots ├── Template: context, changes, testing, checklist for reviewer ├── Small PR: < 300 lines. If larger → chained-pr ├── Labels: feat, fix, chore, breaking, needs-review └── REVIEW CYCLE: author opens → reviewer approves/requests changes → author updates → merge5. VERIFY ├── The PR has a clear description ├── Tests pass in CI ├── No conflicts with the base branch └── Reviewer is assigned### Post-task (always)1. Save this task to Engram with mem_save2. Review if documentation needs updating (README, AGENTS.md, ARCHITECTURE.md)3. If docs changed → include in the same PR/commit## Patterns- **Issue-first**: every branch/PR comes from an issue- **Small PRs**: < 300 lines, one logical change- **Branch naming**: `type/issue-number-description`- **PR description**: what, why, how, screenshots, testing- **Review cycle**: author opens → reviewer feedback → author updates → merge## Anti-patterns- ❌ PRs without an associated issue- ❌ PRs with 1000+ lines — split them with chained-pr- ❌ PR descriptions without context — "fixes stuff" is not a description- ❌ Merging without review- ❌ Branch names like "fix-stuff" or "asd123"

Frequently asked questions

Branch Pr