Przejdź do treści
Biblioteka skilli
Produktywność osobista · Automatyzacja

sync

/sync

Synchronizuje skonfigurowane repozytorium kontekstu z jego źródłem i uruchamia opcjonalną integrację konfiguracji, na wyraźne żądanie.

Repozytorium
skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
11.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 11.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Synchronizuje skonfigurowane repozytorium kontekstu z jego źródłem i uruchamia opcjonalną integrację konfiguracji, na wyraźne żądanie.

Oryginalny opis (EN)

Synchronize the configured context repository with its upstream and run its optional setup integration. Use for an explicit request to sync the private knowledge repository.

Jak działa

  1. Private configuration
  2. SSH execution and preflight
  3. Synchronization
Sekcje z nagłówków SKILL.md, w oryginale · 50 linii, 706 słów
Podgląd SKILL.md
---
name: sync
description: Synchronize the configured context repository with its upstream and run its optional setup integration. Use for an explicit request to sync the private knowledge repository.
---

# Sync

## Private configuration

For an ordinary invocation that needs personal defaults or integrations, read the installed `skill-config` skill and resolve the `profile.<key>` fields below. Load only context relevant to the request. Command examples with these fields are templates; substitute configured values as quoted arguments before execution. Ask for required missing fields and skip unavailable optional integrations.

For a prepared worker packet, use only its declared access and supplied configuration. The coordinator resolves private defaults and passes the minimum required values or permitted resources. A worker must not load a machine-wide profile or unrelated context unless the packet explicitly permits it.

Run this workflow in `profile.paths.brain`. Invoking this skill authorizes its setup, commit, and push steps.

## SSH execution and preflight

On this Mac, run Git remote operations and SSH-signed commits in an interactive
terminal with access to the 1Password agent. For Codex `exec_command`, use
`tty: true` and `sandbox_permissions: "require_escalated"`, subject to normal
approval review. Use this mode for the preflight, pull, signed commit, push,
and remote verification. Keep local read-only inspection in the sandbox.

After inspecting the repository and before creating a stash, resolve the current
branch's configured upstream remote and branch. Run `git ls-remote --exit-code
--heads <remote> <branch>` and require success. Do not hardcode `origin/main`.
If it fails, preserve the working tree and diagnose the connection before
stashing. Agent socket access and authorization to sign are separate checks.

For `Operation not permitted` or `communication with agent failed`, verify the
execution mode and effective `IdentityAgent`; do not conclude that 1Password is
locked or the key is missing. If the failed attempt was noninteractive or
sandboxed, retry once in the required mode. If it already used that mode, report
the actual blocker instead of repeating the same command. Apply this check
before falling back to an unsigned commit. Do not change global sandbox policy,
export private keys, or relax 1Password authorization settings.

When resuming a failed run, inspect its recorded stash IDs and operation state
first. Reuse the existing stash; preserve any newer changes separately. Never
create another stash merely because authentication is being retried.

## Synchronization

1. Inspect `git status --short --branch`. If another merge or rebase is already in progress, stop and report it. Stay on the current branch and use its configured upstream.
2. If local changes exist, run `git stash push -u -m "sync"` and record the new stash ID. Leave existing stashes alone.
3. Run `git pull --prune --rebase` (`git pull -pr`). Resolve conflicts by preserving the intent of both sides, then run `git add <resolved-files>` and `GIT_EDITOR=true git rebase --continue` until the rebase finishes. Ask only when conflicting intent cannot be inferred. If the pull fails for another reason, stop and preserve the stash.
4. If you created a stash, restore it with `git stash apply <recorded-stash-id>`. Resolve any conflicts and stage the resolved files. Drop only that stash, by its current stash reference, after its contents are safely restored and committed.
5. After restoring local changes, run the configured `profile.integrations.sync.setup_command` when present. Without that optional setup integration, skip machine configuration and continue repository synchronization. This installs new shared skills and refreshes managed configuration links. If incoming configuration needs setup beyond links, read its updated installation instructions and perform the relevant setup. Preserve machine-specific settings and report any setup that cannot finish. Do not run full machine provisioning unless the incoming changes require it.
6. Review `git diff` and `git diff --cached`. Stage the local Brain changes with `git add -A`, then run `git diff --cached --check`. If staged changes exist, run `git commit -S -m "chore: sync brain"` with the 30 second signing timeout from AGENTS.md. If SSH signing fails or times out, retry unsigned and report it. Do not add a co-author.
7. Run `git push`. Never force-push. If the remote advanced, repeat the pull, conflict-resolution, and setup steps, commit any resulting local changes, then retry the push once.
8. Verify that the remote branch SHA matches `git rev-parse HEAD`, and check `git status --short --branch`. Report the sync result, installed skills or configuration, and any remaining changes or required reloads.

Keep repository syncing limited to Brain, and setup limited to its managed skills and configuration. Do not sync nested repositories or discard changes to resolve conflicts.

Wersje

RepozytoriumWynikLicencja
Ta strona · lucastamoios/skills100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
makenotion/notion-cookbook100MIT
wookiya1364/scv-claude-code100MIT
biliboss/skills100MIT
olehsov/gcp-certification-coach100MIT
enzo-thuilliez/my-starter-kit100MIT

Migawka bazy z 13.11.2026 · wersja paczki 9463a7a75ca3 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100skill-sync
    Synchronizuje skille między instalacją lokalną a repozytorium GitHub będącym źródłem prawdy: instaluje, aktualizuje, wyświetla i wypycha skille.
  • 100react-sync
    Buduje lokalne zmiany React w wariantach bundli używanych przez Next.js, synchronizuje je z lokalnym checkoutem Next.js i testuje integrację.
  • 100update-qm
    Synchronizuje prywatny fork qm z upstreamem przez scalenie i otwiera pull request ze zmianami.
  • 100meeting-sync
    Synchronizuje nowe spotkania z Granola do lokalnego folderu Knowledge przy dziennym planowaniu oraz przeglądzie i synchronizacji spotkań.
  • 95obsidian-github-sync
    Synchronizuje vault Obsidian z repozytorium GitHub, wykrywa konflikty i konfiguruje codzienną kopię zapasową.
  • 95github-sync-upstream
    Synchronizuje kod z repozytorium upstream do docelowego forka: scala do gałęzi synchronizacji, przywraca chronione pliki, rozwiązuje konflikty i otwiera pull request.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.