Skip to content
Skills Library
Programming · Automation

sync-context

/sync-context

After a change lands, brings the shared context in line with the code (roadmap statuses, AGENTS.md commands, known issues, env vars, architecture lists) with surgical edits that add lines and never rewrite curated prose. Flags specs the change made stale. Use when a slice is done or merged, or when save-session lists items for shared context.

Repository
pantoo-ai ↗
Licence
MIT
Last repository change
29.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

After a change lands, brings the shared context in line with the code (roadmap statuses, AGENTS.md commands, known issues, env vars, architecture lists) with surgical edits that add lines and never rewrite curated prose. Flags specs the change made stale. Use when a slice is done or merged, or when save-session lists items for shared context.

Arguments

/sync-context [uncommitted]
Original author description

After a change lands, brings the shared context in line with the code (roadmap statuses, AGENTS.md commands, known issues, env vars, architecture lists) with surgical edits that add lines and never rewrite curated prose. Flags specs the change made stale. Use when a slice is done or merged, or when save-session lists items for shared context.

How it works

  1. 1. Scope
  2. 2. Update, line by line
  3. Finish
Original SKILL.md headings · 46 lines, 386 words
SKILL.md preview
---
name: sync-context
description: After a change lands, brings the shared context in line with the code (roadmap statuses, AGENTS.md commands, known issues, env vars, architecture lists) with surgical edits that add lines and never rewrite curated prose. Flags specs the change made stale. Use when a slice is done or merged, or when save-session lists items for shared context.
argument-hint: "[uncommitted]"
---

Recommended: Sonnet · low.

## 1. Scope

- `git fetch --quiet`; behind the base branch → say pull first (a teammate may have synced already).
- The change: on a feature branch, everything since `git merge-base <base> HEAD` plus uncommitted
  work; on the base branch, or with `uncommitted`, the working tree. Use `--name-status`: added,
  modified and deleted each matter.
- Read `context/session.md` → **For shared context**, if it exists.
- Code and manifests are the sources. Docs, tests and lockfiles are context, not changes. Nothing
  left and no session items → "nothing to sync"; stop.

## 2. Update, line by line

Re-read each file right before editing it. Idempotent: a fact already there in any wording isn't
added again, so a second run on the same change makes no edits.

| File | What sync-context may change |
| --- | --- |
| `context/roadmap.md` | Status cells, from evidence. `done` only with the tier's steps run or the developer's word, and then Now and Next too. Lines in Decisions and notes from session items |
| `AGENTS.md` | Commands that were added or renamed; a row in Where things are for a new context file |
| `context/known-issues.md` | An issue the diff fixed → `fixed`. A new issue with a real `path:line` → a summary row and its block |
| `context/standards.md` | The env vars table: a new variable and where it's read |
| `context/architecture.md` | The routes, modules or tables it lists, when the diff adds or removes one |

Flag, don't edit:

- A new dependency missing from `standards.md` → Approved dependencies or from `libraries.md`:
  the developer adds it, or `write-spec` if it was a real choice.
- A spec the code now contradicts → stale: `/pantoo:write-spec NNN` to update or supersede it.
- Every `Assumed` spec → decision debt, `/pantoo:write-spec NNN` to ratify.
- Anything that would rewrite curated prose, reorder slices or add slices (`plan-roadmap`) → listed
  for the developer.

Once session items are in the shared files, set **For shared context** in `session.md` to "none".

## Finish

```
Context synced: <N edits in M files | everything already current>.
Next: <commit the context changes | the first flagged item's command>.
Heads-up: <only if real: stale specs, Assumed specs, dependencies to approve, conflicts>
Files: <the files edited>
```

Versions

The database has no other skills named sync-context.

Database snapshot: 13.11.2026 · package version 91f6a2938380 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90contextual-sync
    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.
  • 100code-sync
    Reconcile the project's documents with what the code now shows, after a merge or at the end of a build: spec statuses (building → done only with a named gate, or → stale with the reason), assumed specs owed ratification, the project README map and its Last verified date.…
  • 100technical-spec
    Defines environment variables, architecture design, and build/test commands. Use when configuring environment or designing architecture.
  • 100trove-docs-sync-audit
    Read-only documentation drift audit comparing what the docs claim against what the code does. Covers READMEs, setup guides, API and env docs, changelogs, examples, and generated docs. Use when asked whether docs are stale, missing, or inconsistent after a code change. This is not a code review.
  • 100openspec-sync-specs
    Sync delta specs from an OpenSpec change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change. Also use when the user says "openspec sync" or "opsx sync".
  • 100openspec-sync-specs
    Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.