Push commits to an existing GitHub PR's source branch. NEVER create new branches. Use when the user says "push to PR
80
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Push local commits to an existing PR's source branch. Never create new branches.
curl -s https://api.github.com/repos/{OWNER}/{REPO}/pulls/{N} \
| python3 -c "import sys,json; p=json.load(sys.stdin); print(f\"branch={p['head']['ref']}\nclone_url={p['head']['repo']['clone_url']}\ncan_modify={p['maintainer_can_modify']}\")"head.ref = branch name (e.g. active_visual_chat)head.repo.clone_url = fork URLmaintainer_can_modify must be truegit remote -v # check if clone_url already listed
git remote add <name> <clone_url> # only if missinggit fetch <remote> <branch>
# If local commits not on top:
git rebase <remote>/<branch>git push <remote> HEAD:<branch>git push <remote> <local_branch> if local branch differs from PR branch — always use HEAD:<pr_branch>head.ref in API responsemaintainer_can_modify is false, inform user — cannot pushc6f1797
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.