CtrlK
BlogDocsLog inGet started
Tessl Logo

sync-upstream

Update a stale session branch by rebasing onto the latest origin. Use when the upstream has moved significantly and the session needs to catch up, resolving conflicts by preserving upstream changes and adapting session work to fit.

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

Update Branch

Rebase the current session branch onto the latest upstream so the work stays grounded in origin.

Workflow

  1. If there are uncommitted changes, use the /commit skill to commit them first.
  2. Fetch the latest upstream and rebase onto it:
    git fetch origin
    git rebase origin/main
    Use the appropriate base branch if it is not main.

Conflict Resolution

When conflicts arise, upstream always wins:

  • Never alter upstream logic, APIs, or patterns to accommodate session changes.
  • Adapt session work to fit the new upstream — rename, restructure, or rewrite as needed while preserving the session's goals.
  • After resolving each conflict, git add the files and git rebase --continue.

Validation

After the rebase completes, verify the result still compiles and meets the session's objectives. If session changes no longer make sense against the updated upstream, explain what changed and propose a revised approach.

Repository
posit-dev/positron
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.