agentleFS
KUNDURUHIMANEESHREDDYKUNDURUHIMANEESHREDDY/saber/.agents/skills/sync/SKILL.md

sync

Skill0 starsChanged 55 days agoMITView on GitHub

Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.

  • Commits and pushes

57 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use develop, scope and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • hong9LeeSkill

    develop

    빌드, 아키텍처, git 관련 작업 시 OMS MSA 공통 인프라 규칙을 적용한다. 기술 스택, 빌드 명령, 헥사고날 아키텍처 구조, git 워크플로우, AI Context 동기화 규칙을 다룬다. 코드 작성 컨벤션은 /convention, 테스트 컨벤션은 /test-guide 스킬을 참조.

    Also in 6 projects that use this

  • YuriNachosSkill

    scope

    Configure claude-scope status line widgets for Claude Code. Use when user wants to customize widgets, change theme, reorder elements, or modify display style.

    Also in 7 projects that use this

  • nicolasestremSkill

    document

    Create focused documentation for specific components or features

    Also in 5 projects that use this

  • kt057Skill

    check

    lint, typecheck, test を一括実行して結果をサマリーする

    Also in 6 projects that use this

  • Microsoft AzureSkill

    test

    Also in 8 projects that use this

  • Microsoft AzureSkill

    validate

    Run the full CI validation workflow locally before submitting a PR. Use this as a final check to ensure all Azure DevOps CI pipeline steps will pass.

    Also in 4 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 12 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 47 edited versions we read keep these.

  • 12

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When in doubt about conflict resolution — ask the user.

    line 16
  2. Very specific:

    Check for uncommitted changes first.

    line 20
  3. Distinctive:

    Check whether the current session branch has an upstream branch.

    line 21
  4. Distinctive:

    If the current session branch has an upstream branch: 3.1.

    line 22
  5. Distinctive:

    If conflict resolution is unclear, ask the user how to proceed.

    line 40
  6. Distinctive:

    If the push is rejected because the rebase rewrote history, explain the situation to the user and ask for approval before force-pushing.

    line 48
  7. Distinctive:

    If the current session branch does not have an upstream branch: 4.1.

    line 49
  8. Distinctive:

    If there is only one remote, use it.

    line 51
  9. Distinctive:

    If there are multiple remotes, use the #tool:vscode/askQuestions tool to ask which remote to use.

    line 52
  10. Distinctive:

    After the workflow completes, validate the result with explicit checks:

    line 60
  11. Distinctive:

    Verify the working tree is clean:

    line 62
  12. Distinctive:

    Verify sync state (ahead/behind counts are both 0):

    line 66
  13. Distinctive:

    If the branch was newly published, verify the upstream branch is configured:

    line 70

“Common” is measured: kept by at least 6 in 10 of the 47 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->

Sync Changes

Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.

Guidelines

  • Never force-push (--force, --force-with-lease) without explicit user approval.
  • Never skip pre-push hooks (do not use --no-verify).
  • Never rewrite or drop commits during rebase without asking the user.
  • When in doubt about conflict resolution — ask the user.

Workflow

  1. Check for uncommitted changes first. If there are uncommitted changes, use the /commit skill to commit them before continuing.
  2. Check whether the current session branch has an upstream branch.
  3. If the current session branch has an upstream branch: 3.1. Fetch the upstream remote first so tracking refs are up to date.
    git fetch <upstream-remote>
    3.2. Check ahead/behind counts. If the branch is already in sync (0 ahead, 0 behind), stop and report that no sync is needed.
    git rev-list --left-right --count HEAD...@{u}
    3.3. If behind, rebase onto the upstream tracking branch.
    git rebase @{u}
    3.4. If there are merge conflicts, resolve them by preserving the intent of both sides. Stage the resolved files and continue the rebase.
    git add <resolved-files>
    git rebase --continue
    If conflict resolution is unclear, ask the user how to proceed. If the user wants to stop the rebase, abort it:
    git rebase --abort
    3.5. If the branch has local commits (ahead > 0), push them to the remote after a successful rebase.
    git push
    If the push is rejected because the rebase rewrote history, explain the situation to the user and ask for approval before force-pushing.
  4. If the current session branch does not have an upstream branch: 4.1. Determine the remote to publish to.
    • If there is only one remote, use it.
    • If there are multiple remotes, use the #tool:vscode/askQuestions tool to ask which remote to use. 4.2. Publish the current branch and set upstream in one step.
    git push -u <remote> HEAD

Validation

After the workflow completes, validate the result with explicit checks:

  1. Verify the working tree is clean:
    git status --porcelain
  2. Verify sync state (ahead/behind counts are both 0):
    git rev-list --left-right --count HEAD...@{u}
  3. If the branch was newly published, verify the upstream branch is configured:
    git rev-parse --abbrev-ref --symbolic-full-name @{u}

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.