Imported from 2ssunny/ai-agents (skills/global/push-pr/SKILL.md). Install upstream with npx skills add 2ssunny/ai-agents --skill push-pr. Copyright stays with the author.

Push & PR Workflow

Global rules forbid autonomous push. When the user explicitly asks, this skill defines the exact approved procedure. Follow it precisely — deviations (wrong author, wrong base branch, co-author lines) have all been corrected by the user before and waste a review cycle.

Commit rules

• Commit any uncommitted work first, in logical units (not one mega-commit).
• Message: Angular convention — feat:, fix:, docs:, refactor:, test:, chore: with a clear scope and summary.
• Always append --author using commit.author from agent-config.json at the ai-agents repository root. If that file is missing, ask the user for the identity instead of guessing or copying one out of git history.
• Never add Co-Authored-By lines or AI attribution footers unless commit.coAuthorTrailers is true.
• Never --force, never --no-verify.

Branch and PR rules

• Base branch is git.prBaseBranch from agent-config.json (default develop, or the project's integration branch). Never open a PR against a branch listed in git.protectedBranches (default main) and never push to one directly — when humanMergesProtectedBranches is set, the user merges there themselves via GitHub.
• If currently on a protected or integration branch with local changes, create a feat/<name> or fix/<name> branch first.
• PR title follows the same Angular convention as commits. Body: concise summary of what/why, list of key changes.
• After creating PRs, if multiple are open, present the sensible merge order (dependency-first) in one short list.

Conflict resolution

When asked to resolve PR conflicts (e.g. "#10 conflict resolve해"):

1. gh pr view <n> to identify head/base branches.
2. Fetch and merge base into the head branch locally (prefer merge over rebase — the branch is shared).
3. Resolve conflicts preserving both sides' intent; when intent is ambiguous, ask rather than guess.
4. Commit the merge (same author flag), push the head branch.

After pushing

Check CI: gh pr checks <n> (or gh run list --limit 3). If checks fail, read the logs, fix, and push again — don't report "done" with red CI. Finish with a one-line status per PR: number, title, CI state, merge order position.