PR-Auto
Overview
Create a PR end-to-end: stage and commit changes, push the branch, fill the PR template, open the PR with gh, then merge it with gh safely.
Workflow
- •Inspect git state: run
git status -sb, identify uncommitted/untracked changes, and confirm which files to include. Avoid modifying unrelated files. - •Stage changes:
git add <paths>for the approved files only, then re-check status. - •Commit: generate a Conventional Commit message when requested and run
git commit -m "<message>". - •Push branch:
git push origin <branch>orgit push -u origin <branch>if needed. If push fails due to auth/remote issues, ask for next steps. - •Build PR body: read
.github/pull_request_template.mdif present and fill required sections (Summary, Type of Change, Related Issues). Keep checkboxes accurate. - •Create PR:
gh pr create --base <base> --head <branch> --title "<title>" --body "<body>", then return the PR URL. - •Then merge with
gh pr merge <pr> --squashand return the final PR state/URL.
Notes
- •Follow repo conventions for templates and Conventional Commits.
- •Require explicit confirmation before any network operations:
git push,gh pr create,gh pr merge. - •Prefer not to merge if required reviews/checks are missing or failing; if blocked, report status and ask for next steps.