CtrlK
BlogDocsLog inGet started
Tessl Logo

push-to-pr

Push commits to an existing GitHub PR's source branch. NEVER create new branches. Use when the user says "push to PR

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Push to PR

Push local commits to an existing PR's source branch. Never create new branches.

Workflow

1. Find PR head branch

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 URL
  • maintainer_can_modify must be true

2. Ensure remote exists

git remote -v  # check if clone_url already listed
git remote add <name> <clone_url>  # only if missing

3. Fetch + rebase if needed

git fetch <remote> <branch>
# If local commits not on top:
git rebase <remote>/<branch>

4. Push

git push <remote> HEAD:<branch>

Critical Rules

  1. NEVER create new branches on any remote
  2. NEVER git push <remote> <local_branch> if local branch differs from PR branch — always use HEAD:<pr_branch>
  3. Branch name comes only from head.ref in API response
  4. If maintainer_can_modify is false, inform user — cannot push
  5. If push rejected (non-fast-forward), fetch and rebase first
Repository
Project-N-E-K-O/N.E.K.O
Last updated
First committed

Is this your skill?

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.