Github Sync PR Flow
Use when preparing iPolloWork local changes for GitHub: stash or preserve local edits...
Install
npx skills add Devin-AXIS/iPolloWork --skill github-sync-pr-flow -g -a claude-code -y- Repository
- Devin-AXIS/iPolloWork7.3k
- Category
- Git and review
- Updated
- 3d ago
- License
- See repository
- Context cost
- Mediumabout 1,865 tokens
- Runs scripts
- No, instructions only
What it does
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.
