- name
- github-sync-pr-flow
- description
- Use when preparing iPolloWork local changes for GitHub: stash or preserve local edits, sync the current personal branch with remote main, re-apply local work, diagnose conflicts, commit in English, push to the current remote branch, and open a PR to main without creating extra branches.
GitHub Sync, Pull, and PR Flow
Use this workflow for iPolloWork developer submissions, personal-branch syncs, and PR requests. Keep the developer on their current personal branch unless the user explicitly asks for another branch.
Permission Boundary
- This skill is a workflow guide. Do not run the publish flow just because the skill exists.
- Before changing branch history, syncing from
main, committing, pushing, creating a PR, or calling GitHub APIs, get explicit user approval for that phase. - If the user only asks to prepare or document the workflow, only create or update this skill file.
- If the user asks to check readiness, inspect and report state without changing Git state unless they approve the next step.
- If any command would overwrite, drop, rebase, force-push, or otherwise risk local work, stop and ask for explicit approval.
Branch Rules
- Do not create extra branches by default.
- Never commit directly to
main. - Treat the current non-main branch as the developer's personal remote branch.
- Commit messages, PR titles, and PR bodies must be in English.
- Push to the current branch's upstream or
origin/<current-branch>. - PR target is the remote default branch, normally
origin/main.
Intent Routing
Choose the smallest workflow that matches the user's words.
- "Submit/commit my code" means commit current local changes and push them to the current personal remote branch. Do not open a PR unless requested.
- "Push my code" means push committed or newly committed changes to the current personal remote branch. Do not open a PR unless requested.
- "Pull/sync/update from main" means preserve local work, bring
origin/maininto the current personal branch, then restore local work. Do not commit or push unless requested. - "Open a PR" means ensure the personal branch is pushed, then create a PR from the current branch to
main. - "Merge my code into main" means use the PR flow. Do not push directly to
main. - "Merge the PR" means merge through GitHub after checks and review approval, using the repository's normal merge method.
- Ambiguous requests must be clarified before write operations.