contextual-sync
/contextual-sync
Doprowadza katalog context do zgodności z kodem po zmianach bez wpisu w dzienniku i oznacza scalone funkcje jako wdrożone.
- Autor
- mikaelendale ↗
- Repozytorium
- contextual ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 5
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Doprowadza katalog context do zgodności z kodem po zmianach bez wpisu w dzienniku i oznacza scalone funkcje jako wdrożone.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use when the person says "sync the context", "update the context" or "the context is out of date", after code changed without a log entry, or after a feature branch was merged. Brings context/ back in line with the code, flags changes no feature owns, and marks merged features shipped.
Jak działa
- 1. Find what changed
- 2. Find each file's owner
- 3. Bring each affected feature up to date
- 4. Finish merged features (on the default branch)
- 5. Close
Podgląd SKILL.md
---
name: contextual-sync
description: Use when the person says "sync the context", "update the context" or "the context is out of date", after code changed without a log entry, or after a feature branch was merged. Brings context/ back in line with the code, flags changes no feature owns, and marks merged features shipped.
license: MIT
---
# Sync the context with the code
If you haven't this session, do the start-of-session read in `AGENTS.md` first. `<cli>` below is the `cli` value in `context/.meta.json`.
## 1. Find what changed
Work out the starting point from `lastSync` in `context/.meta.json`, as [references/since-last-sync.md](references/since-last-sync.md) describes: the stored commit, else the last commit before the stored date, else a rescan. Then list the changed files: committed since that point, plus anything uncommitted.
## 2. Find each file's owner
Run `<cli> which <path>` for every changed file outside `context/`. Group the files by feature.
- Shared paths: mention them in the log entries of the features they serve, if that's clear. Otherwise just list them in your report.
- No owner: list them for the person with a suggested owner, either a feature's `covers:` or the `shared:` line in `context/architecture.md`. Add them only once the person agrees, unless the right owner is plain from the path.
## 3. Bring each affected feature up to date
For each feature with changes, read its `README.md` and `build.md`, then the diff of its files.
- Correct the facts in `build.md`, `tests.md` and `notes.md`.
- Add one entry at the top of its `log.md`: `## <today> · <agent> · Sync: <what changed>`, saying which commits it covers. Use `Deslop: not verified (changed outside Contextual; the UI wasn't reviewed)` when its UI changed, and `Deslop: not UI` otherwise. If the feature has no `log.md` yet, create it from [assets/feature-log.md](assets/feature-log.md).
- Don't tick an acceptance box you haven't verified. A planned feature whose code now exists becomes `in-progress`.
## 4. Finish merged features (on the default branch)
When a feature's branch has been merged, follow [references/merge.md](references/merge.md): it becomes `shipped`, the plan gets ticked, and its branch status file is deleted.
## 5. Close
1. Rewrite the status file for the current branch (`context/status/main.md` on the default branch, otherwise from [assets/status-branch.md](assets/status-branch.md) if it's missing), in 40 lines or fewer.
2. In `context/.meta.json`, set `lastSync` to `{ "commit": "<git rev-parse HEAD>", "date": "<now, ISO 8601 UTC>" }`. Change nothing else in that file.
3. Run `<cli> check --fix`, then fix what it reports until there are 0 errors.
4. Commit the context changes as `Sync context`. Then report what changed for each feature, and anything you couldn't map.
Pliki w paczce (5)
- SKILL.md 3 KB
- assets/feature-log.md 1 KB
- assets/status-branch.md 1 KB
- references/merge.md 1 KB
- references/since-last-sync.md 1 KB
Wersje
W bazie nie ma innych skilli o nazwie contextual-sync.
Migawka bazy z 13.11.2026 · wersja paczki ad407e58f811 (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
- 90contextual-setup
Zapisuje kontekst projektu w katalogu context po raz pierwszy, z pliku planu, kilku pytań lub istniejącego kodu. - 90contextual-next
Wybiera kolejną funkcję z katalogu context, buduje ją na własnej gałęzi, weryfikuje, zapisuje w kontekście i zatrzymuje się do przeglądu. - 100planupdate
Uzgadnia istniejący plan z bieżącą bazą kodu i oznacza elementy, które zostały już wdrożone. - 100update-project-docs
Synchronizuje task.md, changelog.md i files.md z kodem i historią gita, a potem podaje gotowy tekst commita. - 100sync-context
Po wdrożeniu zmiany uzgadnia wspólny kontekst z kodem: statusy z roadmapy, polecenia, znane problemy, zmienne środowiskowe i listy architektury. - 100update-docs
Wykrywa rozjazdy między dokumentacją a kodem, oznacza nieaktualne twierdzenia i wprowadza poprawki w dokumentach.