Comprehensive knowledge for creating, managing, and merging pull requests with Jira integration, following best practices for code review, deployment, and team collaboration
View on GitHubJanuary 24, 2026
Select agents to install to:
npx add-skill https://github.com/Lobbi-Docs/claude/blob/main/plugins/jira-orchestrator/skills/pr-workflow/SKILL.md -a claude-code --skill pr-workflowInstallation paths:
.claude/skills/pr-workflow/# PR Workflow Skill Guidance for creating, managing, and merging PRs with Jira integration and deployment best practices. ## Branch Naming Format: `<type>/<jira-key>-<short-description>` **Types:** feature, bugfix, hotfix, refactor, docs, test, chore, perf **Rules:** lowercase, hyphens, max 50 chars, include Jira key Example: `feature/LOBBI-1234-member-dashboard` ## Commit Messages **Format:** ``` <type>(<scope>): <subject> <body> <footer> ``` **Types:** feat, fix, docs, style, refactor, perf, test, chore, build, ci **Rules:** lowercase subject, no period, imperative mood, max 50 chars **Footers:** `Closes PROJ-123`, `BREAKING CHANGE: description`, `Refs PROJ-456` ## PR Title & Description **Title:** `[JIRA-KEY] Type: Brief description` **Description checklist items:** - Jira issue link - Changes made (bullet points) - Technical details (architecture, database, API changes) - Testing: unit, integration, E2E, manual steps - Screenshots/videos if UI changes - Risk assessment (Low/Medium/High/Critical) - Deployment prerequisites & migration steps - Dependencies (related PRs, blocked by, blocks) - Checklist: code style, tests, docs, no console.log, no commented code ## Review Process **Reviewer selection:** 1. Code owner (required, auto-assigned via CODEOWNERS) 2. Subject matter expert (complex/security/performance) 3. Team lead (major architectural changes, breaking changes) **Review labels:** needs-review, needs-changes, approved, security-review, breaking-change, hotfix, size/small|medium|large, wip **Merge requirements:** - All CI/CD checks pass - Required approvals received - Branch up-to-date with main - Documentation complete - Conversations resolved ## Merge Strategies | Strategy | Best For | Benefit | |----------|----------|---------| | **Squash** | Features, bug fixes, WIP commits | Clean history | | **Merge Commit** | Long-lived branches, team effort | Preserves history | | **Rebase** | Clean commits, small focused PRs | Linear history |