pr-workflow
/pr-workflow
Prowadzi przez tworzenie, zarządzanie i scalanie pull requestów powiązanych ze zgłoszeniami Jira, w tym prośby o review.
- Autor
- TheLobbi ↗
- Repozytorium
- claude ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 22.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 4
Brak sygnałów. Repozytorium zmienione 22.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Prowadzi przez tworzenie, zarządzanie i scalanie pull requestów powiązanych ze zgłoszeniami Jira, w tym prośby o review.
Wyzwalacze z opisu
Oryginalny opis (EN)
This skill should be used when the user asks to "create a PR", "open a pull request", "merge changes", "set up a git/PR workflow", or "request review" — creating, managing, and merging pull requests linked to Jira issues.
Jak działa
- Branch Naming
- Commit Messages
- PR Title & Description
- Review Process
- Merge Strategies
- Jira Integration
- Deployment
- Common Workflows
- Troubleshooting
- PR Size Guidelines
Podgląd SKILL.md
--- name: pr-workflow description: This skill should be used when the user asks to "create a PR", "open a pull request", "merge changes", "set up a git/PR workflow", or "request review" — creating, managing, and merging pull requests linked to Jira issues. version: 1.0.0 trigger_phrases: [create PR, pull request, merge changes, git workflow, review request] categories: [git, pr, workflow, deployment, code-review] author: Claude Orchestration created: 2025-12-17 updated: 2025-12-17 --- # 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 | **Decision Matrix:** - Feature + WIP commits → Squash - Hotfix (single commit) → Rebase - Large feature (team) → Merge Commit - Bug fix (2-3 commits) → Squash - Refactor (logical steps) → Merge Commit ## Jira Integration **Automatic linking:** Include Jira key in branch name, PR title, or commits **Status transitions:** - PR opened → To Do → In Progress - Ready for review → In Review - Changes requested → In Progress - Approved → Ready for Merge - Merged → Done - Closed (not merged) → Cancelled **Automatic Jira comments post:** - PR opened notification with metadata - Status updates on approval - Merge/close notifications ## Deployment **Risk assessment checklist:** - Database schema changes - API breaking changes - Third-party integration changes - Auth/authorization changes - Performance-critical code - High-traffic endpoints - Data migration required **Rollback procedure:** 1. Immediate: alert team, document in incident channel 2. Execute: kubectl rollout undo / helm rollback / vercel rollback 3. Verify: health checks, error rates, user traffic 4. Database: run down migration if needed 5. Post: update Jira, notify stakeholders, schedule post-mortem **Feature flags:** Use gradual rollout (10%, 50%, 100%) with kill switches ## Common Workflows **Create Feature PR:** ```bash git checkout -b feature/PROJ-123-new-dashboard # Make changes git add . && git commit -m "feat: add dashboard" git push -u origin feature/PROJ-123-new-dashboard # Create PR via Harness Code API ``` **Address Feedback:** ```bash git add . && git commit -m "fix: address review feedback" git fetch origin && git rebase origin/main git push --force-with-lease # Re-request review ``` **Merge PR (via Harness Code):** ```bash # Verify all pipeline checks pass via Harness Code API harness_get_pull_request_checks --pr-number 123 # Merge via Harness Code API harness_merge_pull_request --pr-number 123 --strategy squash git checkout main && git pull origin main # Verify deployment via Harness Pipeline ``` ## Troubleshooting **Merge conflicts:** - Update main: `git checkout main && git pull origin main` - Rebase: `git checkout feature && git rebase main` - Resolve files and `git add . && git rebase --continue` - Force push: `git push --force-with-lease` **Failed CI checks:** - View logs via Harness Pipeline execution logs - Run locally: `npm test && npm run lint && npm run type-check` - Fix and push again **Large PR feedback:** - Create feature base branch - Split into logical chunks - Create sub-PRs against base, then final PR to main ## PR Size Guidelines - **Small:** < 100 lines (ideal, easy to review) - **Medium:** 100-500 lines (acceptable) - **Large:** 500-1000 lines (consider splitting) - **Too Large:** > 1000 lines (must split) ## Review Turnaround - Hotfix: < 1 hour - Bug fix: < 4 hours - Small feature: < 1 day - Medium feature: < 2 days - Large feature: < 3 days ## Best Practices 1. Keep PRs focused on single concern 2. Write descriptive titles and descriptions 3. Link to Jira tickets 4. Include tests and documentation 5. Respond to feedback promptly 6. Use draft PRs for early feedback 7. Clean up commits before merging 8. Delete branches after merge 9. Monitor post-deployment ## Resources - [Conventional Commits](https://www.conventionalcommits.org/) - [Harness Code Repository](https://developer.harness.io/docs/code-repository) - [Git Best Practices](https://git-scm.com/book/en/v2) - [Code Review Best Practices](https://google.github.io/eng-practices/review/)
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · TheLobbi/claude | 100 | MIT |
| akunzai/agent-skills | 100 | MIT |
| hugrverk/riggverk | 100 | MIT |
| notque/vexjoy-agent | 100 | MIT |
| tencent-hunyuan/unirl | 100 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki b800f337b876 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100project-management-jira-workflow-steward
Działa jako Jira Workflow Steward z Agency Agents: pilnuje przepływów git powiązanych z Jira, commitów z odnośnikami, uporządkowanych pull requestów i bezpiecznej strategii gałęzi. - 100git-pr
Prowadzi przez tworzenie skutecznych pull requestów: otwieranie PR, opisy, prośby o przegląd i zarządzanie przepływem PR. - 100managing-jira-issues
Zarządza zgłoszeniami Jira przez jira CLI z wyjściem JSON: tworzenie, podgląd, aktualizacja, wyszukiwanie, pobieranie pełnych hierarchii i obsługa sprintów. - 100jira-issue-to-pr
Konfiguruje automatyzację odpytującą Jira o zgłoszenia create-pr i tworzącą pull requesty w GitHubie, merge requesty w GitLabie lub pull requesty w Bitbucket. - 100pr
Pisze opisy pull requestów i merge requestów. - 100git-pr
Opisuje tworzenie i aktualizację pull requestów na GitHubie w tym repozytorium: format tytułu, struktura treści, czyste opisy i przepływ z gh CLI.