agentleFS
Sign inStart free
vzhukovsvzhukovs/podman-desktop-kit/skills/sync/SKILL.md

sync

Skill0 starsChanged 11 days agoApache-2.0View on GitHub

Report fork status against upstream and the state of every worktree.

54 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use develop, scope and 7 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

  • AnthropicSkill

    debug

    Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

    Also in 10 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 47 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read-only. Never rebase, never push, never reset from here — this command exists so the answer to "where am I" costs nothing and is always …

    line 9
  2. Distinctive:

    Call out anything that will bite later rather than only what is broken now:

    line 30

“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

Read-only. Never rebase, never push, never reset from here — this command exists so the answer to "where am I" costs nothing and is always safe to ask.

Steps

  1. pdkit doctor — if anything required is red, stop and report it. Every later step assumes it.
  2. git fetch upstream --prune and git fetch origin --prune.
  3. For the base branch: git rev-list --left-right --count upstream/main...main. Report both numbers. Behind is normal; ahead of upstream on main is not — it means something was committed to the base branch, and it will follow every branch cut from it afterwards.
  4. git worktree list, and for each: its branch, and git status --porcelain.
  5. For each branch matching DESKTOP-<n>/…, run pdkit state <n> and report the state next to it.

Report

One line per branch: branch, issue state, ahead/behind against upstream/main, whether its tree is clean.

Call out anything that will bite later rather than only what is broken now:

  • a DESKTOP-… branch with no state record, or a state record with no branch — the two have drifted apart;
  • an uncommitted change: preflight refuses to report on a dirty tree, so this blocks the flow before it starts;
  • a branch far behind upstream/main — it will rebase, and the further behind it is the more likely that rebase is semantic rather than mechanical.

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.

Check your setup, free