PR
Overview
Create a PR end-to-end: stage and commit changes, push the branch, fill the PR template, ask for confirmation, then open the PR with gh.
Workflow
- Inspect git state: run
git status -sb, identify uncommitted or 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> or git 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.md if 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.
Notes
- Follow repo conventions for templates, required sections, and Conventional Commits.
- Require explicit confirmation before any network operations:
git push or gh pr create
