What problem does it solve?
Pull requests become slow, noisy, and error-prone without consistent branch naming, commit hygiene, reviewer selection, merge strategies, and post-merge verification. This skill reduces review friction, prevents merge conflicts, and ensures merges are traceable and deployment-safe.
Core Features & Use Cases
- Structured PR creation: Enforces branch naming, commit message conventions, and a comprehensive PR description template to make changes discoverable and reviewable.
- Review coordination and hygiene: Recommends reviewer selection, response patterns for feedback, re-review practices, and escalation paths for stalled PRs.
- Safe merging and cleanup: Defines pre-merge checks, merge strategy selection, and post-merge steps such as branch deletion, issue verification, and deployment monitoring.
- Use Case: A feature branch follows the naming convention, assigns domain reviewers, resolves requested changes with fixup commits, receives required approvals, and is merged with a documented strategy to minimize regressions.
Quick Start
Create a PR from branch feature/123-add-login into main, include the What/Why/How/Testing checklist in the description, assign two reviewers with domain ownership, and request CI to run before merging.
