# Github Sync PR Flow

Use when preparing iPolloWork local changes for GitHub: stash or preserve local edits...

- Repository: https://github.com/Devin-AXIS/iPolloWork (7348 stars)
- Category: Git and review
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Devin-AXIS/iPolloWork --skill github-sync-pr-flow -g -a claude-code -y`
Codex: `npx skills add Devin-AXIS/iPolloWork --skill github-sync-pr-flow -g -a codex -y`
Cursor: `npx skills add Devin-AXIS/iPolloWork --skill github-sync-pr-flow -g -a cursor -y`
Gemini CLI: `npx skills add Devin-AXIS/iPolloWork --skill github-sync-pr-flow -g -a gemini-cli -y`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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.

The rest: https://github.com/Devin-AXIS/iPolloWork/blob/HEAD/.codex/skills/github-sync-pr-flow/SKILL.md