What problem does it solve?
This skill standardizes the manual, error-prone process of turning local code changes into a clean merged pull request, reducing accidental file inclusion, failing CI, and improper merge practices.
Core Features & Use Cases
- Branch creation & naming: Guidance for creating feature, fix, and chore branches following team conventions.
- Staged-only commits: Best practices to stage only intended files and craft clear, multi-line commit messages.
- PR creation & CI handling: Instructions to open PRs with the GitHub CLI, monitor CI checks, inspect failed logs, iterate fixes, and merge with squash semantics.
- Use Case: A developer finishing a feature can follow this workflow to create a focused branch, open a descriptive PR, resolve CI failures, and merge without leaving temp files or broken tests.
Quick Start
Create a branch from your current HEAD, stage only the intended files, push to origin, open a pull request with the GitHub CLI, monitor CI results, fix any failures, and squash-merge when green.