Skip to content

LeandroBenjaminL/lend-ai / skills/branch-pr

branch-pr

Verified

Enterprise PR workflow — issue-first, branch naming, conventional commits, PR description, and review cycle. PRs under 300 lines. Trigger: When creating a PR, preparing changes for review, or opening a branch.

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

  1. 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 changes

  3. CHOOSE → user confirms

  4. 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

  5. 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_save
  2. 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"
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall